Remove actions/cache
in favor of actions/setup-python
caching
#288
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:
Currently, all CI jobs emit warnings due to
actions/cache@v3
, which uses an old Node.js version (recent example).However, on inspection, it appears that
actions/cache
is configured incorrectly:There are no lock files for it to hash, resulting in a blank portion in the cache key (caches generated in CI).
The comments in the YAML claim that it's caching for pipenv, but then caches the pip directory instead.
Therefore, this PR rips out
actions/cache
in favor of the Python caching already supported byactions/setup-python
.If this merges, please close #284.
PR Checklist:
pre-commit run --all-files
)make test
)n/a
n/a
n/a