Skip to content

chore(deps): update astral-sh/setup-uv action to v7.6.0#126

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/astral-sh-setup-uv-7.x
Open

chore(deps): update astral-sh/setup-uv action to v7.6.0#126
renovate[bot] wants to merge 1 commit intomainfrom
renovate/astral-sh-setup-uv-7.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 13, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action minor v7.1.5v7.6.0

Release Notes

astral-sh/setup-uv (astral-sh/setup-uv)

v7.6.0: 🌈 Fetch uv from Astral's mirror by default

Compare 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 provider

Compare 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-file input 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.


[!TIP]
The next section is only interesting for users of the manifest-file input

The manifest-file input 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":"..."}]}

[!WARNING]
The old format still works but is deprecated. A warning will be logged when you use it.

Changes
🚀 Enhancements
📚 Documentation

v7.4.0: 🌈 Add riscv64 architecture support to platform detection

Compare 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 available

Compare Source

Changes

This release adds support for running in containers like debian:testing or debian:unstable

🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates

v7.3.0: 🌈 New features and bug fixes for activate-environment

Compare 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.28

Compare Source

Changes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v7.2.0: 🌈 add outputs python-version and python-cache-hit

Compare 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:

  • python-version: The Python version that was set (same content as existing UV_PYTHON)
  • python-cache-hit: A boolean value to indicate the Python cache entry was found

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.

[!NOTE]
This release will invalidate caches that contain the Python binaries. This happens a single time.

🐛 Bug fixes
  • chore: remove stray space from UV_PYTHON_INSTALL_DIR message @​akx (#​720)
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates

v7.1.6: 🌈 add OS version to cache key to prevent binary incompatibility

Compare Source

Changes

This release will invalidate your cache existing keys!

The os version e.g. ubuntu-22.04 is 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: (UTC)

  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions github-actions Bot added the ci label Dec 13, 2025
@codecov
Copy link
Copy Markdown

codecov Bot commented Dec 13, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 5 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 41d12a4 to 5ec2133 Compare January 1, 2026 01:52
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v7.1.6 chore(deps): update astral-sh/setup-uv action to v7.2.0 Jan 6, 2026
@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 5ec2133 to b3b49c1 Compare January 6, 2026 21:21
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v7.2.0 chore(deps): update astral-sh/setup-uv action to v7.2.1 Jan 30, 2026
@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from b3b49c1 to 0eeff90 Compare January 30, 2026 10:15
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v7.2.1 chore(deps): update astral-sh/setup-uv action to v7.3.0 Feb 6, 2026
@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 0eeff90 to 8324f7e Compare February 6, 2026 17:49
@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 8324f7e to f3bfe7f Compare February 27, 2026 21:16
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v7.3.0 chore(deps): update astral-sh/setup-uv action to v7.3.1 Feb 27, 2026
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v7.3.1 chore(deps): update astral-sh/setup-uv action to v7.5.0 Mar 14, 2026
@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from f3bfe7f to 8897b3a Compare March 14, 2026 19:55
@renovate renovate Bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 8897b3a to a401d8e Compare March 31, 2026 18:47
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v7.5.0 chore(deps): update astral-sh/setup-uv action to v7.6.0 Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants