build: invalidate github action cache to prune old files #24896
Merged
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
With Angular v14, and the CLDR update one of the files got renamed just in casing. Yarn 1.x. does not seem to prune the old files causing two files to have the same name (ignoring casing). This throws off Bazel and we need to prune the cache like we did for CircleCI.
devversion
added
merge safe
target: rc
crisbeto
pushed a commit
that referenced
this pull request
May 7, 2022
With Angular v14, and the CLDR update one of the files got renamed just in casing. Yarn 1.x. does not seem to prune the old files causing two files to have the same name (ignoring casing). This throws off Bazel and we need to prune the cache like we did for CircleCI. (cherry picked from commit 00e589b)
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
With Angular v14, and the CLDR update one of the files got renamed
just in casing. Yarn 1.x. does not seem to prune the old files
causing two files to have the same name (ignoring casing). This throws
off Bazel and we need to prune the cache like we did for CircleCI.