Changes
This release adds a new input manifest-file.
The manifest-file input allows you to specify a JSON manifest that lists available uv versions,
architectures, and their download URLs. By default, this action uses the manifest file contained
in this repository, which is automatically updated with each release of uv.
The manifest file contains an array of objects, each describing a version,
architecture, platform, and the corresponding download URL.
You can supply a custom manifest file URL to define additional versions,
architectures, or different download URLs.
This is useful if you maintain your own uv builds or want to override the default sources.
For example:
[
{
"version": "0.7.12-alpha.1",
"artifactName": "uv-x86_64-unknown-linux-gnu.tar.gz",
"arch": "x86_64",
"platform": "unknown-linux-gnu",
"downloadUrl": "https://release.pyx.dev/0.7.12-alpha.1/uv-x86_64-unknown-linux-gnu.tar.gz"
},
...
]- name: Use a custom manifest file
uses: astral-sh/setup-uv@v6
with:
manifest-file: "https://example.com/my-custom-manifest.json"Warning
If you have previously used server-url to use your self hosted uv binaries use this new way instead.
server-url is deprecated and will be removed in a future release
🚀 Enhancements
- Add input manifest-file @eifinger (#454)
- Add warning about shadowed uv binaries to
activate-environment@zanieb (#439)
🧰 Maintenance
- chore: update known versions for 0.7.13 @github-actions[bot] (#444)
- Set expected cache dir drive to C: on windows @eifinger (#451)
- chore: update known versions for 0.7.11 @github-actions[bot] (#442)
- chore: update known versions for 0.7.10 @github-actions[bot] (#440)
- chore: update known versions for 0.7.9 @github-actions[bot] (#437)
- Check that all jobs are in all-tests-passed.needs @eifinger (#432)
- chore: update known versions for 0.7.8 @github-actions[bot] (#428)