Proposal: allow disabling package manager caching

[MikeMcC399]

• follows on from suggestion in Package manager caching strategy for pnpm and Yarn Modern #1366

What would you like?

• Provide an action option to disable package manager caching when installing dependencies
• Add / modify example workflows to demonstrate using package manager caching from GitHub Actions' actions/setup-node

Why is this needed?

cypress-io/github-action caches package manager dependencies for:

• npm
• Yarn v1 Classic

and offers no equivalent built-in functionality for:

• pnpm
• Yarn Modern

If a pnpm lockfile pnpm-lock.yaml is detected, the action caches the npm cache, not the pnpm cache, leading to a potentially incorrect Cypress version usage in npx verify steps. For projects with pnpm workspaces, this means that the action cannot be used to install dependencies (see description of failure condition in #1594 (comment)). Instead dependencies must be installed using pnpm install commands directly.

GitHub Actions offers a full suite of setup-* actions to cache dependencies of commonly-used package managers.

For Cypress, the relevant caching action is actions/setup-node which offers caching for npm, Yarn (v1 and Modern) and pnpm.

Duplicating the capability from actions/setup-node into cypress-io/github-action for pnpm and Yarn would involve a significant re-write and on-going action maintenance effort, so this would not be a recommended resolution strategy.

Other

Relates to:

• Package manager caching strategy for pnpm and Yarn Modern #1366
• Add workspace support for pnpm #1144
• Allow disabling cache #953