Bump astral-sh/setup-uv from 4.2.0 to 5.1.0 by dependabot[bot] · Pull Request #4625 · python-telegram-bot/python-telegram-bot
v5.1.0 🌈 Fewer cache invalidations
Changes
This release includes less frequently invalidated caches and a fix for setting the correct VIRTUAL_ENV
🐛 Bug fixes
- Set VIRTUAL_ENV to .venv instead of .venv/bin
@eifinger(#210)
🚀 Enhancements
- Remove uv version from cache key
@eifinger(#206)
📚 Documentation
- Align use of
actions/setup-pythonwith uv docu@eifinger(#207)
v5.0.1 🌈 The christmas elves overlooked something
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 a requirements*.txt can be found. This is now a warning instead.
🐛 Bug fixes
- Fix wrong cacheDependencyPathHash
@eifinger(#201) - Warn instead of fail for no-dependency-glob
@eifinger(#200)
v5.0.0 🎄 Merry Christmas - Help fastly and users by default
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 old requirements.txt. We now automatically search for both uv.lockand requirements*.txt (this means also requirements-test.txt, requirements-dev.txt, ...) files.
You can change this with cache-dependency-glob
... (truncated)