Fix additional occurrence of yarn cache nesting #987
Merged
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.
The current yarn cache restore logic (introduced in #978) can create nested caches like below, iff the
.yarn/cache
folder is committed in the repo, but empty.This PR changes the cache restore logic to remove the empty folder before moving the cache, so we essentially replace the folder, rather than nesting folders.
This also adds some temporary logic to delete any nested caches we created in #978.
GUS-W-10519616