ci: use setup-yarn-cache action to follow caching strategy #34694
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kalmarz
approved these changes
Jul 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Our GHA cache usage is higher than it used to be, so I was investigating where this increased usage is coming from.
Checking https://github.com/camunda/camunda/actions/caches showed a PR #32595 against
stable/operate-8.5creating GHA cache entries related tosetup-nodeand Yarn - this is something we want to avoid according to our strategy. GHA cache is a shared resource and we must make best use of limited resources.This PR uses the better
setup-yarn-cacheglobal action onstable/operate-8.5branch.Checklist
Related issues
Related to #34695