# Is it possible to have version 0.22 available on Homebrew?

**URL:** <https://zola.discourse.group/t/is-it-possible-to-have-version-0-22-available-on-homebrew/2955>\
**Category:** Support\
**Created:** [August 6, 2026, 2:01pm UTC](https://zola.discourse.group/t/is-it-possible-to-have-version-0-22-available-on-homebrew/2955 "2026-08-06T14:01:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![asibahi](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/asibahi/32/1567_2.png) [@asibahi](https://zola.discourse.group/u/asibahi)\
**Post date:** [August 6, 2026, 2:01pm UTC](https://zola.discourse.group/t/is-it-possible-to-have-version-0-22-available-on-homebrew/2955/1 "2026-08-06T14:01:33Z")

</div>

Hello.

I upgraded the zola version today and my website stopped building. There are more breaking changes than I can work through right now and since brew upgraded it lost the older version, and I cannot figure out how to install it back.

I dont know if the brew bottle is “official” or not but 0.22 being available and pinnable would solve a big pain point.

Edit: Two things would make the changes more palatable:

- This is actually the main annoyance: Restrict the Tera syntax that works in `md` files. Not every code block that has the literal `{{` should be escaped. Even creating a new syntax of `{%<` that exclusively runs components or something would be preferable.
- Show errors for all files when compilation fails. As it stands, it stops as soon as one file errors, so fixing stuff becomes very whack-a-mole.

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [August 6, 2026, 9:58pm UTC](https://zola.discourse.group/t/is-it-possible-to-have-version-0-22-available-on-homebrew/2955/2 "2026-08-06T21:58:00Z")

</div>

The binary is available on the Zola github page: [Releases · getzola/zola · GitHub](https://github.com/getzola/zola/releases#release-v0.22.1)

No clue who handles it on homebrew.

> This is actually the main annoyance: Restrict the Tera syntax that works in `md` files. Not every code block that has the literal `{{` should be escaped. Even creating a new syntax of `{%<` that exclusively runs components or something would be preferable.

The whole point is that it’s the same syntax. Wrap things in raw/endraw if needed, or you can mark globs in the config to skip templating. It took me maybe 20 minutes to upgrade the Zola docs? [zola/docs at master · getzola/zola · GitHub](https://github.com/getzola/zola/tree/master/docs)

> Show errors for all files when compilation fails. As it stands, it stops as soon as one file errors, so fixing stuff becomes very whack-a-mole.

I thought about it but not that many people use {{ }} etc in their content in practice so I kept it simple

---

<div class="post-metadata">

**Author:** ![asibahi](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/asibahi/32/1567_2.png) [@asibahi](https://zola.discourse.group/u/asibahi)\
**Post date:** [August 7, 2026, 6:32am UTC](https://zola.discourse.group/t/is-it-possible-to-have-version-0-22-available-on-homebrew/2955/3 "2026-08-07T06:32:19Z")

</div>

> [@keats](#):
>
> > Show errors for all files when compilation fails. As it stands, it stops as soon as one file errors, so fixing stuff becomes very whack-a-mole.
> 
> I thought about it but not that many people use {{ }} etc in their content in practice so I kept it simple

What does `{{` have to do with compilation errors being shown for all files?

> The whole point is that it’s the same syntax. Wrap things in raw/endraw if needed, or you can mark globs in the config to skip templating.

I don’t like that it is the same syntax. I edit my markdown files as markdown files, not as templates. And I don’t want to litter them with SSG-specific stuff (besides the frontmatter, which is trivial enough to edit). The shortcodes were an ok compromise

> you can mark globs in the config to skip templating

This is useful (and thanks for pointing it out). But that would not work for me, as the articles where I use shortcodes and the ones I have `{{` in are all in the same directory. And skipping articles individually in the config is brittle and annoying. If anything this should be controlled by a frontmatter variable.

* * *

I apologize if my tone seems confrontational. But note that all I asked for in the beginning is to be able to stick to a previous version of zola in Homebrew, and that’s all I want.

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [August 7, 2026, 6:53am UTC](https://zola.discourse.group/t/is-it-possible-to-have-version-0-22-available-on-homebrew/2955/4 "2026-08-07T06:53:48Z")

</div>

I’ll let someone that knows about homebrew answer then if the binary in the releases page is not enough.
