Keep zola at 0.22.1, in step with the flake
All checks were successful
Build and Deploy to Production / check (push) Successful in 5s
Build and Deploy to Production / build (push) Successful in 11s
Build and Deploy to Production / deploy (push) Successful in 18s

zola 0.23 changes config.toml ([markdown.highlighting] no longer takes
`enabled`) and moved its binary in the image, while the flake that
runs the tests and local serve still has 0.22.1. Bumping only the
image split the two and broke the build (runs 411, 412). Go back to
0.22.1 and have Renovate leave the image pin alone: bump both together
by hand, with the config migration.

Assisted-by: Claude:opus-5-5
This commit is contained in:
Sergei Poljanski 2026-11-13 02:08:08 +04:00
commit ab7aa5d68e
Signed by: asxpi
GPG key ID: 4F8851660FA4121B
2 changed files with 13 additions and 4 deletions

View file

@ -2,5 +2,14 @@
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"local>asxpi/renovate"
],
"packageRules": [
{
"description": "zola must match the flake's (tests, local serve): bump both by hand, and migrate config.toml for 0.23 ([markdown.highlighting] lost `enabled`)",
"matchPackageNames": [
"ghcr.io/getzola/zola"
],
"enabled": false
}
]
}