Skip to content

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

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.5.0#1492
renovate[bot] wants to merge 1 commit intomainfrom
renovate/astral-sh-setup-uv-7.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 27, 2026

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action minor v7.3.0v7.5.0

Release Notes

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

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


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

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

@renovate renovate bot enabled auto-merge (squash) February 27, 2026 21:43
@codecov
Copy link

codecov bot commented Feb 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@65f2469). Learn more about missing BASE report.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@          Coverage Diff           @@
##             main   #1492   +/-   ##
======================================
  Coverage        ?     55%           
======================================
  Files           ?      32           
  Lines           ?    3894           
  Branches        ?       0           
======================================
  Hits            ?    2144           
  Misses          ?    1750           
  Partials        ?       0           
Flag Coverage Δ
tests 55% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from f916235 to a247398 Compare March 3, 2026 06:09
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from a247398 to d626e40 Compare March 11, 2026 00:33
@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.4.0 Mar 11, 2026
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from d626e40 to 1d01929 Compare March 13, 2026 01:25
@renovate renovate bot changed the title chore(deps): update astral-sh/setup-uv action to v7.4.0 chore(deps): update astral-sh/setup-uv action to v7.5.0 Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants