"nx migrate 22" resolves always to latest version under npm@12.0.2

[MorfMichael]

Current Behavior

If i want to migrate an v21 nx monorepo with npm@12.0.2 i always get the following error:
NX Fetching nx@22.7.8 resolved to version 23.1.1. Check for registry, override, or minimum-release-age configuration that hides the requested version.
With a npm@11.19.0 it works.

Expected Behavior

With npm@12.0.2 it should also be possible to migrate one major version at a time.

GitHub Repo

No response

Steps to Reproduce

1. npm install -g npm@12.0.2
2. npx create-nx-monorepo@21.6.11 (Angular)
3. npx nx migrate 22

Nx Report

Node           : 24.18.0
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 12.0.2

nx                     : 21.6.11
@nx/js                 : 21.6.11
@nx/eslint             : 21.6.11
@nx/workspace          : 21.6.11
@nx/angular            : 21.6.11
@nx/devkit             : 21.6.11
@nx/eslint-plugin      : 21.6.11
@nx/module-federation  : 21.6.11
@nx/rspack             : 21.6.11
@nx/web                : 21.6.11
@nx/webpack            : 21.6.11
typescript             : 5.9.3
---------------------------------------
Community plugins:
angular-eslint : 20.7.0
---------------------------------------
Cache Usage: 0.00 B / 47.48 GB

Failure Logs

NX   Fetching nx@22.7.8 resolved to version 23.1.1. Check for registry, override, or minimum-release-age configuration that hides the requested version.

Package Manager Version

npm@12.0.2

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

I didn't found any npm option which helped out on this one. So maybe somebody can help out. Thanks.

[AgentEnder]

Triage notes — automated triage, reviewed before posting.

Reproduced on Linux with the global npm as the only variable — one create-nx-workspace@21.6.11
workspace, copied so both arms run the same tree:

npm 11.19.0 -> nx migrate 22 succeeds, fetches nx@22.7.8, writes migrations.json
npm 12.0.2  -> nx migrate 22 fails, no migrations.json, package.json untouched

The npm 12 arm fails earlier than the error you hit — in the provenance check rather than in version
resolution:

ProvenanceError: An error occurred while checking the provenance of nx@latest.
Error: No attestation URL found
    at ensurePackageHasProvenance (nx/src/utils/provenance.js:28:19)
    at async nxCliPath (nx/src/command-line/migrate/migrate.js:1210:5)

Running npm view nx@latest --json --silent directly under npm 12.0.2 does return
dist.attestations.url, so the registry data is intact and the array-vs-object shape difference is
already handled. npm 12 additionally prints npm notice run … lines that npm 11 does not.

Confirms npm 12 is the trigger rather than anything in your workspace. Staying on npm 11 is the reliable
workaround for now; NX_SKIP_PROVENANCE_CHECK gets past the specific failure above, but it disables a
security check and won't help if you then hit the resolution error you originally reported.