mirror of https://github.com/astral-sh/uv
b7e5ac24b5
Add a script and associated CI check that checks whether a new uv build can use the cache of the previous uv version. This prevents accidental changes to cache keys, e.g. by changing nested data structures. I've tested the script by using a previous change of https://github.com/astral-sh/uv/pull/16143. The check can be disabled with a PR label for PRs that change the cache layout. What's missing here is that the base is the last release, meaning that once a PR with that label merges, all following PRs will fail this check, as we currently don't have a good way to ask whether there was a change previously or to download the latest build binary from main as baseline. |
||
|---|---|---|
| .. | ||
| build-binaries.yml | ||
| build-docker.yml | ||
| ci.yml | ||
| publish-crates.yml | ||
| publish-docs.yml | ||
| publish-pypi.yml | ||
| release.yml | ||
| setup-dev-drive.ps1 | ||
| sync-python-releases.yml | ||
| zizmor.yml | ||