Verify latest release

• I verified that the issue exists in the latest pnpm release

pnpm version

No response

Which area(s) of pnpm are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

Just have latest corepack installed and pnpm init and pnpm install in an empty folder

Reproduction steps

1. Open an empty folder.
2. pnpm init
3. pnpm install

(With latest corepack installed)

Describe the Bug

pnpm init creates devEngines.packageManager.version with a. semver range which corepack does not yet seem to support (Does it even intend to support it? They kinda want to pin the package manager with an hash in corepack no?)

Expected Behavior

pnpm init and pnpm install should work cleanly with corepack installed.

Which Node.js version are you using?

22.22.2

Which operating systems have you used?

• macOS
• Windows
• Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response