[BUG]: NpmAuthenticateV0 generates obsolete strict, always-auth settings in .npmrc #21434
Description
New issue checklist
- I searched for existing GitHub issues
- I read pipeline troubleshooting guide
- I checked how to collect logs
Task name
NpmAuthenticateV0
Task version
0
Issue Description
When NpmAuthenticateV0 generates .npmc and later npm install is used with current node 24 LTS (24.11.0) with built-in npm 11.6.1 there are these warnings
npm warn Unknown user config "strict". This will stop working in the next major version of npm.
npm warn Unknown user config "always-auth". This will stop working in the next major version of npm.
Task NpmAuthenticate generates strict, always-auth settings, which are obsolete in current node, npm (see above).
There is no sense to generate these settings. User can add these into .npmrc himself if old npm/node is used.
Maybe it's breaking change, so removing in NpmAuthenticateV1?
Environment type (Please select at least one enviroment where you face this issue)
- Self-Hosted
- Microsoft Hosted
- VMSS Pool
- Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 24.04, Windows 11
Relevant log output
npm warn Unknown user config "strict". This will stop working in the next major version of npm.
npm warn Unknown user config "always-auth". This will stop working in the next major version of npm.Full task logs with system.debug enabled
No response