Skip to content

Update astral-sh/setup-uv action to v6 #356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
neutrinoceros merged 1 commit into from
Apr 29, 2025
Merged

Update astral-sh/setup-uv action to v6 #356

neutrinoceros merged 1 commit into from
Apr 29, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 29, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action major v5.3.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

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
🧰 Maintenance
📚 Documentation

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
🧰 Maintenance
📚 Documentation

v5.4.1: 🌈 Add support for pep440 version specifiers

Compare Source

Changes

With this release you can also use pep440 version specifiers as required-version in filesuv.toml, pyroject.toml and in the version input:

- name: Install a pep440-specifier-satisfying version of uv
  uses: astral-sh/setup-uv@v5
  with:
    version: ">=0.4.25,<0.5"
🐛 Bug fixes
🧰 Maintenance
📚 Documentation

v5.4.0: 🌈 uv and uvx path as outputs

Compare Source

Changes

The absolute paths to the uv and uvx binaries can now be accessed via the outputs uv-path and uvx-path.

setup-uv now also issues a warning if the working directory is empty. This makes users aware of the common mistake to run setup-uv before actions/checkout. You can remove the warning by setting ignore-empty-workdir: true

🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Apr 29, 2025
@neutrinoceros neutrinoceros added this to the Next release milestone Apr 29, 2025
@neutrinoceros neutrinoceros merged commit 76a65d0 into main Apr 29, 2025
23 checks passed
@neutrinoceros neutrinoceros deleted the renovate/astral-sh-setup-uv-6.x branch April 29, 2025 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

2.1.0

Development

Successfully merging this pull request may close these issues.

2 participants

@neutrinoceros