Repository navigation
fix: require patched Node runtimes for development and CI - #3
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
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.
Development installs previously accepted Node runtimes predating the October security fixes, and workflows bootstrapped pnpm or ran release metadata scripts before selecting Node. Require Node >=22.23.4 <23 or >=24.22.1 <25 for development, pin Node 24.22.1, and select it before package-manager setup and Node scripts in CI, publishing, and oracle workflows. Update the checkout, Node setup, and pnpm setup actions while retaining immutable SHA pins.
Validation with Node 24.22.1 and pnpm 9.15.0: