docs: close the CHANGELOG [Unreleased] section as 2.3.0 - #263
Merged
Merged
Conversation
The 2.3.0 release published and tagged the packages but left the entries under [Unreleased]. Move them under a 2.3.0 heading and point the link definitions at the new tag. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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 bookkeeping that the 2.3.0 release skipped. The packages were published and tagged
v2.3.0, butCHANGELOG.mdstill carried those entries under## [Unreleased].What this commit carries
## [Unreleased]stays in place and empty; the entries it held are now under## [2.3.0] — 2026-09-12, the same shape docs(changelog): cut 2.2.0 and pin the CDN snippets to it #254 left behind after 2.2.0.[Unreleased]compares fromv2.3.0, and a[2.3.0]line comparesv2.2.0...v2.3.0.No entry text was added, edited or removed. The diff is one heading and two link lines.
Not in this PR
The CDN pins in seven files still read
2.2.0: the rootREADME.md/README.ja.md,docs/sri.md/docs/sri.ja.md,packages/media-query/README.md/README.ja.mdandpackages/wcstack/README.md. Raising them now cannot change the npm READMEs already published for 2.3.0, so they belong in the next release's pre-release PR, before publish.🤖 Generated with Claude Code