If cache: yarn is specified, this action fails

[esperecyan]

Description:
If I set packageManager property in package.json and set cache: yarn in this action, this action will fail.

Related:

• Corepack Support #531 (comment)

Action version:
v4 (v4.0.2)

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

• yarn 4.1.1

Repro steps:
This is the workflow that reproduced this issue with the minimum configuration.
https://github.com/esperecyan/actions-setup-node-debug/actions/runs/8907795048/workflow
You can confirm that the issue does not occur in the following cases:

• If I set npm to packageManager.
• If I set yarn to packageManager and do not set cache: yarn for this action.

Expected behavior:
actions/setup-node succeeds.

Actual behavior:
actions/setup-node fails with the following error.

Error: error This project's package.json defines "packageManager": "yarn@4.1.1". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
https://github.com/esperecyan/actions-setup-node-debug/actions/runs/8907795048/job/24462266566

Running corepack enable before actions/setup-node will avoid this issue.
https://github.com/esperecyan/actions-setup-node-debug/actions/runs/8907795048/job/24462266822

[HarithaVattikuti]

Hello @esperecyan
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

[1kevgriff]

Hitting this today too.

[n0099]

#901
#546
#480

[SunsetTechuila]

Running corepack enable before actions/setup-node will avoid this issue.

works only for node 18+

for node 14-16 see #1075 (comment)

[unickq]

Still there, 2025.

    steps:
      - uses: actions/checkout@v4

      - name: Enable Corepack
        run: corepack enable

      - name: Setup Node.js Environment
        uses: actions/setup-node@v4
        with:
          node-version-file: '.nvmrc'
          # https://github.com/actions/setup-node/issues/1027
          cache: 'yarn'

Environment details
  node: v18.20.6
  npm: 10.8.2
  yarn: 1.22.22
/usr/local/bin/yarn --version
1.22.22
/usr/local/bin/yarn cache dir
/home/runner/.cache/yarn/v6
/usr/local/bin/yarn config get enableGlobalCache
undefined

[socketbox]

One thing to note is that OP explicitly states they're using yarn v4.1.1. Those of you using v1.22.22 are obviously going to have a different experience.

For what it's worth, the reported issue is not encountered using the following workflow steps (no Corepack needed):

      - name: Setup cache
        uses: actions/setup-node@v4
        with:
          node-version-file: '.nvmrc'
          cache: 'yarn'
      - name: Prepare dependencies
        id: prepare-dependencies
        run: |
          echo "Install latest yarn..."
          npm install -g yarn@latest
          echo "Check that we're running latest yarn..."
          which yarn 
          mkdir ./dist
          yarn install --immutable