action-setup v6 renders invalid YAML file

[openscript]

After updating from v5 to v6 pnpm install --frozen-lockfile isn't successful anymore, because it seems something is modifying the pnpm-lock.yaml and renders it invalid.

> pnpm exec nx run-many --nx-bail --target=build --parallel 10 --output-style stream


 NX   Failed to parse pnpm lockfile

Please open an issue at `https://github.com/nrwl/nx/issues/new?template=1-bug.yml` and provide a reproduction.

Original error: expected a single document in the stream, but found more


YAMLException: expected a single document in the stream, but found more
    at load (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/@zkochan+js-yaml@0.0.7/node_modules/@zkochan/js-yaml/lib/loader.js:1722:9)
    at parseAndNormalizePnpmLockfile (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/plugins/js/lock-file/utils/pnpm-normalizer.js:48:36)
    at parsePnpmLockFile (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/plugins/js/lock-file/pnpm-parser.js:23:73)
    at getPnpmLockfileNodes (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/plugins/js/lock-file/pnpm-parser.js:29:18)
    at getLockFileNodes (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/plugins/js/lock-file/lock-file.js:53:59)
    at internalCreateNodes (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/plugins/js/index.js:53:79)
    at /home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/project-graph/plugins/utils.js:10:33
    at Array.map (<anonymous>)
    at createNodesFromFiles (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/project-graph/plugins/utils.js:8:35)
    at exports.createNodesV2 (/home/runner/work/sparkium/sparkium/node_modules/.pnpm/nx@22.6.5/node_modules/nx/src/plugins/js/index.js:27:51)


 NX   Failed to process project graph.

Pass --verbose to see the stacktraces.

 ELIFECYCLE  Command failed with exit code 1.
Error: Process completed with exit code 1.

[zkochan]

pnpm v11 will sometimes write two yaml documents into "pnpm-lock.yaml". The first one related to the pnpm version resolution and config dependencies.

[openscript]

I see, but pnpm v11 isn't stable yet?

[zkochan]

So action-setup@v6 uses pnpm v11 and I guess it updates the lockfile and then pnpm v10 fails? but the latest pnpm v10 can work with the lockfile that has two documents. If nx fails, they should also add support.

[sondr3]

@zkochan do I understand it correctly then that action-setup@v6 only supports the unreleased v11? #225, #227 and #226 (plus this one) all report errors from existing workflows upgrading from v5, and the release notes only mention "Added support for pnpm v11", not dropping support for v10. It's quite disruptive at the moment, I have ~40 dependabot PRs that are all failing at work because of this.

[n3dst4]

@sondr3 action-setup@v6 does also support the latest pnpm v10. I just updated to pnpm 10.33 and the error about "expected a single document in the stream" goes away. I can't speak for nx, I don't use it.

As per @zkochan's comment:

but the latest pnpm v10 can work with the lockfile that has two documents

The release notes could have been more explicit.