Skip to content

Conversation

@lab-assistant
Copy link
Contributor

@lab-assistant lab-assistant bot commented Oct 7, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action major v6.8.0 -> v7.1.2

Release Notes

astral-sh/setup-uv (astral-sh/setup-uv)

v7.1.2: 🌈 Speed up extraction on Windows

Compare 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 strategy

Compare Source

Changes

This release fixes a bug where the working-directory input was not used to detect an empty work dir. It also fixes the lowest resolution 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 cases

Compare 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-strategy lets 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-environment the path to the activated venv is now also exposed under the output venv.

Downloaded python installations can now also be uploaded to the GitHub Actions cache backend. Useful if you are running in act and 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 PATH on Windows.

🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v7.0.0: 🌈 node24 and a lot of bugfixes

Compare 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-url which 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
  • The action now respects when the environment variable UV_CACHE_DIR is already set and does not overwrite it. It now also finds cache-dir settings in config files if you set them.
  • Some users encountered problems that cache pruning took forever because they had some uv processes running in the background. Starting with uv version 0.8.24 this action uses uv cache prune --ci --force to ignore the running processes
  • If you just want to install uv but not have it available in path, this action now respects UV_NO_MODIFY_PATH
  • Some other actions also set the env var UV_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

[tool.uv]
required-version = ">=0.8.17"

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.x this 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
🚀 Enhancements
🧰 Maintenance
⬆️ 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@lab-assistant lab-assistant bot changed the title ci(github-action)!: Update astral-sh/setup-uv ( v6.8.0 ➔ v7.0.0 ) ci(github-action)!: Update astral-sh/setup-uv ( v6.8.0 ➔ v7.1.0 ) Oct 12, 2025
@lab-assistant lab-assistant bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from a3433b7 to da84482 Compare October 12, 2025 19:17
@lab-assistant lab-assistant bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from da84482 to 7900cbf Compare October 19, 2025 19:18
@lab-assistant lab-assistant bot changed the title ci(github-action)!: Update astral-sh/setup-uv ( v6.8.0 ➔ v7.1.0 ) ci(github-action)!: Update astral-sh/setup-uv ( v6.8.0 ➔ v7.1.1 ) Oct 19, 2025
| datasource  | package            | from   | to     |
| ----------- | ------------------ | ------ | ------ |
| github-tags | astral-sh/setup-uv | v6.8.0 | v7.1.2 |
@lab-assistant lab-assistant bot changed the title ci(github-action)!: Update astral-sh/setup-uv ( v6.8.0 ➔ v7.1.1 ) ci(github-action)!: Update astral-sh/setup-uv ( v6.8.0 ➔ v7.1.2 ) Oct 26, 2025
@lab-assistant lab-assistant bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 7900cbf to a3ac76b Compare October 26, 2025 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant