chore(deps): update astral-sh/setup-uv action to v7#393
chore(deps): update astral-sh/setup-uv action to v7#393renovate-sh-app[bot] wants to merge 1 commit intomainfrom
Conversation
|
|
2 similar comments
|
|
|
|
renovate-sh-app
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
2 times, most recently
from
b8ee500 to
cc56865
Compare
| datasource | package | from | to | | ----------- | ------------------ | ------ | ------ | | github-tags | astral-sh/setup-uv | v6.8.0 | v7.6.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
renovate-sh-app
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
cc56865 to
ba43a9b
Compare
This PR contains the following updates:
v6.8.0→v7.6.0Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v7.6.0: 🌈 Fetch uv from Astral's mirror by defaultCompare Source
Changes
We now default to download uv from
releases.astral.sh.This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.5.0: 🌈 Use `astral-sh/versions` as version providerCompare Source
No more rate-limits
This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.
Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.
The
manifest-fileinput was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest.However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.
This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:
https://raw.githubusercontent.com/astral-sh/versions/refs/heads/main/v1/uv.ndjson
By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.
The
manifest-fileinput lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:
{"version":"0.10.7","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]} {"version":"0.10.6","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}Changes
🚀 Enhancements
📚 Documentation
v7.4.0: 🌈 Add riscv64 architecture support to platform detectionCompare Source
Changes
Thank you @luhenry for adding support for riscv64 arch
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.3.1: 🌈 fall back to VERSION_CODENAME when VERSION_ID is not availableCompare Source
Changes
This release adds support for running in containers like
debian:testingordebian:unstable🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.3.0: 🌈 New features and bug fixes for activate-environmentCompare Source
Changes
This release contains a few bug fixes and a new feature for the activate-environment functionality.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.2.1: 🌈 update known checksums up to 0.9.28Compare Source
Changes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.2.0: 🌈 add outputs python-version and python-cache-hitCompare Source
Changes
Among some minor typo fixes and quality of life features for developers of actions the main feature of this release are new outputs:
UV_PYTHON)While implementing this it became clear, that it is easier to handle the Python binaries in a separate cache entry. The added benefit for users is that the "normal" cache containing the dependencies can be used in all runs no matter if these cache the Python binaries or not.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.1.6: 🌈 add OS version to cache key to prevent binary incompatibilityCompare Source
Changes
This release will invalidate your cache existing keys!
The os version e.g.
ubuntu-22.04is now part of the cache key. This prevents failing builds when a cache got populated with wheels built with different tools (e.g. glibc) than are present on the runner where the cache got restored.🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.1.5: 🌈 allow settingcache-local-pathwithoutenable-cache: trueCompare Source
Changes
#612 fixed a faulty behavior where this action set
UV_CACHE_DIReven thoughenable-cachewasfalse. It also fixed the cases were the cache dir is already configured in a settings file likepyproject.tomlorUV_CACHE_DIRwas already set. Here the action shouldn't overwrite or setUV_CACHE_DIR.These fixes introduced an unwanted behavior: You can still set
cache-local-pathbut this action didn't do anything. This release fixes that.You can now use
cache-local-pathto automatically setUV_CACHE_DIReven whenenable-cacheisfalse(or gets set to false by default e.g. on self-hosted runners)🐛 Bug fixes
🧰 Maintenance
npm ci --ignore-scriptseverywhere @woodruffw (#699)⬆️ Dependency updates
v7.1.4: 🌈 Fix libuv closing bug on WindowsCompare Source
Changes
This release fixes the bug
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING)on Windows runners🐛 Bug fixes
🧰 Maintenance
v7.1.3: 🌈 Support actCompare Source
Changes
This bug fix release adds support for https://github.com/nektos/act
It was previously broken because of a too new
undiciversion and TS transpilation target.Compatibility with act is now automatically tested.
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
cache-dependency-glob@allanlewis (#676)v7.1.2: 🌈 Speed up extraction on WindowsCompare Source
Changes
@lazka fixed a bug that caused extracting uv to take up to 30s. Thank you!
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.1.1: 🌈 Fix empty workdir detection and lowest resolution strategyCompare Source
Changes
This release fixes a bug where the
working-directoryinput was not used to detect an empty work dir. It also fixes thelowestresolution strategy resolving to latest when only a lower bound was specified.Special thanks to @tpgillam for the first contribution!
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.1.0: 🌈 Support all the use casesCompare Source
Changes
Support all the use cases!!!
... well, that we know of.
This release adds support for some use cases that most users don't encounter but are useful for e.g. people running Gitea.
The input
resolution-strategylets you use the lowest possible version of uv from a version range. Useful if you want to test your tool with different versions of uv.If you use
activate-environmentthe path to the activated venv is now also exposed under the outputvenv.Downloaded python installations can now also be uploaded to the GitHub Actions cache backend. Useful if you are running in
actand have configured your own backend and don't want to download python again, and again over a slow internet connection.Finally the path to installed python interpreters is now added to the
PATHon Windows.🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.0.0: 🌈 node24 and a lot of bugfixesCompare Source
Changes
This release comes with a load of bug fixes and a speed up. Because of switching from node20 to node24 it is also a breaking change. If you are running on GitHub hosted runners this will just work, if you are using self-hosted runners make sure, that your runners are up to date. If you followed the normal installation instructions your self-hosted runner will keep itself updated.
This release also removes the deprecated input
server-urlwhich was used to download uv releases from a different server.The manifest-file input supersedes that functionality by adding a flexible way to define available versions and where they should be downloaded from.
Fixes
UV_CACHE_DIRis already set and does not overwrite it. It now also finds cache-dir settings in config files if you set them.uvprocesses running in the background. Starting with uv version0.8.24this action usesuv cache prune --ci --forceto ignore the running processesUV_NO_MODIFY_PATHUV_CACHE_DIR. This action can now deal with that but as this could lead to unwanted behavior in some edgecases a warning is now displayed.Improvements
If you are using minimum version specifiers for the version of uv to install for example
This action now detects that and directly uses the latest version. Previously it would download all available releases from the uv repo
to determine the highest matching candidate for the version specifier, which took much more time.
If you are using other specifiers like
0.8.xthis action still needs to download all available releases because the specifier defines an upper bound (not 0.9.0 or later) and "latest" would possibly not satisfy that.🚨 Breaking changes
🐛 Bug fixes
UV_CACHE_DIRhas changed @jamesbraza (#601)🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.