Upgrade to Node 24 and add min-release-age#240
Open
judeallred wants to merge 1 commit into
Open
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Author
|
Note: Pre-existing CI failure (unrelated to this PR) The macOS build jobs fail during the post-job cleanup step — This is a repo-level infrastructure issue that predates this PR (the Node 24 upgrade + See SEC-1019 for full context on this effort. |
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.
Summary
min-release-age=1to.npmrc, telling npm to only resolve package versions published more than 1 day agomin-release-agefeatureTest plan
npm installworks correctlynpm ciworks correctlyMade with Cursor