Update pypa/gh-action-pypi-publish action to v1.14.2 - #4308
Open
renovate-bot wants to merge 1 commit into
Open
Conversation
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
April 29, 2026 15:40
e18d198 to
1473c8d
Compare
Contributor
|
I guess this will need to wait for update from ASF infra. cc @jbonofre |
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
2 times, most recently
from
May 14, 2026 16:14
d8ee212 to
3870e62
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
May 22, 2026 18:09
3870e62 to
bb32b5f
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
May 28, 2026 13:50
bb32b5f to
62187b7
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
June 12, 2026 06:58
62187b7 to
bf35b1b
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
June 18, 2026 16:23
bf35b1b to
7dff658
Compare
Member
|
ASF infra team appreciates contributions for reviewed action updates. |
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
July 12, 2026 13:50
7dff658 to
e5045d3
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
3 times, most recently
from
July 24, 2026 14:08
02d710a to
0cfd752
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
2 times, most recently
from
July 30, 2026 16:11
4f175d2 to
6e15477
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
August 2, 2026 13:50
6e15477 to
738bcf1
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
August 11, 2026 16:44
738bcf1 to
6aeecea
Compare
renovate-bot
force-pushed
the
renovate/pypa-gh-action-pypi-publish-1.x
branch
from
August 15, 2026 02:00
6aeecea to
2e8ed07
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
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:
v1.13.0→v1.14.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
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.
v1.14.0Compare Source
Audit your supply chain regularly!
✨ What's Changed
The main change in this release is that
verboseandprint-hashinputs are now on by default. This was contributed by @whitequark💰 in #397.📝 Docs
@woodruffw💰 updated the mentions of PEP 740 to stop implying that it might be experimental (it hasn't been for quite a while!) in #388 and @him2him2💰 brushed up some grammar in the README and SECURITY docs via #395.
🛠️ Internal Updates
@woodruffw💰 bumped
sigstoreandpypi-attestationsin the lock file (#391) and @webknjaz💰 added infra for using type annotations in the project (#381).💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.13.0...v1.14.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @facutuesca💰 and @woodruffw💰 for helping maintain this project when I can't!
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
Configuration
📅 Schedule: (UTC)
🚦 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.