release: nodejs-mobile 24.20.0-0 - #12
Merged
Merged
Conversation
Updated changelog to summarize notable changes for version 24.20.0-0.
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
2 participants
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.
Automated release PR for nodejs-mobile 24.20.0-0 (see docs/RELEASING.md).
expected-tree.txtre-anchored viaprepare.shrelease-notescheck fails while the_TODO_stub is there)Merging makes the version-of-record untagged-at-HEAD, so the merge push runs the full gate chain (build matrix, boot smokes, curated and full device suites, real devices) and, if everything is green, tags
v24.20.0-0and publishes the prerelease. PR checks do not run on this bot-pushed branch — your CHANGELOG commit is what starts them, and it is also what clears therelease-notescheck. Nothing publishes unverified either way (all gates re-run on the merge push).