chore: prepare the 2.4.0 release - #278
Merged
Merged
Conversation
Close the changelog as 2.4.0 and move the CDN pins to 2.4.0 before publish, since npm serves each README as it was at publish time. 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.
Prepares the minor release 2.4.0. Merge this before dispatching
release.ymlwithversion_type=minor.Changes
CHANGELOG.md[Unreleased]is closed as[2.4.0] — 2026-09-15, and an empty[Unreleased]stays above it.2.4.0, in the seven places the release pins (the same set as docs(changelog): cut 2.2.0 and pin the CDN snippets to it #254):README.mdREADME.ja.mddocs/sri.mddocs/sri.ja.mdpackages/wcstack/README.mdpackages/media-query/README.mdpackages/media-query/README.ja.mdWhy before publish
npm serves a package's README as it was at publish time. That is how 2.3.0 shipped with these pins still at 2.2.0. The
integrityvalues are placeholders (sha384-…), so pinning ahead of the digests is safe.Not touched
@wcstack/state@2.1.1example in the root README. It is outside the pin set, as it was in docs(changelog): cut 2.2.0 and pin the CDN snippets to it #254.packages/signals/CHANGELOG.md. Signals has not changed since v2.3.0, so there is no new heading.packages/vscode-wcs/CHANGELOG.md. The extension is released separately.No packages were added since v2.3.0, so no package needs a manual first publish.
🤖 Generated with Claude Code