Bump the gha-updates group in /.github/workflows with 3 updates

[dependabot]

Bumps the gha-updates group in /.github/workflows with 3 updates: py-cov-action/python-coverage-comment-action, pypa/gh-action-pypi-publish and zizmorcore/zizmor-action.

Updates py-cov-action/python-coverage-comment-action from 4.1 to 4.3

Release notes

Sourced from py-cov-action/python-coverage-comment-action's releases.

v4.3

What's Changed

• Improve release procedure by @​ewjoachim in py-cov-action/python-coverage-comment-action#739

Full Changelog: py-cov-action/python-coverage-comment-action@v4.2...v4.3

v4.2

What's Changed

• Zizmor, Linting, documentation by @​ewjoachim in py-cov-action/python-coverage-comment-action#738

Full Changelog: py-cov-action/python-coverage-comment-action@v4.1...v4.2

Commits

• a05be3d Merge pull request #739 from py-cov-action/improve-release
• ef991b3 Avoid full checkout
• a5496e3 Exclude renovate form auto-notes
• bf8a28f Lock file maintenance (#733)
• 8207f4b Merge pull request #738 from py-cov-action/persist-credentials-and-workflow-lint
• 89461f2 ci: link the e2e repositories from the deployment
• 1c01767 ci: run the end-to-end tests in their own job
• c64623c ci: keep the e2e tokens available to ci.yml
• a5a7a09 chore: check that action.yml and the docs agree on the inputs
• f7bf75b docs: document USE_GH_PAGES_HTML_URL
• Additional commits viewable in compare view

Updates pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

v1.14.2

🛠️ 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.

[!tip] So what most people will find useful is @​takluyver💰's update of Twine to v7 that we use internally (#416). This version will let them upload their sdists and wheels containing core packaging metadata v2.5 to (Test)PyPI.

🧐 Tell me why..

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

• @​davidbrochart made their first contribution in #415
• @​takluyver made their first contribution in #416

🪞 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][release discussion].

[![GH Sponsors badge]][GH Sponsors URL]

... (truncated)

Commits

• dc37677 Merge pull request #417 from trail-of-forks/ft/bump-deps
• 8b2f234 Bump pypi-attestations and sigstore
• 78b72db Merge pull request #416 from takluyver/twine-v7
• 92f4d2a Update twine to v7
• See full diff in compare view

Updates zizmorcore/zizmor-action from 0.6.0 to 0.6.2

Release notes

Sourced from zizmorcore/zizmor-action's releases.

v0.6.2

zizmor 1.29.0 is now the default version.

v0.6.1

zizmor 1.28.0 is now the default version used by the action.

Commits

• 3dc1ecc Sync zizmor versions (#149)
• dc57e30 chore(deps): bump the github-actions group with 3 updates (#147)
• d94880a README: bump pins (#146)
• 6fc4b00 Sync zizmor versions (#145)
• 2596f29 chore(deps): bump github/codeql-action/upload-sarif from 4.36.3 to 4.37.0 in ...
• 1159a04 Bump pins (#140)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.