Repository navigation
chore(deps): update github actions - #3754
Merged
Merged
Conversation
Docker Image SizesCPU
CUDA
XPU
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
AlexanderBarabanov
approved these changes
Sep 1, 2026
This branch was previously deployed
This file contains hidden or 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
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:
v9.0.0→v10.0.1v4.5.1→v4.6.0v4.2.0→v4.3.04cda84d→4360b52v4.37.3→v4.37.8v4.37.9v0.83.4→v0.87.4v0.87.10(+5)v2→v3.0.0v1.14.1→v1.14.2v46.1.21→v46.2.4v46.2.543.285.3→44.41.144.53.0(+35)v2.20.0→v2.21.0v2.21.1v3.96.0→v3.97.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v10.0.1: 🌈 Tolerate transient manifest timeoutsCompare Source
Changes
Thank you @arguile- for making this action more resilient.
🐛 Bug fixes
🧰 Maintenance
📚 Documentation
v10.0.0: 🌈 Disable automatic caching for sensitive events and new QOL featuresCompare Source
Changes
Another breaking release, directly after v9.0.0 but we think the added security justifies that.
Extra security by default
If you use the default
enable-cache: autothis will now DISABLE THE CACHE to protect against cache poisoning for the following events:pull_request_targetworkflow_runreleaseYou can read the full reasoning in #984
version: latest-knownThis will now install the latest version with a checksum that is known by this action. The known
uvchecksums are automatically updated but will take a release of this action to take effect. You won't be always using the latest & greatest but you will have an extra level of security.Read python version from
.tool-versionsWill now also set the python version if it is defined in
.tool-versions. You can read the details in the docs🚨 Breaking changes
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
docker/login-action (docker/login-action)
v4.6.0Compare Source
Full Changelog: docker/login-action@v4.5.2...v4.6.0
v4.5.2Compare Source
Full Changelog: docker/login-action@v4.5.1...v4.5.2
docker/setup-buildx-action (docker/setup-buildx-action)
v4.3.0Compare Source
Full Changelog: docker/setup-buildx-action@v4.2.0...v4.3.0
github/codeql-action (github/codeql-action)
v4.37.8Compare Source
No user facing changes.
v4.37.7Compare Source
v4.37.6Compare Source
.github/codeql-config.ymlto align it with the suggested path that is used elsewhere. #4070v4.37.5Compare Source
initAction instead of falling back to downloading the bundle before extracting it. #4061v4.37.4Compare Source
toolsinput for thecodeql-action/initstep to be specified using agithub-codeql-toolsrepository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value totoolcacheto always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided fortoolsin the workflow definition always takes precedence unless the value of the repository property starts with!. #4037github/gh-aw-actions (github/gh-aw-actions)
v0.87.4Compare Source
Sync of actions from gh-aw at
v0.87.4.v0.87.2Compare Source
Sync of actions from gh-aw at
v0.87.2.v0.87.1Compare Source
Sync of actions from gh-aw at
v0.87.1.v0.87.0Compare Source
Sync of actions from gh-aw at
v0.87.0.v0.86.3Compare Source
Sync of actions from gh-aw at
v0.86.3.v0.86.2Compare Source
Sync of actions from gh-aw at
v0.86.2.v0.86.1Compare Source
Sync of actions from gh-aw at
v0.86.1.v0.86.0Compare Source
Sync of actions from gh-aw at
v0.86.0.j178/prek-action (j178/prek-action)
v3.0.0Compare Source
prek-actionreleases are now immutableStarting with v3,
prek-actionwill no longer publish moving major or minor tags. References such asj178/prek-action@v3andj178/prek-action@v3.0will not be available.Moving tags can be retargeted after users adopt them, creating unnecessary supply-chain risk. Use an exact release tag or, for stronger protection, pin the action to a full commit SHA.
What's Changed
Full Changelog: j178/prek-action@v2...v3.0.0
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.14.2Compare Source
This one probably won't touch you visibly so just bookmark @webknjaz's EuroPython 2026 “AI” slop rant for when it's published on YouTube or encourage him to come back with more to share next year!
🛠️ Urgh… Another release!? Again? Explain yourself!
Looking at the diff, you'll only witness updates across the dependency tree. That's it! It's not a security fix or anything like that even, no. But you'll want this update.
🧐 Tell me why..
The rest of the updates bump things related to
pypi-attestationsandsigstore, which has the most interesting backstory here. @facutuesca💰 sent a patch in #417 but a bunch more helped out.TL;DR non-pure-python projects with C-extensions tend to have dozens (sometimes hundreds) wheels to upload to PyPI per release. They are often quite big and take time to transfer over the network. People started noticing problems and coming up with DIY sharding workarounds like aio-libs/aiohttp#13226 around July 23.
On this date, projects with a good amount of bytes to publish would start getting timeouts 5 minutes after the PyPI publishing job begun. The same job that worked just fine before.
I had to start pinging upstream library and ecosystem people, on GitHub and privately, to start making sense of what was happening. Eventually, we collectively concluded that GitHub must've shortened the lifetime of their OIDC identity — it seems to have used to be 10 minutes long (at some point in the past) and is now 5 minutes, apparently. It's not documented clearly, and we have not been able to get any clarity by attempting to contact GitHub through private channels, using personal connections.
Over the course of investigation, @facutuesca💰 found and fixed a related underlying cache invalidation bug in sigstore/sigstore-python#1838, which he then coordinated propagation through the dependency chain updates in sigstore-python, pypi-attestations, gh-action-pypi-publish and gh-action-sigstore-python.
Mike's also discovered that Sigstore's Rekor slowdown seems to have become the main contributing cause of the last week's incident. He's collected some data to support this claim: https://publishing-five-minute-timeout.tiiny.site.
🫶 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.1...v1.14.2
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @davidbrochart💰 and @Dreamsorcerer💰 for turning my attention (in #415 and in private) to the newly surfaced corner case in GitHub's behavior that only affected a narrow category of projects while many others remained blissfully unaware. @bdraco💰 came up with a DIY sharding workaround for aiohttp that served as a demo for other projects. @miketheman💰 confirmed the Warehouse-side details. Also, @jku💰 and @woodruffw💰 helped work through, review and release the Sigstore ecosystem upstream libs.
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
renovatebot/github-action (renovatebot/github-action)
v46.2.4Compare Source
Documentation
Build System
v46.2.3Compare Source
Documentation
Miscellaneous Chores
Build System
Continuous Integration
v46.2.2Compare Source
Documentation
Miscellaneous Chores
Build System
Continuous Integration
v46.2.1Compare Source
Documentation
Miscellaneous Chores
Build System
Continuous Integration
v46.2.0Compare Source
Features
Documentation
Miscellaneous Chores
Continuous Integration
renovatebot/renovate (renovatebot/renovate)
v44.41.1Compare Source
Bug Fixes
v44.41.0Compare Source
Features
overrideDescriptionoption (#45400) (9d0e535)v44.40.1Compare Source
Bug Fixes
Miscellaneous Chores
v44.40.0Compare Source
Features
Documentation
4fad234(main) (#45407) (9ce288e)Miscellaneous Chores
v44.39.3Compare Source
Bug Fixes
Miscellaneous Chores
v44.39.2Compare Source
Bug Fixes
Continuous Integration
v44.39.1Compare Source
Bug Fixes
Miscellaneous Chores
Configuration
📅 Schedule: (UTC)
* * 1 * *)🚦 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 these updates again.
This PR has been generated by Mend Renovate.