Repository navigation
release: prepare Node 24.22 snapshot prerelease with English notes - #11
Merged
Merged
Conversation
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.
Prepare the Node 24 line to publish the reviewed Node.js 24.22.0 proposal as an explicit GitHub prerelease.
Backport the existing Node 26 snapshot controller: both manual workflows require the exact pinned upstream SHA, the controller verifies the official version header, and the reviewed release markers must match. Publication keeps every build, host, smoke, curated and full-device gate. Package all four SDK archives and SHA256SUMS before tagging, and publish a verified source snapshot with recipe/upstream provenance.
Use English release titles and notes. Explain the full-ICU size increase and the retained danmu lite profile. Runtime source, flavor settings and the expected product tree are unchanged.
Validation: 22 release-control regressions passed, including the Node 24 snapshot and cross-line rejection cases; official upstream/repository preflight selected unused version 24.22.0-0; YAML, workflow input propagation, shell syntax and release-note validation passed. The complete runtime Build and Verify for upgrade PR #10 already passed. The explicit prerelease run will execute all publication gates again.