Commit graph

5 commits

Author SHA1 Message Date
469e00d1c2 deps: Update nginx Docker tag to v1.30
All checks were successful
Test / check (push) Successful in 6s
2026-11-12 22:22:41 +00:00
ab7aa5d68e
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
2026-11-13 02:08:08 +04:00
2f1cc8184a
Dockerfile: call zola by its path in the 0.23 image
Some checks failed
Build and Deploy to Production / check (push) Successful in 5s
Build and Deploy to Production / build (push) Failing after 4s
Build and Deploy to Production / deploy (push) Has been skipped
zola's image moved the binary from /bin/zola to /zola, outside PATH,
so the build stage failed with "zola: executable file not found"
after the Renovate bump to 0.23.6 (deploy run 411).

Assisted-by: Claude:opus-5-5
2026-11-13 02:06:46 +04:00
558e798d59 deps: Update ghcr.io/getzola/zola Docker tag to v0.23.6
All checks were successful
Test / check (push) Successful in 5s
2026-11-12 21:48:20 +00:00
a4b677f898
blog: Zola site, nginx image, Forgejo deploy pipeline
All checks were successful
Build and Deploy to Production / check (push) Successful in 9s
Build and Deploy to Production / build (push) Successful in 25s
Build and Deploy to Production / deploy (push) Successful in 36s
2026-07-16 19:51:31 +04:00