You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release notes for npm@12.0.0 still incorrectly state:
unknown configs in .npmrc, unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning.
This statement is incorrect and is not aligned with the updated CHANGELOG 12.0.0 which now states:
unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning. (Unknown .npmrc configs still warn by default; opt into erroring with the new strict-npmrc config.)
Suggestion
Correct also the release notes npm@12.0.0 concerning the description of handling unknown configs in .npmrc.
Note that this is not addressable through a PR. It requires direct write access to the repo in order to edit a release note manually.
The incorrect release notes content is linked to nodejs/node#66212 which promotes npm@12.1.0 to Node.js. This is misleading on a major functional change.
Activity
reggi commentedon Jul 29, 2026
this should update today with a patch to 12
MikeMcC399 commentedon Aug 6, 2026
Not fixed in https://github.com/npm/cli/releases/tag/v12.0.0
MikeMcC399 commentedon Sep 23, 2026
The incorrect release notes content is linked to nodejs/node#66212 which promotes npm@12.1.0 to Node.js. This is misleading on a major functional change.
It should be possible for a maintainer to simply edit https://github.com/npm/cli/releases/tag/v12.0.0 manually.