chore(deps): update github actions - #175
Merged
Merged
Conversation
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
June 24, 2026 05:27
4d2865a to
ab7905d
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
4 times, most recently
from
July 8, 2026 13:36
bea5b2b to
c4134a2
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
July 15, 2026 15:58
c4134a2 to
99e6c4d
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
9 times, most recently
from
July 23, 2026 21:41
166c057 to
ba45128
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
4 times, most recently
from
July 30, 2026 15:09
2ccbd21 to
1572057
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
5 times, most recently
from
August 8, 2026 02:43
abac3c9 to
f853e95
Compare
edgarrmondragon
added
chore
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
August 8, 2026 03:35
f853e95 to
fa9f6d5
Compare
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
1 participant
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:
v7.0.0→v7.0.1v4.36.2→v4.37.6v1.14.0→v1.14.2v1.72.0→v1.73.1v0.5.6→v0.6.2Release Notes
actions/checkout (actions/checkout)
v7.0.1Compare Source
github/codeql-action (github/codeql-action)
v4.37.6Compare Source
.github/codeql-config.ymlto align it with the suggested path that is used elsewhere. #4070v4.37.5Compare Source
v4.37.4Compare Source
v4.37.3Compare Source
No user facing changes.
v4.37.2Compare Source
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023v4.37.1Compare Source
v4.37.0Compare Source
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973v4.36.3Compare Source
No user facing changes.
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.
v1.14.1Compare Source
This release was cut at EuroPython 2026 Sprints
🛠️ Internal Dependencies
@adisivaprasad💰 helped get rid of the GitHub Actions runner warning about the old Node 20 runtime being used by updating
actions/setup-pythonfrom v5.6.0 to v6.2.0 in #408.💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.0...v1.14.1
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @jylenhof💰 for reminding me to work on this release!
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
reviewdog/action-actionlint (reviewdog/action-actionlint)
v1.73.1Compare Source
v1.73.0Compare Source
What's Changed
New Contributors
Full Changelog: reviewdog/action-actionlint@v1.72.1...v1.73.0
v1.73Compare Source
v1.72.1Compare Source
v1.72.1: PR #211 - fix: include digest in Docker image reference for action.yml
zizmorcore/zizmor-action (zizmorcore/zizmor-action)
v0.6.2Compare Source
zizmor 1.29.0 is now the default version.
v0.6.1Compare Source
zizmor 1.28.0 is now the default version used by the action.
v0.6.0Compare Source
zizmor 1.27.0 is now the default version used by the action.
What's Changed
collectinput by @woodruffw in #139New Contributors
Full Changelog: zizmorcore/zizmor-action@v0.5.7...v0.6.0
v0.5.7Compare Source
1.26.1 is now available via the action
1.26.1 is now the default version of zizmor used by the action
Configuration
📅 Schedule: (in timezone America/Mexico_City)
* * 1 */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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.