Skip to content
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.

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

Update astral-sh/setup-uv action to v5.4.1 #73

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action minor v5.1.0 -> v5.4.1

Release Notes

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

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

v5.3.1: 🌈 - Fix issues with GHES and HTTP proxies

Compare Source

Changes

This release fixes some issues when this action was used behind a HTTP proxy or with GHES.
If you have been seeing ENOTFOUND or timeout errors, this release should fix that.

A huge thank you to everyone who helped investigating this and testing the fixes:

🐛 Bug fixes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v5.3.0: 🌈 Support MUSL, s390x and powerpc

Compare Source

In this release we add support for MUSL based systems.
This is helpful if you are running your workflow inside a docker image based on alpine.

[!TIP]
Please be aware that you have to make sure a python interpreter is already present (apk add python3), see also https://docs.astral.sh/uv/concepts/python-versions/#cpython-distributions and https://github.com/astral-sh/uv/issues/6890

@​Zxilly also added support for running this action on self-hosted runners using s390x and powerpc architectures. Thank you!

This release also includes more debug logs which makes tracking down issues easier in the future.

🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation

v5.2.2: 🌈 Full support for GHES

Compare Source

Changes

This release fixes some issues that prevented use with GitHub Enterprise Server instances.

🐛 Bug fixes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v5.2.1: 🌈 Support toml spec 1.0.0

Compare Source

v5.2.0 introduced TOML parsing using @​iarna/toml because we already found out in astral-sh/ruff-action that toml has missing features.

As it turns out @​iarna/toml also is not fully TOML spec (1.0.0) compliant.

We now use smol-toml

🐛 Bug fixes

v5.2.0: 🌈 Detect required-version from config file

Compare Source

This release adds support to derive the version of uv to be installed from pyproject.toml and uv.toml files.
If no version input is defined the default is now to look for a required-version in uv.toml and then pyproject.toml in the repository root. If it cannot find any it falls back to latest.

If your files are at a different place you can use the new inputs uv-file or pyproject-file.

🐛 Bug fixes
🚀 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 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 changed the title Update astral-sh/setup-uv action to v5.2.0 Update astral-sh/setup-uv action to v5.2.1 Jan 16, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-5.x branch from e74c6e6 to 93b21ad Compare January 16, 2025 17:14
@renovate renovate bot changed the title Update astral-sh/setup-uv action to v5.2.1 Update astral-sh/setup-uv action to v5.2.2 Jan 30, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-5.x branch from 93b21ad to d253598 Compare January 30, 2025 18:56
@renovate renovate bot changed the title Update astral-sh/setup-uv action to v5.2.2 Update astral-sh/setup-uv action to v5.3.0 Feb 21, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-5.x branch from d253598 to 12cb9ed Compare February 21, 2025 10:29
@renovate renovate bot changed the title Update astral-sh/setup-uv action to v5.3.0 Update astral-sh/setup-uv action to v5.3.1 Mar 1, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-5.x branch from 12cb9ed to 2d229f0 Compare March 1, 2025 19:15
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-5.x branch from 2d229f0 to 58fe4b8 Compare March 21, 2025 15:57
@renovate renovate bot changed the title Update astral-sh/setup-uv action to v5.3.1 Update astral-sh/setup-uv action to v5.4.0 Mar 21, 2025
@renovate renovate bot changed the title Update astral-sh/setup-uv action to v5.4.0 Update astral-sh/setup-uv action to v5.4.1 Mar 30, 2025
@renovate renovate bot force-pushed the renovate/astral-sh-setup-uv-5.x branch from 58fe4b8 to 57b79f7 Compare March 30, 2025 18:30
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