yeasy d705dfb631 fix(ci): make the Mermaid fail-closed guard actually fire ...

The guard added earlier could never trigger. tools/render_mermaid.py has no
nonzero exit path — its own docstring said "Exits 0 even if some/all fail
(non-fatal)" — so `if ! render_mermaid.py ...; then exit 1; fi` never ran its
body, and a build that rendered zero diagrams still passed. Reproduced by
running the script with no Chrome on PATH: it printed the fallback warning and
exited 0.

Adds a --strict flag that exits 1 when Chrome is missing or any diagram fails
to render, and passes it from every workflow invocation. The default stays
lenient so local mobile-reader builds keep working, which is what the exit-0
behaviour was actually for.

Verified both directions: with no Chrome, --strict exits 1 and the default
exits 0; against the real book with Chrome, --strict renders every diagram and
exits 0.

2026-07-23 07:40:28 -07:00

..

build_html_reader.py

ci: build and attach HTML reader to each release

2026-06-21 10:14:47 +08:00

prepare_pdf_sources.py

fix(content): correct verified technical facts across cgroups, namespaces, etcd and k8s sections

2026-07-10 06:13:27 -07:00

render_mermaid.py

fix(ci): make the Mermaid fail-closed guard actually fire

2026-07-23 07:40:28 -07:00

test_examples.py

fix(ci): attest releases and validate offline examples

2026-07-10 19:29:30 -07:00

test_prepare_pdf_sources.py

fix(ci): harden publishing and validate examples

2026-07-10 19:29:30 -07:00

verify_artifacts.py

fix(ci): harden publishing and validate examples

2026-07-10 19:29:30 -07:00