[mmcky]

Cuts v0.19.0. It carries wave 7's restore-gh-pages (#306) and the build-lectures jupyter warning guard (#307), and the sphinx-exercise bump in both images (#312). v0 is on v0.18.0. It moves to v0.19.0 only after the gate passes this release, and after the canary restore below is green.

What's in it

Change	PR	Issue
A new action, restore-gh-pages, and templates/restore.yml: put a GitHub Pages site back from the archive, checksum and manifest that publish-gh-pages attaches to a release, without a build	#306	#27
⚠️ BREAKING build-lectures: a jupyter build under -W --keep-going, the default extra-args, fails on its warnings, as the other builders do	#307	#300
Container images: sphinx-exercise 1.2.2 in both images	#312	none

One entry is marked ⚠️ BREAKING: #307. The three QuantEcon lecture repositories whose jupyter build warned have dropped the entry that caused it (QuantEcon/lecture-python.myst#1123, QuantEcon/lecture-python-programming#659 and QuantEcon/lecture-python-advanced.myst#409). With the guard on main, the lecture matrix then passed on all eight legs (run 42985241521).

Also merged since v0.18.0, docs or CI only, with no entry: #308 (PLAN), #309 (the harness's restore round trip) and #279 (the CHANGELOG footer).

Changes in this PR

File	Change
CHANGELOG.md	## [0.19.0] - 2026-11-11 below an empty ## [Unreleased], plus the entry #312 owed, under Changed, as #293's was
docs/dev/PLAN.md	The release line: the latest release is v0.19.0, and @v0 is on v0.18.0 until the gate has passed it

The date is today's in UTC, as for v0.18.0. If the merge slips past 00:00 UTC, I'll move it to 2026-11-12 first.

What I checked

• The CHANGELOG: the diff adds 10 lines and deletes none, and everything from ## [0.18.0] down is byte-identical to main. Every PR merged since v0.18.0 has its entry, or is docs- or CI-only.
• generate-docs.py --check: 23 files current.
• No other page names a release as the current one.

Staging, after the tag

As CONTRIBUTING's Staged Releases says:

1. The release gate: gate.yml on the canary's main with candidate=v0.19.0, self-test off. It must be green, with each site serving the marker for the release commit. The gate fixture's jupyter build logs no warning, so fix(build-lectures): a jupyter build fails on its warnings under -W --keep-going (#300) #307 changes nothing there.
2. The gate's build-fails self-test, once, for fix(build-lectures): a jupyter build fails on its warnings under -W --keep-going (#300) #307. It must go red, now at the jupyter build's build step, with the annotation "jb build exited 0, but the jupyter build logged 2 warning(s)…". Until now only the error-output check caught the raised cell. The pdflatex and html checks after it report figures.md cell 3 with the cause "unknown: no later cell was to run", since the raising cell is the fixture's last. That is expected.
3. What the gate doesn't reach: restore-gh-pages. After the gate's run has replaced the canary's Pages site, a canary pull request puts templates/restore.yml, pinned to @v0.19.0, on the canary's main. Dispatched there with tag: publish-staged-v0180, the release kept from v0.18.0's staging for this check, it must deploy that archive, and the Pages URL must serve its index.html, compared by content. It is the action's first run against the real releases API, and the first real Pages deploy of a restored site. Afterwards the publish-staged-v0180 tag and release are deleted.

Container images don't go through the canary. #312's images were promoted on 2026-11-11 and are already :latest.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WT8bMbZoC2dpGt3sPyBjyd

[Copilot]

Note

Copilot was unable to complete this review at the selected tier due to model policy or plan restrictions.

🟢 Approval recommended

The changes are straightforward documentation updates to the changelog and release plan with no remaining concerns or unresolved items indicated in the provided review context.

No open issues 🎉

What changed in this PR

Prepares the repository for the v0.19.0 release by updating release documentation and the developer plan to reflect the new version.

Changes:

• Add a dated 0.19.0 section to the changelog and record the owed #312 entry under Changed.
• Update the dev plan to mark v0.19.0 as the latest release while keeping @v0 on v0.18.0 until the release gate passes.

File	Description
docs/​dev/​PLAN.md	Updates the release status line to identify v0.19.0 as the latest release and clarifies that @v0 remains on v0.18.0 until the gate passes.
CHANGELOG.md	Adds a 0.19.0 release section dated 2026-11-11 and includes the #312 container dependency bump entry under Changed.

_{Review effort: Balanced}