Update astral-sh/setup-uv action to v8 #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/astral-sh-setup-uv-8.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v3→v8.2.0Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v8.2.0: 🌈 New inputsquietanddownload-from-astral-mirrorCompare Source
Changes
This release brings two new inputs and a few bug fixes.
New inputs
Lets talk about the new inputs first.
quiet
Pretty simple. It turns of all
infologgings. Useful if you use this in a composite action and are not interested in all the details.In the upcoming releases we will add log groups to fully implement support for "less noise"
download-from-astral-mirror
In some cases you may want to directly use the fallback of checking for available versions and downloading releases from GitHub instead of using the astral.sh mirror. Setting
download-from-astral-mirror: falseallows you to do that.Bugfixes
When using the astral.sh mirror to query available versions and download releases (done by default) we now stop sending the GitHub token in the header. The mirror never looked at it but we shouldn't be handing out that data even if it is just a short lived token.
All other bugfixes try to limit the impact of failed GitHub queries due to retries and other faults.
We couldn't pinpoint all rootcauses yet but added more logging for error cases to track them down.
🐛 Bug fixes
🚀 Enhancements
download-from-astral-mirrorinput @eifinger (#897)🧰 Maintenance
⬆️ Dependency updates
v8.1.0: 🌈 New inputno-projectCompare Source
Changes
This add the a new boolean input
no-project.It only makes sense to use in combination with
activate-environment: trueand will append--no projectto theuv venvcall. This is for example useful if you have a pyproject.toml file with parts unparseable by uv🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v8.0.0: 🌈 Immutable releases and secure tagsCompare Source
This is the first immutable release of
setup-uv🥳All future releases are also immutable, if you want to know more about what this means checkout the docs.
This release also has two breaking changes
New format for
manifest-fileThe previously deprecated way of defining a custom version manifest to control which
uvversions are available and where to download them from got removed. The functionality is still there but you have to use the new format.No more major and minor tags
To increase security even more we will stop publishing minor tags. You won't be able to use
@v8or@v8.0any longer. We do this because pinning to major releases opens up users to supply chain attacks like what happened to tj-actions.🚨 Breaking changes
🧰 Maintenance
v7.6Compare Source
v7.6.0: 🌈 Fetch uv from Astral's mirror by defaultCompare Source
Changes
We now default to download uv from
releases.astral.sh.This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.5Compare Source
v7.5.0: 🌈 Useastral-sh/versionsas version providerCompare Source
No more rate-limits
This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.
Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.
The
manifest-fileinput was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest.However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.
This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:
https://raw.githubusercontent.com/astral-sh/versions/refs/heads/main/v1/uv.ndjson
By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.
The
manifest-fileinput lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:
Changes
🚀 Enhancements
📚 Documentation
v7.4Compare Source
v7.4.0: 🌈 Add riscv64 architecture support to platform detectionCompare Source
Changes
Thank you @luhenry for adding support for riscv64 arch
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.3.1: 🌈 fall back to VERSION_CODENAME when VERSION_ID is not availableCompare Source
Changes
This release adds support for running in containers like
debian:testingordebian:unstable🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v7.3.0: 🌈 New features and bug fixes for activate-environmentCompare Source
Changes
This release contains a few bug fixes and a new feature for the activate-environment functionality.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.3Compare Source
v7.2.1: 🌈 update known checksums up to 0.9.28Compare Source
Changes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.2.0: 🌈 add outputs python-version and python-cache-hitCompare Source
Changes
Among some minor typo fixes and quality of life features for developers of actions the main feature of this release are new outputs:
UV_PYTHON)While implementing this it became clear, that it is easier to handle the Python binaries in a separate cache entry. The added benefit for users is that the "normal" cache containing the dependencies can be used in all runs no matter if these cache the Python binaries or not.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.2Compare Source
v7.1.6: 🌈 add OS version to cache key to prevent binary incompatibilityCompare Source
Changes
This release will invalidate your cache existing keys!
The os version e.g.
ubuntu-22.04is 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 settingcache-local-pathwithoutenable-cache: trueCompare Source
Changes
#612 fixed a faulty behavior where this action set
UV_CACHE_DIReven thoughenable-cachewasfalse. It also fixed the cases were the cache dir is already configured in a settings file likepyproject.tomlorUV_CACHE_DIRwas already set. Here the action shouldn't overwrite or setUV_CACHE_DIR.These fixes introduced an unwanted behavior: You can still set
cache-local-pathbut this action didn't do anything. This release fixes that.You can now use
cache-local-pathto automatically setUV_CACHE_DIReven whenenable-cacheisfalse(or gets set to false by default e.g. on self-hosted runners)🐛 Bug fixes
🧰 Maintenance
npm ci --ignore-scriptseverywhere @woodruffw (#699)⬆️ Dependency updates
v7.1.4: 🌈 Fix libuv closing bug on WindowsCompare Source
Changes
This release fixes the bug
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING)on Windows runners🐛 Bug fixes
🧰 Maintenance
v7.1.3: 🌈 Support actCompare Source
Changes
This bug fix release adds support for https://github.com/nektos/act
It was previously broken because of a too new
undiciversion and TS transpilation target.Compatibility with act is now automatically tested.
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
cache-dependency-glob@allanlewis (#676)v7.1.2: 🌈 Speed up extraction on WindowsCompare 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 strategyCompare Source
Changes
This release fixes a bug where the
working-directoryinput was not used to detect an empty work dir. It also fixes thelowestresolution 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 casesCompare 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-strategylets 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-environmentthe path to the activated venv is now also exposed under the outputvenv.Downloaded python installations can now also be uploaded to the GitHub Actions cache backend. Useful if you are running in
actand 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
PATHon Windows.🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v7.1Compare Source
v7.0Compare Source
v7.0.0: 🌈 node24 and a lot of bugfixesCompare 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-urlwhich 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
UV_CACHE_DIRis already set and does not overwrite it. It now also finds cache-dir settings in config files if you set them.uvprocesses running in the background. Starting with uv version0.8.24this action usesuv cache prune --ci --forceto ignore the running processesUV_NO_MODIFY_PATHUV_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
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.xthis 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
UV_CACHE_DIRhas changed @jamesbraza (#601)🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7Compare Source
v6.8Compare Source
v6.8.0: 🌈 Add **/*.py.lock to cache-dependency-globCompare Source
Changes
Thanks to @parched the default
cache-dependency-globnow also find all lock files generated byuv lock --script🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v6.7Compare Source
v6.7.0: 🌈 New inputsrestore-cacheandsave-cacheCompare Source
Changes
This release adds fine-grained control over the caching steps.
restore-cache(trueby default) can be set tofalseto skip restoring the cache while still allowing to save the cache.save-cache(trueby default) can be set tofalseto skip saving the cache.Skipping cache saving can be useful if you know, that you will never use this version of the cache again and don't want to waste storage space:
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v6.6.1: 🌈 Fix exclusions in cache-dependency-globCompare Source
Changes
Exclusions with a leading
!in the cache-dependency-glob did not work and got fixed with this release. Thank you @KnisterPeter for raising this!🐛 Bug fixes
🧰 Maintenance
v6.6.0: 🌈 Support for .tools-versionsCompare Source
Changes
This release adds support for asdf
.tool-versionsin theversion-fileinput🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
v6.6Compare Source
v6.5Compare Source
v6.5.0: 🌈 Better error messages, bug fixes and copilot agent settingsCompare Source
Changes
This release brings better error messages in case the GitHub API is impacted, fixes a few bugs and allows to disable problem matchers for better use in Copilot Agent workspaces.
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v6.4.3: 🌈 fix relative paths starting with dotsCompare Source
🐛 Bug fixes
v6.4.2: 🌈 Interpret relative inputs as under working-directoryCompare Source
Changes
This release will interpret relative paths in inputs as relative
to the value of
working-directory(default is${{ github.workspace }}) .This means the following configuration
will look for the
cache-dependency-globunder/my/path/uv.lock🐛 Bug fixes
🧰 Maintenance
v6.4.1: 🌈 Hotfix: Ignore deps starting with uv when finding uv versionCompare Source
Changes
Thank you @phpmypython for raising a PR to fix this issue!
🐛 Bug fixes
v6.4.0: 🌈 Add inputversion-fileCompare Source
Changes
You can now use the
version-fileinput to specify a file that contains the version of uv to install.This can either be a
pyproject.tomloruv.tomlfile which defines arequired-versionoruv defined as a dependency in
pyproject.tomlorrequirements.txt.🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v6.4Compare Source
v6.3.1: 🌈 Do not warn when version not in manifest-fileCompare Source
Changes
This is a hotfix to change the warning messages that a version could not be found in the local manifest-file to info level.
A
setup-uvrelease contains a version-manifest.json file with infos in all availableuvreleases. When a newuvversion is released this is not contained in this file until the file gets updated and a newsetup-uvrelease is made.We will overhaul this process in the future but for now the spamming of warnings is removed.
🐛 Bug fixes
🧰 Maintenance
v6.3.0: 🌈 Use latest version from manifest-fileCompare Source
Changes
If a manifest-file is supplied the default value of the version input (latest) will get the latest version available in the manifest. That might not be the actual latest version available in the official uv repo.
🚀 Enhancements
v6.3Compare Source
v6.2.1: 🌈 Fix "No such file or directory version-manifest.json"Compare Source
Changes
Release v6.2.0 contained a bug that slipped through the automated test. The action tried to look for the default version-manifest.json in the root of the repostory using this action instead of relative to the action itself.
🐛 Bug fixes
v6.2Compare Source
v6.2.0: 🌈 New input manifest-fileCompare Source
Changes
This release adds a new input
manifest-file.The
manifest-fileinput allows you to specify a JSON manifest that lists available uv versions,architectures, and their download URLs. By default, this action uses the manifest file contained
in this repository, which is automatically updated with each release of uv.
The manifest file contains an array of objects, each describing a version,
architecture, platform, and the corresponding download URL.
You can supply a custom manifest file URL to define additional versions,
architectures, or different download URLs.
This is useful if you maintain your own uv builds or want to override the default sources.
For example:
🚀 Enhancements
activate-environment@zanieb (#439)🧰 Maintenance
v6.1Compare Source
v6.1.0: 🌈Compare Source
Changes
This release adds the input
server-urlwhich defaults tohttps://github.com. You can set this to a custom url to control where this action downloads the uv release from. This is useful for users of gitea and comparable solutions.@sebadevo pointed out that we don't invalidate the cache when the
prune-cacheinput is changed. This leads to unnessecarily big caches. The input is now used to compute the cache key, properly invalidating the cache when it is changed.🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v6.0.1: 🌈 Fix default cache dependency globCompare Source
Changes
The new default in v6 used illegal patterns and therefore didn't match requirements files. This is now fixed.
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v6.0.0: 🌈 activate-environment and working-directoryCompare Source
Changes
This version contains some breaking changes which have been gathering up for a while. Lets dive into them:
cache-dependency-globActivate environment
In previous versions using the input
python-versionautomatically 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):The venv gets created by the
uv venvcommand so the python version is controlled by thepython-versioninput or the filespyproject.toml,uv.toml,.python-versionin theworking-directory.Working Directory
The new input
working-directorycontrols where we look forpyproject.toml,uv.tomland.python-versionfileswhich are used to determine the version of uv and python to install.
It can also be used to control where the venv gets created.
Default
cache-dependency-glob@ssbarnea found out that the default
cache-dependency-globwas not suitable for a lot of users.The old default
is changed and should cover over 99.5% of use cases:
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_DIRis no longer set and the default cache directory is used instead.🚨 Breaking changes
🧰 Maintenance
📚 Documentation
v6.0Compare Source
v6Compare Source
v5.4.2: 🌈 Make sure uv installed by setup-uv is first in PATHCompare 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 specifiersCompare Source
Changes
With this release you can also use pep440 version specifiers as
required-versionin filesuv.toml,pyroject.tomland in theversioninput:🐛 Bug fixes
🧰 Maintenance
📚 Documentation
v5.4.0: 🌈 uv and uvx path as outputsCompare Source
Changes
The absolute paths to the uv and uvx binaries can now be accessed via the outputs
uv-pathanduvx-path.setup-uvnow also issues a warning if the working directory is empty. This makes users aware of the common mistake to runsetup-uvbeforeactions/checkout. You can remove the warning by settingignore-empty-workdir: true🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v5.4Compare Source
v5.3.1: 🌈 - Fix issues with GHES and HTTP proxiesCompare Source
Changes
This release fixes some issues when this action was used behind a HTTP proxy or with GHES.
If you have been seeing
ENOTFOUNDor 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 powerpcCompare 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.
@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.3Compare Source
v5.2.2: 🌈 Full support for GHESCompare 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.0Compare Source
v5.2.0 introduced TOML parsing using @iarna/toml because we already found out in
astral-sh/ruff-actionthat 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 fileCompare Source
This release adds support to derive the version of uv to be installed from
pyproject.tomlanduv.tomlfiles.If no
versioninput is defined the default is now to look for a required-version inuv.tomland thenpyproject.tomlin the repository root. If it cannot find any it falls back tolatest.If your files are at a different place you can use the new inputs
uv-fileorpyproject-file.🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
astral-sh/setup-uvtov5@njzjz (#205)⬆️ Dependency updates
v5.2Compare Source
v5.1Compare Source
v5.1.0: 🌈 Fewer cache invalidationsCompare Source
Changes
This release includes less frequently invalidated caches and a fix for setting the correct
VIRTUAL_ENV🐛 Bug fixes
🚀 Enhancements
📚 Documentation
actions/setup-pythonwith uv docu @eifinger (#207)v5.0.1: 🌈 The christmas elves overlooked somethingCompare Source
Changes
With so many breaking changes so close to the end of the year we missed something.
Thank you @ryanhiebert for quickly reporting that our new defaults fail the workflow if neither a
uv.locknor arequirements*.txtcan be found. This is now a warning instead.🐛 Bug fixes
v5.0Compare Source
v5.0.0: 🎄 Merry Christmas - Help fastly and users by defaultCompare Source
Changes
This christmans 🎄 release is a bit early bit still full of presents 🎁
Since we are changing some of the defaults this can lead to breaking changes, thus the major version increase.
Here are the highlights:
Default to enable-cache: true on GitHub hosted runners
Did you know that that Fastly, the company hosting PyPI, theoretically has to pay $12.5 million per month and so far have served more than 2.41 exabytes of data?
This is why they asked us to turn on caching by default. After weighting the pros and cons we decided to automatically upload the cache to the GitHub Actions cache when running on GitHub hosted runners. You can still disable that with
enable-cache: false.I remember when I first got into actions and didn't understand all the magic. I was baffled that some actions did something behind the scenes to make everything faster. I hope with this change we help a lot of users who are don't want to or are afraid to understand what
enable-cachedoes.Add **/requirements*.txt to default cache-dependency-glob
If caching is enabled we automatically searched for a
uv.lockfile and when this changed we knew we had to refresh the cache. A lot of projects don't use this but rather the good oldrequirements.txt. We now automatically search for bothuv.lockandrequirements*.txt(this means alsorequirements-test.txt,requirements-dev.txt, ...) files.You can change this with
cache-dependency-globAuto activate venv when python-version is set
Some workflows install packages on the fly. This automatically works when using a python version that is already present on the runner. But if uv installs the version, e.g. because it is a free-threaded version or an old one, it is a standalone-build and installing packages "into the system" is not possible.
We now automatically create a new virtual environment with
uv venvand activate it for the rest of the workflow ifpython-versionis used. This means you can now do🚨 Breaking changes
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v5Compare Source
v4.2Compare Source
v4.2.0: 🌈 Resolve latest version instead of downloading latest releaseCompare Source
Changes
We got a frist contribution from @pollenjp!
Thanks to this we are now resolving the latest version and try to find it in the local cache instead of always downloading the latest release from the uv repository.
This new approach is not only more efficient, it also fixes a latent bug in the self-hosted runners tools cache and makes the code more maintainable.
Thank you @pollenjp!
🚀 Enhancements
🧰 Maintenance
v4.1Compare Source
v4.1.0: 🌈 Set UV_PYTHON for your workflowCompare Source
Changes
You can now use the input
python-versionto set the environment variableUV_PYTHONfor the rest of your workflow.This will override any python version specifications in
pyproject.tomland.python-versionYou can combine this with a matrix to test multiple python versions:
🚀 Enhancements
🧰 Maintenance
📚 Documentation
v4.0Compare Source
v4.0.0: 🌈 Fail when cache local path does not exist when trying to cacheCompare Source
🚨 Breaking change 🚨
By default, the action will now fail if caching is enabled but there is nothing to upload (the uv cache directory does not exist).
If you want to ignore this, set the
ignore-nothing-to-cacheinput totrue.In previous releases only an error got logged when saving the cache failed. In most cases users did not realize something was wrong with their config.
Changes
🚨 Breaking changes
🐛 Bug fixes
📚 Documentation
v4Compare Source
v3.2.4: 🌈 Expand~tilde in input pathsCompare Source
This release adds support for expanding the
~character to the user's home directory for the following inputs:cache-local-pathtool-dirtool-bin-dircache-dependency-globIn order to make this work
cache-dependency-globalso got support to glob files outside the working directory:Thank you @fynnsu for raising this issue!
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v3.2.3: 🌈 update known checksums for 0.5.2Compare Source
Changes
🧰 Maintenance
v3.2.2: 🌈 Avoid leftover files by using temp dirCompare Source
Changes
The previous release left over downloaded files.
🐛 Bug fixes
v3.2.1: 🌈 Fix extracting with old PowerShell versionsCompare Source
Changes
Old PowerShell versions (5.1) have a problem with extracting files without the
.zipextension. To fix that we now make sure the extension is part of the filename.🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v3.2.0: 🌈 add option to disable cache pruningCompare Source
Changes
Big thanks to @merlinz01 for adding the option to disable the cache pruning prior to saving it to the Github Actions Cache.
This is useful if downloading the GitHub Actions cache is fast and cheap for you but downloading from an index is slow or expensive.
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v3.2Compare Source
v3.1.7: 🌈 update known checksums for 0.4.21Compare Source
Changes
🧰 Maintenance
v3.1.6: 🌈 Fix cache linebreak in linux runnerCompare Source
Changes
🐛 Bug fixes
v3.1.5: 🌈 update known checksums for 0.4.20Compare Source
Changes
🧰 Maintenance
⬆️ Dependency updates
v3.1.4: 🌈 update known checksums for 0.4.18Compare Source
Changes
🧰 Maintenance
⬆️ Dependency updates
v3.1.3: 🌈 update known checksums for 0.4.17Compare Source
Changes
🧰 Maintenance
⬆️ Dependency updates
v3.1.2: 🌈 update known checksums for 0.4.16Compare Source
Changes
🐛 Bug fixes
🧰 Maintenance
⬆️ Dependency updates
v3.1.1: 🌈 update known checksums for 0.4.15Compare Source
Changes
🧰 Maintenance
📚 Documentation
v3.1.0: 🌈 Support for semver version rangesCompare Source
You can now also use semver ranges to define the version of uv to install:
Learn more in the README
Changes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v3.1Compare Source
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate.