[rush] Seeing several "Unknown env config" warnings from npm while publishing packages

[kgetz-arista]

Summary

Seeing this while publishing packages:

npm warn Unknown env config "cache-dir". This will stop working in the next major version of npm.
npm warn Unknown env config "state-dir". This will stop working in the next major version of npm.
npm warn Unknown env config "store-dir". This will stop working in the next major version of npm.
npm warn Unknown env config "workspace-dir". This will stop working in the next major version of npm.
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.

Repro steps

1. 'rush-pnpm publish --no-git-checks -r

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question	Answer
@microsoft/rush globally installed version?	5.169.3
rushVersion from rush.json?	5.169.3
pnpmVersion, npmVersion, or yarnVersion from rush.json?	pnpm@10.32.1 -->
(if pnpm) useWorkspaces from pnpm-config.json?	true
Operating system?	Linux
Would you consider contributing a PR?	No
Node.js version (node -v)?	24.12.0

[iclanton]

This should have been fixed in Rush 5.167.0 (https://github.com/microsoft/rushstack/blob/main/apps/rush/CHANGELOG.md#51670). See PR: #5574.

Do you have a repro repo?

[iclanton]

Actually, is there a reason you're using rush-pnpm publish ... instead of rush publish?

[kgetz-arista]

Actually, is there a reason you're using rush-pnpm publish ... instead of rush publish?

We don't use rush change (too much of an inconvenience) so I believe that precludes us from using rush publish.

[iclanton]

@kgetz-arista - I'm pretty sure you can use rush publish without Rush's version management. I'll just publish the current state of all publish-enabled projects.

[kgetz-arista]

Okay interesting, I'll have to give that a try the next time we publish.

[kgetz-arista]

I'm pretty sure you can use rush publish without Rush's version management. I'll just publish the current state of all publish-enabled projects.

@iclanton I'm not seeing this behavior. If I run rush publish --publish, nothing happens. Nothing is packaged, nothing is published.