Skip to content

node_auth_token is not used in workflows when running pnpm install #11539

@aulonm

Description

@aulonm

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)

CLI

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

https://github.com/aulonm/pnpm-11-repro-bug

Reproduction steps

I've set up a github workflow that triggers a job with both pnpm 10 and pnpm 11 that are identical. The pnpm 11 job fails to install internal github dependencies with custom registry. Look at the actions tab on the reproduction repo

Describe the Bug

We tried to upgrade pnpm to v11 but our workflows started failing. The reason is that node_auth_token is not being set when running pnpm install in the workflow. This worked before with pnpm 10. Is this a regression or has the flow been changed?

Can't seem to find any documentation of this change, so not sure if it is a bug or not (it is for us right now..)

If you look at the lastest github action that has ben run, you can see that pnpm 10 works as it should, while pnpm 11 is failing with a 401: https://github.com/aulonm/pnpm-11-repro-bug/actions/runs/25541232976

Not sure if this should be in this repo or in the pnpm/setup-action repo

Expected Behavior

pnpm install should work as it worked with pnpm 10 in a workflow

Which Node.js version are you using?

v24.12.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

Metadata

Metadata

Assignees

Labels

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions