asxpi/blog
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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
Details
Build and Deploy to Production / build (push) Successful in 11s
Details
Build and Deploy to Production / deploy (push) Successful in 18s
Details

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

8
Dockerfile
View file

@ -1,10 +1,10 @@
# Renovate bumps the zola pin; flake.nix (used by the tests) tracks nixpkgs.
FROM ghcr.io/getzola/zola:v0.23.6 AS build
# Keep in step with the zola in flake.nix (tests, local serve); Renovate
# leaves this pin alone (renovate.json). 0.23 changes config.toml.
FROM ghcr.io/getzola/zola:v0.22.1 AS build
COPY . /project
WORKDIR /project
# The image has no zola on PATH since 0.23 (/bin/zola moved to /zola)
RUN ["/zola", "build"]
RUN ["zola", "build"]
FROM nginx:1.28-alpine