chore(deps): update astral-sh/setup-uv action to v7#538
Open
renovate[bot] wants to merge 3 commits intomainfrom
Open
chore(deps): update astral-sh/setup-uv action to v7#538renovate[bot] wants to merge 3 commits intomainfrom
renovate[bot] wants to merge 3 commits intomainfrom
Conversation
Contributor
Greptile OverviewGreptile SummaryThis PR updates the GitHub Action used to install The change applies to the Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub
participant WF as Workflow (release/version-bump)
participant C as actions/checkout@v4
participant UV as astral-sh/setup-uv@v7
participant R as Runner shell
GH->>WF: push / workflow_dispatch
WF->>C: Checkout repository
C-->>WF: Working tree ready
WF->>UV: Install uv (v7)
UV-->>WF: uv available on PATH
WF->>R: Run uv commands (build / version bump)
R-->>WF: Command outputs + artifacts
WF-->>GH: Job status + artifacts
|
f1d6d93 to
30169db
Compare
726f578 to
a3a0866
Compare
a3a0866 to
01fdbee
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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.8.0→v7.3.1Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v7.3.1: 🌈 fall back to VERSION_CODENAME when VERSION_ID is not availableCompare Source
Changes
This release adds support for running in containers like
debian:testingordebian:unstable🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.3.0: 🌈 New features and bug fixes for activate-environmentCompare Source
Changes
This release contains a few bug fixes and a new feature for the activate-environment functionality.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.2.1: 🌈 update known checksums up to 0.9.28Compare Source
Changes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.2.0: 🌈 add outputs python-version and python-cache-hitCompare Source
Changes
Among some minor typo fixes and quality of life features for developers of actions the main feature of this release are new outputs:
UV_PYTHON)While implementing this it became clear, that it is easier to handle the Python binaries in a separate cache entry. The added benefit for users is that the "normal" cache containing the dependencies can be used in all runs no matter if these cache the Python binaries or not.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.1.6: 🌈 add OS version to cache key to prevent binary incompatibilityCompare Source
Changes
This release will invalidate your cache existing keys!
The os version e.g.
ubuntu-22.04is now part of the cache key. This prevents failing builds when a cache got populated with wheels built with different tools (e.g. glibc) than are present on the runner where the cache got restored.🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.1.5: 🌈 allow settingcache-local-pathwithoutenable-cache: trueCompare Source
Changes
#612 fixed a faulty behavior where this action set
UV_CACHE_DIReven thoughenable-cachewasfalse. It also fixed the cases were the cache dir is already configured in a settings file likepyproject.tomlorUV_CACHE_DIRwas already set. Here the action shouldn't overwrite or setUV_CACHE_DIR.These fixes introduced an unwanted behavior: You can still set
cache-local-pathbut this action didn't do anything. This release fixes that.You can now use
cache-local-pathto automatically setUV_CACHE_DIReven whenenable-cacheisfalse(or gets set to false by default e.g. on self-hosted runners)🐛 Bug fixes
🧰 Maintenance
npm ci --ignore-scriptseverywhere @woodruffw (#699)⬆️ Dependency updates
v7.1.4: 🌈 Fix libuv closing bug on WindowsCompare Source
Changes
This release fixes the bug
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING)on Windows runners🐛 Bug fixes
🧰 Maintenance
v7.1.3: 🌈 Support actCompare Source
Changes
This bug fix release adds support for https://github.com/nektos/act
It was previously broken because of a too new
undiciversion and TS transpilation target.Compatibility with act is now automatically tested.
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
cache-dependency-glob@allanlewis (#676)v7.1.2: 🌈 Speed up extraction on WindowsCompare Source
Changes
@lazka fixed a bug that caused extracting uv to take up to 30s. Thank you!
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.1.1: 🌈 Fix empty workdir detection and lowest resolution strategyCompare Source
Changes
This release fixes a bug where the
working-directoryinput was not used to detect an empty work dir. It also fixes thelowestresolution strategy resolving to latest when only a lower bound was specified.Special thanks to @tpgillam for the first contribution!
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.1.0: 🌈 Support all the use casesCompare Source
Changes
Support all the use cases!!!
... well, that we know of.
This release adds support for some use cases that most users don't encounter but are useful for e.g. people running Gitea.
The input
resolution-strategylets you use the lowest possible version of uv from a version range. Useful if you want to test your tool with different versions of uv.If you use
activate-environmentthe path to the activated venv is now also exposed under the outputvenv.Downloaded python installations can now also be uploaded to the GitHub Actions cache backend. Useful if you are running in
actand have configured your own backend and don't want to download python again, and again over a slow internet connection.Finally the path to installed python interpreters is now added to the
PATHon Windows.🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.0.0: 🌈 node24 and a lot of bugfixesCompare Source
Changes
This release comes with a load of bug fixes and a speed up. Because of switching from node20 to node24 it is also a breaking change. If you are running on GitHub hosted runners this will just work, if you are using self-hosted runners make sure, that your runners are up to date. If you followed the normal installation instructions your self-hosted runner will keep itself updated.
This release also removes the deprecated input
server-urlwhich was used to download uv releases from a different server.The manifest-file input supersedes that functionality by adding a flexible way to define available versions and where they should be downloaded from.
Fixes
UV_CACHE_DIRis already set and does not overwrite it. It now also finds cache-dir settings in config files if you set them.uvprocesses running in the background. Starting with uv version0.8.24this action usesuv cache prune --ci --forceto ignore the running processesUV_NO_MODIFY_PATHUV_CACHE_DIR. This action can now deal with that but as this could lead to unwanted behavior in some edgecases a warning is now displayed.Improvements
If you are using minimum version specifiers for the version of uv to install for example
This action now detects that and directly uses the latest version. Previously it would download all available releases from the uv repo
to determine the highest matching candidate for the version specifier, which took much more time.
If you are using other specifiers like
0.8.xthis action still needs to download all available releases because the specifier defines an upper bound (not 0.9.0 or later) and "latest" would possibly not satisfy that.🚨 Breaking changes
🐛 Bug fixes
UV_CACHE_DIRhas changed @jamesbraza (#601)🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
Configuration
📅 Schedule: Branch creation - "on the 15th day of the month before 12pm" 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.