v9.0.5 release ignores "frozen-lockfile" flag

[jekanik]

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)

Lockfile

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

No response

Reproduction steps

npm i -g pnpm@9.0.5
pnpm install --frozen-lockfile

Describe the Bug

Lockfile is updated even if "frozen-lockfile" flag is provided.

Expected Behavior

Lockfile is not changed

Which Node.js version are you using?

18.19.0

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

[zkochan]

We'll fix it.

It isn't an urgent issue as --frozen-lockfile happens mostly in CI envs, where an update to the lockfile will just be ignored.

[jekanik]

@zkochan thanks for response.
In some Teamcity builds we analyse used dependencies by parsing lockfile. And this scenario is started to fall after update to 9.0.5 :)
For now, we rollbacked to 9.0.4.

[AndreaPontrandolfo]

This issue is also present in 9.0.4 and is breaking our builds.
We had to revert back to 8.x.x.

[zkochan]

🚢 9.0.6