Skip to content

build: invalidate github action cache to prune old files #24896

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 7, 2022
Merged

build: invalidate github action cache to prune old files #24896

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/actions/yarn-install/action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ runs:
# Cache key. Whenever the postinstall patches change, the cache needs to be invalidated.
# If just the `yarn.lock` file changes, the most recent cache can be restored though.
# See: https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#example-using-the-cache-action.
key: v3-${{hashFiles('tools/postinstall/apply-patches.js')}}-${{hashFiles('yarn.lock')}}
restore-keys: v3-${{hashFiles('tools/postinstall/apply-patches.js')}}-
key: v4-${{hashFiles('tools/postinstall/apply-patches.js')}}-${{hashFiles('yarn.lock')}}
restore-keys: v4-${{hashFiles('tools/postinstall/apply-patches.js')}}-

- run: yarn install --frozen-lockfile --non-interactive
shell: bash