chore(deps): update astral-sh/setup-uv action to v6.3.1 #10
Conversation
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:
v6->v6.3.1v3->v6.3.1Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v6.3.1: 🌈 Do not warn when version not in manifest-fileCompare Source
Changes
This is a hotfix to change the warning messages that a version could not be found in the local manifest-file to info level.
A
setup-uvrelease contains a version-manifest.json file with infos in all availableuvreleases. When a newuvversion is released this is not contained in this file until the file gets updated and a newsetup-uvrelease is made.We will overhaul this process in the future but for now the spamming of warnings is removed.
🐛 Bug fixes
🧰 Maintenance
v6.3.0: 🌈 Use latest version from manifest-fileCompare Source
Changes
If a manifest-file is supplied the default value of the version input (latest) will get the latest version available in the manifest. That might not be the actual latest version available in the official uv repo.
🚀 Enhancements
v6.2.1: 🌈 Fix "No such file or directory version-manifest.json"Compare Source
Changes
Release v6.2.0 contained a bug that slipped through the automated test. The action tried to look for the default version-manifest.json in the root of the repostory using this action instead of relative to the action itself.
🐛 Bug fixes
v6.2.0: 🌈 New input manifest-fileCompare Source
Changes
This release adds a new input
manifest-file.The
manifest-fileinput 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" }, ... ]🚀 Enhancements
activate-environment@zanieb (#439)🧰 Maintenance
v6.1.0: 🌈Compare Source
Changes
This release adds the input
server-urlwhich defaults tohttps://github.com. You can set this to a custom url to control where this action downloads the uv release from. This is useful for users of gitea and comparable solutions.@sebadevo pointed out that we don't invalidate the cache when the
prune-cacheinput is changed. This leads to unnessecarily big caches. The input is now used to compute the cache key, properly invalidating the cache when it is changed.🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v6.0.1: 🌈 Fix default cache dependency globCompare Source
Changes
The new default in v6 used illegal patterns and therefore didn't match requirements files. This is now fixed.
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
Configuration
📅 Schedule: Branch creation - "every weekday" in timezone UTC, 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 these updates again.
This PR has been generated by Renovate Bot.