chore: pin npm engine range to prevent unintended npm 12 upgrade#497
Merged
Conversation
tp-abtion
marked this pull request as ready for review
July 9, 2026 10:11
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the npm engine version constraint from '>=11.10.0' to '^11.10.0' in both package.json and package-lock.json. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
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.
npm 12 has just been released and Scalingo's build environment is not confirmed to handle it yet. This project's
engines.npmwas an unbounded>=11.10.0range, which would silently allow npm 12 to be resolved during a build even though thepackageManagercorepack pin already guards against it.Changes:
engines.npmto a caret range^11.10.0(excludes npm 12 until deliberately bumped), matching the existingpackageManagerpinNo dependency or behavior changes — purely bounding the npm version range to what's already installed.