Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Situation
If
cypress-io/github-action
detectsyarn.lock
it assumes that Yarn v1 Classic is being used and designates~/.cache/yarn
as the cache folder.yarn.lock
is used by both Yarn v1 Classic and by Yarn Modern.In the case of Yarn Modern, executing
yarn config get cacheFolder
on Linux shows that the cache is located in~/.yarn/berry/cache
.~/.cache/yarn
is the wrong folder for Yarn Modern.~/.yarn/berry/cache
is the correct folder to use for Yarn Modern.Change
For the Yarn Modern examples add actions/setup-node, which offers the built-in optional functionality of caching npm/yarn/pnpm dependencies. It supports Yarn 1 Classic and Yarn Modern.
Workflows:
README sections
Verification
Run workflows manually:
Check cache for presence of the following, for each of the above two workflows: