#2227 chore(deps): bump the github-actions group with 2 updates Pull request opened by dependabot[bot] Bumps the github-actions group with 2 updates: astral-sh/setup-uv and actions/download-artifact. Updates

astral-sh/setup-uv

from 7.3.1 to 7.6.0 Release notes Sourced from astral-sh/setup-uv's releases.

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

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

• Fetch uv from Astral's mirror by default `@​zsol` (#809)

🧰 Maintenance

• Switch to ESM for source and test, use CommonJS for dist `@​eifinger` (#806)

• chore: update known checksums for 0.10.10 @github-actions[bot] (#804)

⬆️ Dependency updates

• chore(deps): bump zizmorcore/zizmor-action from 0.5.0 to 0.5.2 @dependabot[bot] (#808)

• Bump deps `@​eifinger` (#805)

v7.5.0 🌈 Use

astral-sh/versions

as version provider

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":"..."}]}

... (truncated) Commits • `37802ad` Fetch uv from Astral's mirror by default (#809) • `9f00d18` chore(deps): bump zizmorcore/zizmor-action from 0.5.0 to 0.5.2 (#808) • `fd8f376` Switch to ESM for source and test, use CommonJS for dist (#806) • `f9070de` Bump deps (#805) • `cadb67b` chore: update known checksums for 0.10.10 (#804) • `e06108d` Use astral-sh/versions as primary version provider (#802) • `0f6ec07` docs: replace copilot instructions with AGENTS.md (#794) • `821e5c9` docs: add cross-client dependabot rollup skill (#793) • `6ee6290` chore(deps): bump versions (#792) • `9f332a1` Add riscv64 architecture support to platform detection (#791) • Additional commits viewable in compare view Updates

actions/download-artifact

from 8.0.0 to 8.0.1 Release notes Sourced from actions/download-artifact's releases.

v8.0.1

What's Changed

• Support for CJK characters in the artifact name by `@​danwkennedy` in actions/download-artifact#471

• Add a regression test for artifact name + content-type mismatches by `@​danwkennedy` in actions/download-artifact#472

Full Changelog: actions/download-artifact@v8...v8.0.1

Commits • `3e5f45b` Add regression tests for CJK characters (#471) • `e6d03f6` Add a regression test for artifact name + content-type mismatches (#472) • See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot show <dependency name> ignore conditions

will show all of the ignore condition… meltano/hub