chore(release): prepare v2.5.0

[mmcky]

Release prep for v2.5.0, following the same shape as #163.

Moves the [Unreleased] entries under ## [2.5.0] - 2026-09-05 with a headline blockquote, adds the compare link, re-points the [Unreleased] compare base at v2.5.0, and bumps package.json via npm version 2.5.0 --no-git-tag-version. template.yml is stamped by release.yml at build time.

Minor, not patch — the release removes a launch option and changes lecture typography, both user-visible.

What ships

Six PRs merged to main today, unreleased:

PR	Why it matters
#165	Icon-only search trigger matching the Sphinx toolbars, with the ⌘K hint moved into the dialog. Also fixes every toolbar control nesting a second <button> inside its real button or link, and gives icon-only controls an accessible name.
#166	Lecture headings in PT Serif on the Sphinx scale, self-hosted, mirrored into the critical CSS so the first WebKit paint is already serif at final size.
#167	Content links and cross-references in QuantEcon blue (#0072bc, WCAG AA) with the Sphinx hover colour, white in dark mode.
#168	"Back to top" no longer fades out of the page margin on load. A critical-CSS rule pins it hidden through the stylesheet gap the hydration recovery (#126) opens, which a mounted-gated transition could not do.
#169	The WebKit FOUC guard samples from an init script on DOMContentLoaded, ahead of the hydration recovery that restores the stripped critical <style>, and both cases assert their own preconditions.
#152	The Private JupyterHub launch option is removed and the launcher is a direct Colab anchor: no lecture repo ever configured a hub, and the URL it built was hardcoded to one hub layout.

After merge

Push the v2.5.0 tag to trigger release.yml:

git fetch origin main && git tag v2.5.0 origin/main && git push origin v2.5.0

Then consumers pinned at v2.4.0 can bump when convenient; nothing in this release is a fix they are blocked on.

🤖 Generated with Claude Code

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-05 03:46 UTC

[github-actions]

🎭 Visual regression results

 19 passed
 5 skipped

Details

 24 tests across 1 suite
 37.8 seconds
 7dc572f

Skipped tests

mobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › without JavaScript › drawer-opens-without-javascript
mobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › drawer-closes-when-search-opens
mobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › launch-colab
mobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › live-compute-toggle
mobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › live-compute-toggle-absent-without-thebe

[Copilot]

🔵 Needs a closer look

Although the mechanical changes are correct and follow the documented release process, cutting a release is a high-impact action that warrants final human sign-off.

Pull request overview

This is a mechanical release-preparation PR that cuts v2.5.0. It follows the manual release flow documented in CONTRIBUTING.md (curated Keep a Changelog entry + vX.Y.Z tag): the ## [Unreleased] entries are moved under a dated ## [2.5.0] - 2026-09-05 heading with a headline blockquote, the compare links are updated, and the package version is bumped. The release aggregates six merged-but-unreleased PRs (#165, #166, #167, #168, #169, #152) and is versioned minor because it removes the Private JupyterHub launch option and changes lecture typography — both user-visible.

Changes:

• Move the [Unreleased] changelog entries under ## [2.5.0] - 2026-09-05 with a headline summary, add the [2.5.0] compare link, and re-point [Unreleased] at v2.5.0...HEAD.
• Bump the package version from 2.4.0 to 2.5.0 in package.json and package-lock.json.
• template.yml is intentionally not bumped (stamped by release.yml at build time).

File summaries

File	Description
CHANGELOG.md	Adds the dated 2.5.0 section with the moved entries and headline blockquote; updates the footer compare links.
package.json	Bumps the project version field to 2.5.0.
package-lock.json	Bumps both project self-version fields to 2.5.0.

I verified: the release date matches today (not a future date), both compare links ([Unreleased]: v2.5.0...HEAD and [2.5.0]: v2.4.0...v2.5.0) are correct, all moved sections (Changed/Removed/Fixed/Dependencies) are intact, the remaining 2.4.0 strings in package-lock.json are unrelated third-party dependency versions, and the changes match the documented process in CONTRIBUTING.md:171-180. No issues found.

Review details

• Files reviewed: 2/3 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.