ci: disable cache in semver-checks #3839
Closed
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
I noticed that
semver-checks
cache artifacts are tiny (hundreds of kilobytes tops) so it might worth maintaining them. Additionally, I hope it might help with the network issue reported here: #3782 (comment). It's a shot in the dark but some solutions to similar reported problems include clearing directories - my thinking is, maybe we're caching something that we shouldn't.Notes & open questions
Change checklist