chore(release): prepare v2.6.0 - #189
Conversation
|
There was a problem hiding this comment.
🟢 Approval recommended
The changes are a mechanical, low-risk release bump that exactly follows the documented CONTRIBUTING.md flow, with version numbers, changelog structure, compare links, and date all verified consistent.
Pull request overview
This PR prepares the v2.6.0 release, following the manual release flow documented in CONTRIBUTING.md. It bundles three already-merged parity phases (Phase 3 code/text palette via #171, and Phases 4–5 i18n/RTL plus the translator credit via #174) into a single tagged release. No product code changes — this is purely release bookkeeping.
Changes:
- Move the
## [Unreleased]CHANGELOG entries under a new## [2.6.0] - 2026-09-10heading, add the[2.6.0]compare link, and re-point[Unreleased]tov2.6.0...HEAD. - Bump the version to
2.6.0inpackage.jsonandpackage-lock.json(both fields). - Update
PLAN.mdto mark Phases 3, 4 and 5 as shipped in v2.6.0.
File summaries
| File | Description |
|---|---|
| CHANGELOG.md | Moves Unreleased entries under ## [2.6.0] - 2026-09-10; adds/updates compare links, matching the documented flow and the release.yml extraction format. |
| package.json | Version bump 2.5.0 → 2.6.0, the source of truth the release workflow stamps into the bundle. |
| package-lock.json | Mirrors the version bump in both the top-level and root-package fields. |
| PLAN.md | Marks Phases 3–5 as shipped in v2.6.0 and updates the shipped-state narrative. |
I verified: version consistency across package.json/package-lock.json; the CHANGELOG heading format matches the awk guard in release.yml (## [2.6.0]); the compare links are correct; the release date 2026-09-10 equals today (not a future date); template.yml is correctly left unbumped since release.yml stamps it from package.json; and remaining 2.5.0 references are unrelated dependency versions or historical changelog links.
Review details
- Files reviewed: 3/4 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.
🎭 Visual regression resultsDetails
Skipped testsmobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › without JavaScript › drawer-opens-without-javascript |
Release prep for v2.6.0, per the flow in CONTRIBUTING.md. Bundles the three parity phases that landed since v2.5.0.
Included
qetheme_code_style) andseoul256text colours for emphasis, strong text and definition termshreflangalternates from thelanguages/current_languagesite optionsenable_rtl, withcurrent_languagesetting the documentlangtranslators/translators_label, with a per-page overridetemplate.yml(lists carried as YAML block strings)#175 (a comment correction) needs no entry.
What this PR changes
CHANGELOG.md: the Unreleased entries move under## [2.6.0] - 2026-09-10, the compare link is added, and the Unreleased link now compares fromv2.6.0.package.json/package-lock.json: version 2.6.0.template.ymlis stamped by the release workflow.PLAN.md: Phases 3, 4 and 5 marked as shipped in v2.6.0.After merge
Tag the merge commit and push the tag;
release.ymlbuilds the bundle and publishes the GitHub Release with this changelog section as the notes:Consumers pin releases explicitly, so nothing moves until a lecture repo bumps its
site.templateURL.🤖 Generated with Claude Code