## What / Why

#9729 reverts the `.npmrc` file-config half of the breaking change from
`979518d` (#9276): unknown `.npmrc` configs warn by default again, and
the new `strict-npmrc` config opts back into erroring. Unknown CLI flags
and abbreviations still throw.

The `12.0.0-pre.1` changelog entry still carried the original wording,
which claimed unknown `.npmrc` configs now throw. Since release-please
aggregates every prerelease `BREAKING CHANGE` note into the eventual
stable `v12.0.0` release notes, that stale line would surface
(inaccurately) in the 12.0.0 notes. This corrects the wording in place.

## Change

Edits the single breaking-changes bullet in the `## [12.0.0-pre.1]`
section:

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

## Notes

- Manual, targeted edit to an already-released, release-please-generated
section — this does not disturb release-please, which derives versions
from git tags + commit history and only prepends new sections.
Precedent: #8298 (`chore: add contributor to changelog entry`).
- Best merged alongside / after #9729 so the corrected note reflects
shipped behavior.

Co-authored-by: Copilot <[email protected]>

Co-authored-by: Copilot <[email protected]>

…tibility (#35)

The first real automated publish attempt (0.1.1-beta.2, all 9 packages)
failed identically for every package: EUNKNOWNCONFIG "Unknown cli flag:
--git-checks". Root cause confirmed via pnpm/pnpm#9646 and npm/cli#9276:
changeset publish always runs pnpm publish --no-git-checks for a pnpm
workspace, and pnpm has an open bug that mangles --no-git-checks into a
bare --git-checks before forwarding it to the underlying npm call. npm
<12 only warned about this; npm 12's breaking change (npm/cli#9276) made
unknown CLI flags a hard error, and the later walkback (npm/cli#9729)
explicitly excludes CLI flags from the softened behavior - so npm 12 will
always hard-fail here regardless of patch version. `npm install -g
npm@latest` was pulling in 12.0.1. Pinned to 11.18.0 instead - the newest
11.x release, well past the >=11.5.1 OIDC requirement, but before the
breaking change.

Nothing was actually published by the failed attempt (confirmed: all 9
packages failed identically before any registry write), so this is a
clean retry, not a partial-state cleanup.