esperecyan commented 6 months ago

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

https://github.com/actions/setup-node/issues/531#issuecomment-1816774699

Action version: v4 (v4.0.2)

Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] 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