chore(deps): update astral-sh/setup-uv action to v5 #112
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
from
cb5543b to
1403632
Compare
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
2 times, most recently
from
b96c719 to
0367639
Compare
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
from
0367639 to
3632196
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4.2.0->v5.2.2Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
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.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.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
Configuration
📅 Schedule: Branch creation - "before 4:00am on Sunday" in timezone Asia/Tokyo, 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.
This PR was generated by Mend Renovate. View the repository job log.