Merge remote-tracking branch 'upstream/next' into feature/math-rendering

Author: cestef

Diff for: .github/workflows/docs.yml

@@ -16,7 +16,7 @@ jobs:
       - name: checkout
         uses: actions/checkout@v4
       - name: build
-        uses: shalzz/zola-deploy-action@v0.18.0
+        uses: shalzz/zola-deploy-action@v0.19.2
         env:
           BUILD_DIR: docs/
           BUILD_ONLY: true
@@ -28,7 +28,7 @@ jobs:
       - name: checkout
         uses: actions/checkout@v4
       - name: build_and_deploy
-        uses: shalzz/zola-deploy-action@v0.18.0
+        uses: shalzz/zola-deploy-action@v0.19.2
         env:
           PAGES_BRANCH: gh-pages
           BUILD_DIR: docs/

Diff for: CHANGELOG.md

@@ -1,6 +1,9 @@
 # Changelog
 
-## 0.20.0 (unreleased)
+## 0.21.0 (unreleased)
+
+
+## 0.20.0 (2025-02-14)
 
 - Add `name` annotation for codeblock
 - Add argument to `zola serve` to watch additional directories
@@ -13,6 +16,8 @@
 - Handle more editors with change detection in `zola serve`
 - Add argument to `zola serve` to write HTML files to disk (`--store-html`)
 - Add optional parsing of Markdown definition lists
+- Add avif support to the `resize_image` filter
+- Allow `insert_anchor_links` at config.toml level
 
 
 ## 0.19.2 (2024-08-15)

Diff for: CONTRIBUTING.md

@@ -8,7 +8,7 @@ However, if you notice an error or typo in the documentation, feel free to direc
 If you want a feature added or modified, please open a thread on the [forum](https://zola.discourse.group/) to discuss it before doing a PR.
 
 Requested features will not be all added: an ever-increasing features set makes for a hard to use and explain softwares.
-Having something simple and easy to use for 90% of the usecases is more interesting than covering 100% usecases after sacrificing simplicity.
+Having something simple and easy to use for 90% of the use cases is more interesting than covering 100% use cases after sacrificing simplicity.
 
 ## Issues tagging