chore(deps): update astral-sh/setup-uv action to v6 #20
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-6.x
branch
2 times, most recently
from
4f538f7 to
ea999db
Compare
|
helmut-hoffer-von-ankershoffen
force-pushed
the
main
branch
3 times, most recently
from
415af74 to
3747624
Compare
renovate
bot
force-pushed
the
renovate/astral-sh-setup-uv-6.x
branch
from
ea999db to
667aa47
Compare
helmut-hoffer-von-ankershoffen
deleted the
renovate/astral-sh-setup-uv-6.x
branch
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
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:
v5.3.1->v6.0.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
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
v6.0.0: 🌈 activate-environment and working-directoryCompare Source
Changes
This version contains some breaking changes which have been gathering up for a while. Lets dive into them:
cache-dependency-globActivate environment
In previous versions using the input
python-versionautomatically activated a venv at the repository root.This led to some unwanted side-effects, was sometimes unexpected and not flexible enough.
The venv activation is now explicitly controlled with the new input
activate-environment(false by default):The venv gets created by the
uv venvcommand so the python version is controlled by thepython-versioninput or the filespyproject.toml,uv.toml,.python-versionin theworking-directory.Working Directory
The new input
working-directorycontrols where we look forpyproject.toml,uv.tomland.python-versionfileswhich are used to determine the version of uv and python to install.
It can also be used to control where the venv gets created.
Default
cache-dependency-glob@ssbarnea found out that the default
cache-dependency-globwas not suitable for a lot of users.The old default
is changed and should cover over 99.5% of use cases:
Use default cache dir on self hosted runners
The directory where uv stores its cache was always set to a directory in
RUNNER_TEMP. For self-hosted runners this made no sense as this gets cleaned after every run and led to slower runs than necessary.On self-hosted runners
UV_CACHE_DIRis no longer set and the default cache directory is used instead.🚨 Breaking changes
🧰 Maintenance
📚 Documentation
v5.4.2: 🌈 Make sure uv installed by setup-uv is first in PATHCompare Source
Changes
This release fixes an issue on self-hosted runners.
If you manually installed uv with version 0.5.0 or later this version would overwrite the uv version installed by this action.
We now make sure the version installed by this action is the first found in PATH
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
v5.4.1: 🌈 Add support for pep440 version specifiersCompare Source
Changes
With this release you can also use pep440 version specifiers as
required-versionin filesuv.toml,pyroject.tomland in theversioninput:🐛 Bug fixes
🧰 Maintenance
📚 Documentation
v5.4.0: 🌈 uv and uvx path as outputsCompare Source
Changes
The absolute paths to the uv and uvx binaries can now be accessed via the outputs
uv-pathanduvx-path.setup-uvnow also issues a warning if the working directory is empty. This makes users aware of the common mistake to runsetup-uvbeforeactions/checkout. You can remove the warning by settingignore-empty-workdir: true🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
Configuration
📅 Schedule: 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.
This PR was generated by Mend Renovate. View the repository job log.