docs(changelog): repair the [Unreleased] section for the next release - #132
Merged
Conversation
release.yml builds a release's notes from that version's changelog section, so entries in the wrong place are silently dropped from the next release: - The git-history entry (#83, merged 2026-08-19) sat inside the already-tagged [2.2.0] (2026-07-16) section. Moved to [Unreleased] and given its missing PR link. - The two CDN-removal changes had no entries at all. Added under Changed (#125, self-hosted KaTeX + vendored jupyter-matplotlib) and Removed (#124, Font Awesome). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates CHANGELOG.md so release.yml will correctly pick up all intended entries for the next release notes, by ensuring recent changes are listed under [Unreleased] rather than an already-tagged release section.
Changes:
- Moved the git-history entry (#83) from the
[2.2.0]section into[Unreleased] → Added, including the missing PR link. - Added missing changelog entries for the CDN-related changes: self-hosted KaTeX/jupyter-matplotlib stylesheets (#125) under
[Unreleased] → Changed, and Font Awesome stylesheet removal (#124) under[Unreleased] → Removed.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
|
Contributor
🎭 Visual regression results
Details
Skipped testsmobile-chrome › theme.spec.ts › QuantEcon theme — visual regression › launch-colab |
This was referenced Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
release.ymlbuilds a release's notes from that version's section ofCHANGELOG.md, so entries in the wrong place are silently dropped from the next release's notes. Two problems had accumulated, both of which would have made the eventual v2.3.0 notes incomplete:The git-history entry (feat: git history in lecture headers (PLAN Phase 1) #83) sat inside the already-tagged
[2.2.0]section. The PR merged on 2026-08-19, a month after 2.2.0 was tagged (2026-07-16), but its changelog entry had been written into the 2.2.0 section. Moved verbatim to[Unreleased] → Added, and given the PR link it was missing.The two CDN-removal changes had no entries at all. Added under
[Unreleased] → Changedfor perf: self-host KaTeX and jupyter-matplotlib stylesheets #125 (KaTeX and jupyter-matplotlib stylesheets served from the site's own origin — the mainland-China reachability motivation is summarised) and[Unreleased] → Removedfor perf: drop the render-blocking Font Awesome stylesheet #124 (the render-blocking Font Awesome stylesheet, which nothing used).No code changes —
CHANGELOG.mdonly.🤖 Generated with Claude Code