publishing: complete the pinned toolchain; build.sh self-heals missing plugins
requirements.txt pinned only mkdocs-material, so a cold venv lacked mkdocs and mkdocs-redirects — the exact gap that silently stalled the auto-deployer today. build.sh now gates every build on the venv: it verifies the pinned requirements (installing anything missing or off-version — fast local no-op when current) and fails loudly if mkdocs.yml configures a plugin that requirements.txt does not pin. --check-only runs the gates without building, for use as the poller's pre-deploy check.
This commit is contained in:
1 parent
027cf596ef
commit
1691f79621
2 files changed
+139
-12
No files matched your search
@@ -1,3 +1,16 @@
|
||||
# Pinned build toolchain for the documentation site.
|
||||
# Reproducible: `pip install -r publishing/requirements.txt && mkdocs build`
|
||||
#
|
||||
# EVERY package the build needs must be pinned here — this is not decoration:
|
||||
# on 2026-11-12 mkdocs-redirects was missing from the auto-deployer's venv and
|
||||
# the build failed on every poll cycle with a plugin error while the site kept
|
||||
# serving the previous build, with nothing telling anyone. build.sh now checks
|
||||
# this list against the venv before every build and installs anything missing
|
||||
# (self-heal), and it fails loudly if mkdocs.yml configures a plugin this file
|
||||
# does not pin.
|
||||
#
|
||||
# Reproducible cold build:
|
||||
# python3 -m venv .venv-docs \
|
||||
# && .venv-docs/bin/pip install -r publishing/requirements.txt
|
||||
mkdocs==1.6.1
|
||||
mkdocs-material==9.8.0
|
||||
mkdocs-redirects==1.2.3
|
||||
Reference in new issue
Block a user