You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the design note .qe/dev/log/2026-11-16-product-builds-design.md (#335), item 1. QuantEcon/lectures' product builds (QuantEcon/project-monorepo#77) need the engine as a matrix axis from the start: Jupyter Book 1 publishes until the engine switch, and a mystmd leg runs beside it, non-publishing and continue-on-error.
build-lectures runs only jb build, and its checks are Jupyter Book 1's: -n and -W, the warnings log of a jupyter build, and the error outputs read from the execution cache.
Proposed: an engine input, jb1 by default (today's behaviour). With myst, the action runs myst build with the builder's flag (--html, --pdf, --ipynb) from the folder that holds myst.yml, and its chapter says which of the action's checks apply on that engine. The input can ship before every check has a mystmd equivalent, as long as the chapter says which do. One pull request, with the chapter, a harness job, a CHANGELOG entry and a staged release.
Activity