older global pnpm dies on "unexpected event: expected string scalar" before it even switches versions

Feb 12, 2025
45
0
0
bump the global pnpm first (pnpm self-update), thats basically the fix. 12.9.x reads pnpm-workspace.yaml before handing off to the packageManager version, and the lockfile.includeResolutionSettings block added in 12.10 is an object it doesnt get:

Error: × load configuration
╰─▶ Failed to parse pnpm-workspace.yaml at .../repro/pnpm-workspace.yaml: error: line 2 column
3: unexpected event: expected string scalar

calling the 12.10.1 binary directly works too. the merged fix only helps newer versions, old globals stay broken