ci: sync ncrypto from latest Node release, update script#45
Merged
panva merged 1 commit intonodejs:mainfrom May 8, 2026
Merged
ci: sync ncrypto from latest Node release, update script#45panva merged 1 commit intonodejs:mainfrom
panva merged 1 commit intonodejs:mainfrom
Conversation
Signed-off-by: Filip Skokan <panva.ip@gmail.com>
jasnell
approved these changes
May 8, 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
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.
Updates the Node ncrypto sync automation to sync from the latest stable Node.js release by default.
The sync script now resolves the latest stable Node.js release tag from
nodejs/nodetags when nonode_refis provided, while still allowing a specific release tag/ref to be passed manually. Prerelease tags are ignored.The workflow now uses the resolved Node.js version in the sync branch name, commit subject, PR title, and PR body. It also avoids opening a PR when only
.github/sync-node-ncrypto.jsonwould change.PR handling was tightened so existing open sync PRs are updated, closed PRs are not reused, first-time branch creation does not emit a noisy fetch failure, and conflict-producing syncs are opened or kept as draft PRs with the conflicting files listed in the description.