chore(deps): update astral-sh/setup-uv action to v7.5.0#42
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update astral-sh/setup-uv action to v7.5.0#42renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #42 +/- ##
=======================================
Coverage 55.24% 55.24%
=======================================
Files 20 20
Lines 1421 1421
=======================================
Hits 785 785
Misses 636 636 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
331e633 to
0d4b6e6
Compare
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
2 times, most recently
from
23a9fcd to
5b1a7c9
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
5b1a7c9 to
db71e0b
Compare
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
db71e0b to
2f035c2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
2f035c2 to
8d4a61c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
8d4a61c to
57f2050
Compare
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
57f2050 to
75d1bdd
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-7.x
branch
from
75d1bdd to
7032a28
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v7.1.5→v7.5.0Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
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
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.