Update astral-sh/setup-uv action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
astral-sh/setup-uv	action	major	v5.4.1 -> v6.0.0

---

Release Notes

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

v6.0.0: 🌈 activate-environment and working-directory

Compare Source

Changes

This version contains some breaking changes which have been gathering up for a while. Lets dive into them:

• Activate environment
• Working Directory
• Default cache-dependency-glob
• Use default cache dir on self hosted runners

Activate environment

In previous versions using the input python-version automatically 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):

- name: Install the latest version of uv and activate the environment
  uses: astral-sh/setup-uv@v6
  with:
    activate-environment: true
- run: uv pip install pip

The venv gets created by the uv venv command so the python version is controlled by the python-version input or the files pyproject.toml, uv.toml, .python-version in the working-directory.

Working Directory

The new input working-directory controls where we look for pyproject.toml, uv.toml and .python-version files
which are used to determine the version of uv and python to install.

It can also be used to control where the venv gets created.

- name: Install uv based on the config files in the working-directory
  uses: astral-sh/setup-uv@v6
  with:
    working-directory: my/subproject/dir

[!CAUTION]

The inputs pyproject-file and uv-file have been removed.

Default cache-dependency-glob

@​ssbarnea found out that the default cache-dependency-glob was not suitable for a lot of users.

The old default

cache-dependency-glob: |
  **/requirements*.txt
  **/uv.lock

is changed and should cover over 99.5% of use cases:

cache-dependency-glob: |
  **/*(requirements|constraints)*.(txt|in)
  **/pyproject.toml
  **/uv.lock

[!NOTE]

This shouldn't be a breaking change. The only thing you may notice is that your caches get invalidated once.

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_DIR is no longer set and the default cache directory is used instead.

🚨 Breaking changes

• Change default cache-dependency-glob @​eifinger (#​352)
• No default UV_CACHE_DIR on selfhosted runners @​eifinger (#​380)
• new inputs activate-environment and working-directory @​eifinger (#​381)

🧰 Maintenance

• chore: update known checksums for 0.6.16 @​github-actions[bot] (#​378)
• chore: update known checksums for 0.6.15 @​github-actions[bot] (#​377)

📚 Documentation

• bump to v6 in README @​eifinger (#​382)
• log info on venv activation @​eifinger (#​375)

v5.4.2: 🌈 Make sure uv installed by setup-uv is first in PATH

Compare 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

• Make sure uv installed by setup-uv is first in PATH @​eifinger (#​373)

🧰 Maintenance

• chore: update known checksums for 0.6.14 @​github-actions[bot] (#​366)
• chore: update known checksums for 0.6.13 @​github-actions[bot] (#​365)
• chore: update known checksums for 0.6.12 @​github-actions[bot] (#​362)
• chore: update known checksums for 0.6.11 @​github-actions[bot] (#​357)

📚 Documentation

• Fix pep440 identifier instead of specifier @​eifinger (#​358)

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 05:59 AM, on day 1 of the month ( * 0-5 1 * * ) (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.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.