-
Notifications
You must be signed in to change notification settings - Fork 660
Open
Description
Summary
rush update (and other Rush commands) displays multiple warnings when using the latest versions of Node, npm, Rush, and pnpm together.
Repro steps
Upgrade to the latest versions of Node, npm, Rush, and pnpm together and run rush update.
Expected result: No warnings
Actual result:
This warning appears when running any Rush command:
Your version of Node.js (24.12.0) has not been tested with this release of Rush. Please consider installing a newer version of the "@microsoft/rush" package, or downgrading Node.js.
These warnings appear when running rush update:
Running "npm install" in C:\Users\kgetz\.rush\node-v24.12.0\pnpm-10.27.0
(node:26424) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
(Use `node --trace-deprecation ...` to show where the warning was created)
npm warn Unknown project config "email". This will stop working in the next major version of npm.
npm warn Unknown project config "publish-branch". This will stop working in the next major version of npm.
Details
Rush seems to be lagging behind the rest of the web dev community. Node 24 has been out since May of last year and has been the official LTS version since October.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
| Question | Answer |
|---|---|
@microsoft/rush globally installed version? |
5.165.0 |
rushVersion from rush.json? |
5.165.0 |
pnpmVersion, npmVersion, or yarnVersion from rush.json? |
pnpm@10.27.0 |
(if pnpm) useWorkspaces from pnpm-config.json? |
true |
| Operating system? | Windows 11 |
| Would you consider contributing a PR? | No |
Node.js version (node -v)? |
24.12.0 |
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Needs triage