fix(ci): install zensical in the auto-update linters container - #8901
Merged
Conversation
build.sh builds the documentation site with `zensical build` since the MkDocs to Zensical migration (#8848), but entrypoint.sh still installed the MkDocs stack (mike, mkdocs-material, mkdocs-glightbox) before running it. The Auto-Update Linters job has therefore failed with `build.sh: line 20: zensical: command not found` (exit code 127) on every run since 2026-09-04, after the linter versions and the docs had already been regenerated, so no update pull request was ever created. Swap the three unused MkDocs packages for zensical, keeping the list in sync with .config/python/dev/requirements.txt as its header asks.
nvuillam
requested review from
Kurt-von-Laven,
bdovaz and
echoix
as code owners
September 5, 2026 09:34
Contributor
✅
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Problem
The Auto-Update Linters workflow has failed on every run since the MkDocs → Zensical migration:
Failing runs: 33835656037, 33851245685, 33929280561, 33948123307.
build.shbuilds the documentation site withzensical buildsince the migration, butentrypoint.shstill installed the MkDocs stack (mike,mkdocs-material,mkdocs-glightbox) before calling it. The failure happens at the very last step, after the linter versions and the docs have already been regenerated — so the job never reached the "Create Pull Request" step and no linter version update PR has been opened for the last 4 days.Fix
Swap the three now-unused MkDocs packages for
zensicalin theUPGRADE_LINTERS_VERSIONbranch ofentrypoint.sh, keeping the list in sync with.config/python/dev/requirements.txtas its header asks.zensicalpublishes amusllinux_1_2_x86_64abi3 wheel and depends only on pure-Python packages, so it installs cleanly on thepython:3.14-alpinebase image.Other post-migration checks
Swept the repository for other leftovers of the migration:
entrypoint.shwas the only remaining place installing or invoking MkDocstest-docs.yml,build-deploy-docs.yml,deploy-RELEASE.ymlandbuild-command.ymlall install.config/python/dev/requirements.txt, which pinszensical==0.0.57— all greensite/search/search_index.json(the MkDocs-only search index)mkdocs.ymlreferences inbuild.pyare expected: Zensical reads that configuration file unchanged