Skip to content

docs: clarify npm 12 unknown-config breaking change in changelogs - #9805

Open
Hashim1999164 wants to merge 1 commit into
npm:latestfrom
Hashim1999164:docs/clarify-npm12-unknown-npmrc-changelog
Open

docs: clarify npm 12 unknown-config breaking change in changelogs#9805
Hashim1999164 wants to merge 1 commit into
npm:latestfrom
Hashim1999164:docs/clarify-npm12-unknown-npmrc-changelog

Conversation

@Hashim1999164

@Hashim1999164 Hashim1999164 commented Jul 26, 2026

Copy link
Copy Markdown

Summary

Fixes #9802.

Before the npm 12 stable cut, #9729 restored warn-by-default for unknown .npmrc keys (with strict-npmrc to opt into errors). #9733 updated the 12.0.0-pre.1 changelog bullet to match, but the aggregated stable 12.0.0 / @npmcli/config@11.0.0 breaking-change notes (and the config package's pre.1 note) still said unknown .npmrc configs throw.

That stale line also shipped in the published v12.0.0 GitHub release notes.

This aligns those changelog bullets with the corrected wording:

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.)

Maintainers may also want to refresh the published v12.0.0 release body to match; that cannot be updated via this PR alone.

References

The stable 12.0.0 / config 11.0.0 breaking-change notes still said
unknown .npmrc keys throw. That was reverted before the stable cut
(npm#9729): file configs warn by default again, with strict-npmrc to opt
into errors, while unknown CLI flags and abbreviations still throw.

Align the published changelog bullets with the corrected pre.1 wording
from npm#9733 so release notes match actual npm 12 behavior.

Fixes npm#9802
@Hashim1999164
Hashim1999164 requested review from a team as code owners July 26, 2026 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DOCS] Unknown configs throw error in npm@12.0.0 release notes

3 participants