Support for pnpm v11 & v12?

[MikeMcC399]

The README states:

Important

This action has a successor: pnpm/setup.

For pnpm v11 and newer, use pnpm/setup instead. It downloads pnpm's self-contained release binary (no Node.js or npm required) and can install a JavaScript runtime (Node.js, Bun, or Deno) in the same step, replacing actions/setup-node.

pnpm/action-setup remains the action to use for installing pnpm v10 and older. See Migrating to pnpm/setup below.

Does this mean pnpm/action-setup is deprecated for use with pnpm v11 and the future v12, or will it continue to be supported?

pnpm/setup does not replace all the functionality of actions/setup-node, so we'll want to continue using actions/setup-node.

[zkochan]

doesn't pnpm/setup work with actions/setup-node?

[MikeMcC399]

doesn't pnpm/setup work with actions/setup-node?

I don't know, since I haven't tried it and the documentation for pnpm/setup doesn't show an example together with actions/setup-node.

[zkochan]

Well, the documentation also doesn't say that actions/setup-node doesn't work.

[johnmurphy01]

Not related to setup-node but it's important to note that if you are on pnpm v11, pnpm/action-setup doesn't work but also moving to pnpm/setup has its own challenges as the official release doesn't work for pnpm v11. As of right now, you have to pin the action to commit hash 6523ce966bcf7a1061ce6401e5c6e0b60466bd31(pnpm/setup@6523ce9)

[zkochan]

I don't currently use this action, so I don't know if it stopped working. But there was some fix merged: #277 recently. How doesn't it work? What is the issue?

And how does pnpm/setup not work? it is used in the pnpm monorepo. Seems to work.

[johnmurphy01]

I don't currently use this action, so I don't know if it stopped working. But there was some fix merged: #277 recently. How doesn't it work? What is the issue?

And how does pnpm/setup not work? it is used in the pnpm monorepo. Seems to work.

Could be isolated to v11.13.0, I'm not sure. But if you try to use pnpm/action-setup, it throws an error:

Running self-installer...
  
  added 1 package, and audited 2 packages in 1s
  
  1 package is looking for funding
    run `npm fund` for details
  
  found 0 vulnerabilities
  Checking for updates...
  [ERR_PNPM_BROKEN_PNPM_RELEASE] pnpm v11.13.0 is a broken release and cannot be installed
  
  Its "@pnpm/exe" build shipped without a binary and does not run. Even where it does run, pinning it would break everyone on the project who uses "@pnpm/exe", because the pin is shared. Choose another version, or run "pnpm self-update latest".

and if you swap to pnpm/setup@v1 you get:

Installation Completed!
No runtime requested (no `runtime` input and no `devEngines.runtime` in package.json). Skipping runtime install.
Restoring cache...
  /home/runner/setup-pnpm/node_modules/.bin/bin/pnpm store path --silent
  /home/runner/setup-pnpm/node_modules/.bin/bin/../global/v11/844-19fc81b4261/node_modules/@pnpm/exe/pnpm: 1: This: not found
  Error: The process '/home/runner/setup-pnpm/node_modules/.bin/bin/pnpm' failed with exit code 127
  Error: Error: The process '/home/runner/setup-pnpm/node_modules/.bin/bin/pnpm' failed with exit code 127
      at t._setResult (/home/runner/work/_actions/pnpm/setup/v1/dist/index.js:58:19711)
      at t.CheckComplete (/home/runner/work/_actions/pnpm/setup/v1/dist/index.js:58:19298)
      at ChildProcess.<anonymous> (/home/runner/work/_actions/pnpm/setup/v1/dist/index.js:58:18286)
      at ChildProcess.emit (node:events:509:28)
      at maybeClose (node:internal/child_process:1124:16)
      at Socket.<anonymous> (node:internal/child_process:481:11)
      at Socket.emit (node:events:509:28)
      at Pipe.<anonymous> (node:net:351:12)

pinning pnpm/setup to the aforementioned commit hash fixes this

[MikeMcC399]

@johnmurphy01

If you have issues with either action, please take them to separate issue threads.

The topic for this issue was only intended to be about the support status and future of pnpm/action-setup and whether users are forced to migrate the action if they migrate to pnpm v12 when it is released.

[aritma-sondr3]

The whole migration from v10 to v11 was and is quite frankly a mess, this action was left broken for several weeks after the v6 release and the new pnpm/setup is absolutely not a replacement for this action, the fact that it is missing support for alternate/private registries, installing using frozen lockfiles and more makes it a complete non-starter for anything but the most cookie-cutter projects.

[MikeMcC399]

https://pnpm.io/continuous-integration#github-actions for pnpm 11 & 12 shows as recipe for GitHub Actions:

name: pnpm Example Workflow
on:
  push:

jobs:
  build:
    runs-on: ubuntu-24.04
    strategy:
      matrix:
        node-version: [24]
    steps:
      - uses: actions/checkout@v6
      - name: Install pnpm
        uses: pnpm/action-setup@8912a9102ac27614460f54aedde9e1e7f9aec20d # v6.0.5
        with:
          version: 11
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v6
        with:
          node-version: ${{ matrix.node-version }}
          cache: "pnpm"
      - name: Install dependencies
        run: pnpm install

This is incidentally out of date compared to https://github.com/pnpm/action-setup/releases/tag/v6.0.10

Perhaps in the documentation, just show using @v6 instead of pinning? Unless the documentation is going to get continually updated.

[zkochan]

I have a feeling like everyone is super angry.

pnpm/setup is absolutely not a replacement for this action,

Feel free to open an issue in the pnpm/setup repository.

Perhaps in the documentation, just show using @v6 instead of pinning?

Not a good idea. Everyone recommends pinning the version. I think we can add something like a code generator to pnpm to create the action with the latest commits.

[zkochan]

@johnmurphy01 about the error that you see: [ERR_PNPM_BROKEN_PNPM_RELEASE] pnpm v11.13.0 is a broken release and cannot be installed

There were a few broken pnpm versions released. You cannot install v11.13.0. These versions were marked deprecated in the registry and we added additional tests to the release process for this issues to not happen again.

Regarding the issue with pnpm/setup you can create an issue in that repository.