chore(deps): update astral-sh/setup-uv action to v5 #112
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.1.0
Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
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-python
with 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.lock
nor arequirements*.txt
can 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-cache
does.Add **/requirements*.txt to default cache-dependency-glob
If caching is enabled we automatically searched for a
uv.lock
file 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.lock
andrequirements*.txt
(this means alsorequirements-test.txt
,requirements-dev.txt
, ...) files.You can change this with
cache-dependency-glob
Auto 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 venv
and activate it for the rest of the workflow ifpython-version
is 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.