Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 7, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action major v6.7.0 β†’ v7.1.6

Release Notes

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

v7.1.6: 🌈 add OS version to cache key to prevent binary incompatibility

Compare Source

Changes

This release will invalidate your cache existing keys!

The os version e.g. ubuntu-22.04 is 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 setting cache-local-path without enable-cache: true

Compare Source

Changes

#​612 fixed a faulty behavior where this action set UV_CACHE_DIR even though enable-cache was false. It also fixed the cases were the cache dir is already configured in a settings file like pyproject.toml or UV_CACHE_DIR was already set. Here the action shouldn't overwrite or set UV_CACHE_DIR.

These fixes introduced an unwanted behavior: You can still set cache-local-path but this action didn't do anything. This release fixes that.

You can now use cache-local-path to automatically set UV_CACHE_DIR even when enable-cache is false (or gets set to false by default e.g. on self-hosted runners)

- name: This is now possible
  uses: astral-sh/setup-uv@v7
  with:
    enable-cache: false
    cache-local-path: "/path/to/cache"
πŸ› Bug fixes
🧰 Maintenance
⬆️ Dependency updates

v7.1.4: 🌈 Fix libuv closing bug on Windows

Compare Source

Changes

This release fixes the bug Assertion failed: !(handle->flags & UV_HANDLE_CLOSING) on Windows runners

πŸ› Bug fixes
🧰 Maintenance

v7.1.3: 🌈 Support act

Compare Source

Changes

This bug fix release adds support for https://github.com/nektos/act
It was previously broken because of a too new undici version and TS transpilation target.

Compatibility with act is now automatically tested.

πŸ› Bug fixes
🧰 Maintenance
πŸ“š Documentation

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

v6.8.0: 🌈 Add **/*.py.lock to cache-dependency-glob

Compare Source

Changes

Thanks to @​parched the default cache-dependency-glob now also find all lock files generated by uv lock --script

πŸš€ 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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@codecov
Copy link

codecov bot commented Oct 7, 2025

Codecov Report

βœ… All modified and coverable lines are covered by tests.
βœ… Project coverage is 71.38%. Comparing base (563acb6) to head (39f297a).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #822   +/-   ##
=======================================
  Coverage   71.38%   71.38%           
=======================================
  Files         108      108           
  Lines        9674     9674           
  Branches      860      860           
=======================================
  Hits         6906     6906           
  Misses       2595     2595           
  Partials      173      173           
Flag Coverage Ξ”
agent 72.85% <ΓΈ> (ΓΈ)
cli 87.90% <ΓΈ> (ΓΈ)
device 55.21% <ΓΈ> (ΓΈ)
server 87.71% <ΓΈ> (ΓΈ)
Components Coverage Ξ”
Agent 72.85% <ΓΈ> (ΓΈ)
CLI 87.90% <ΓΈ> (ΓΈ)
Common βˆ… <ΓΈ> (βˆ…)
Device Connectors 55.21% <ΓΈ> (ΓΈ)
Server 87.71% <ΓΈ> (ΓΈ)
πŸš€ New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • πŸ“¦ JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 6 times, most recently from 350ca05 to ab88ae4 Compare October 15, 2025 02:26
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 6 times, most recently from 6542591 to 11cc058 Compare October 22, 2025 12:53
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 3 times, most recently from 3142b50 to b4b743d Compare October 30, 2025 15:52
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from b4b743d to b8bde99 Compare November 10, 2025 23:11
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 3 times, most recently from 52a21a7 to 1560aeb Compare November 21, 2025 16:13
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 7 times, most recently from c926c40 to b0dc194 Compare December 4, 2025 18:08
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 3 times, most recently from 37c5880 to 79309f6 Compare December 10, 2025 19:45
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch 4 times, most recently from de0e0b6 to f812afb Compare December 13, 2025 19:06
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from f812afb to 19347b4 Compare December 19, 2025 17:54
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-7.x branch from 19347b4 to 39f297a Compare December 31, 2025 02:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant