Verify latest release

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

pnpm version

v11.0.0-alpha.2

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

CLI

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

No response

Reproduction steps

If optimisticRepeatInstall is set, running pnpm patch followed by pnpm patch-commit causes a no-op.

This can be reproduced in the pnpm repo with:

❯ pnpm patch @yarnpkg/parsers

❯ pnpm patch-commit '/Users/gluxon/Developer/pnpm/node_modules/.pnpm_patches/@yarnpkg/parsers@3.0.3'
pnpm                                     |  WARN  The field "pnpm.overrides" was found in /Users/gluxon/Developer/pnpm/pnpm/package.json. This will not take effect. You should configure "pnpm.overrides" at the root of the workspace instead.
Already up to date

Describe the Bug

The optimistic repeat install thinks the lockfile is up to date and prints "Already up to date".

Expected Behavior

A new installation should run.

Which Node.js version are you using?

v25.2.1

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