chore(release): prepare v2.3.1 - #149
Conversation
Move the [Unreleased] entries under ## [2.3.1] - 2026-08-26 with a headline blockquote, add the footer compare link, re-point the [Unreleased] compare base at v2.3.1, and bump package.json (npm version 2.3.1 --no-git-tag-version). template.yml is stamped by release.yml at build time. Two accuracy corrections ride along: - The #131 changelog entry claimed the visual suite passes against untouched baselines. That was true when written, but the @fontsource glyph metrics re-wrapped a line at the mobile viewport and #148 had to refresh the linux mobile-chrome baselines. The entry now says so. - PLAN.md open question 4 still named #117 as an open defect gating the cutover. It is fixed and ships here, as does #138. The paragraph now points at the live gate items and at the tracking issue #147. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
🎭 Visual regression resultsDetails
Skipped testsmobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › launch-colab |
There was a problem hiding this comment.
Pull request overview
This PR cuts release v2.3.1, a patch release that promotes two already-merged bug fixes (dead run buttons for code cells nested in directives, #137/#117; and 404'd KaTeX font assets in static builds, #139/#138) plus the Source Sans 3 self-hosting optimization (#140) from [Unreleased] into a dated changelog section. It follows the documented release flow in CONTRIBUTING.md: move [Unreleased] entries under a dated heading, add the compare footer link, re-point the [Unreleased] compare base, and bump package.json. It fits into the #147 parity-cutover effort by unblocking the live consumer (lecture-wasm), which is still pinned to the defective v2.3.0.
Changes:
- Move
[Unreleased]entries under## [2.3.1] - 2026-08-26, add the[2.3.1]compare link, and re-point[Unreleased]tov2.3.1...HEAD; also correct the #131 entry to note the linux mobile-chrome baseline refresh (#148). - Bump the version to
2.3.1inpackage.jsonandpackage-lock.json. - Update PLAN.md open-question 4 to reflect that #117/#138 are fixed and shipping, re-pointing the cutover gate at #114/#128/#87 and tracker #147.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CHANGELOG.md | Adds the dated 2.3.1 section with headline blockquote, corrects the Source Sans 3 baseline claim, and updates compare-link footer. |
| package.json | Bumps version to 2.3.1. |
| package-lock.json | Bumps the theme's own version fields to 2.3.1. |
| PLAN.md | Updates the cutover-gate description to reflect the shipped Phase 0 fixes and current gate items. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Cuts v2.3.1 — the release that makes the shipped parity surface actually correct. Both Phase 0 defects on the #147 cutover gate are fixed on
mainbut unreleased, so the live consumer (lecture-wasm) is still pinned to a v2.3.0 that ships dead run buttons and 404'd KaTeX fonts.What ships
{exercise}/{solution}/{note}were clickable but inert, and nested pre-baked outputs blanked once the kernel attachedmyst build --html, so maths fell back to system glyphs on every statically built site — and under abaseurl, including this repo's own PR previewsWhy 2.3.1 and not 2.4.0
Two bug fixes plus an asset-hosting optimization. No new features, no configuration surface added or changed, nothing breaking — consumers upgrade by bumping the pinned release URL in
site.templateand get identical rendered output, minus the defects. Semver puts an optimization under patch.The release move itself
Per CONTRIBUTING.md: the
[Unreleased]entries move under## [2.3.1] - 2026-08-26with a headline blockquote, the footer gains the compare link, andpackage.jsonis bumped vianpm version 2.3.1 --no-git-tag-version.template.ymlis deliberately untouched —release.ymlstamps itsversionfrompackage.jsonat build time.The
[Unreleased]compare base is re-pointed atv2.3.1. Worth flagging because the v2.3.0 prep (#133) missed exactly this and needed #134 to repair it.Two accuracy corrections riding along
@fontsourcebuild's glyph metrics re-wrapped a line at the mobile viewport and test: refresh linux mobile-chrome baselines after Source Sans 3 self-hosting #148 had to refresh the linux mobile-chrome baselines. The entry now says so, and scopes the "untouched" claim to desktop.Verification
npm run compileclean ·npm run test:unit20/20.After merge
Tag and push to trigger
release.yml:git tag v2.3.1 && git push origin v2.3.1🤖 Generated with Claude Code