[ci]: Bump the ci-dependencies group with 3 updates

[dependabot]

Bumps the ci-dependencies group with 3 updates: pypa/gh-action-pypi-publish, re-actors/alls-green and release-drafter/release-drafter.

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 re-actors/alls-green from 1.2.2 to 1.3.0

Release notes

Sourced from re-actors/alls-green's releases.

v1.3.0

🛡️ What's Unmessed

[!caution]

There was a small command injection risk in prior versions. I consider it very low because of the specifics of the action use case. But still, do upgrade, okay?

@​illera88💰 fixed this template injection bug in #37 by passing inputs via env vars.

See GHSA-gj76-h2ch-5m76 for more detail that was first reported by @​Corbynx010💰 while I was at EuroPython.

✨ What's Improved

I did a bunch of internal refactoring including hints of what @​max-sixty💰 reported in #23. And took a small patch of @​krokofant💰 in. This involved a bunch of preparatory infra work with testing infra.

One notable improvement is that now thanks to @​tomasr8💰's and @​hugovk💰's UX suggestions in #31, the gate status output is colored in the console and should be easier to scan in the log output per line. They entries now have leading ✓/❌ acceptance marks and the actual incoming job outcomes are labeled with 🟢/🔴/⬜/⚫.

🐛 What's Fixed

The job-statuses summary could print "Some of the allowed to be skipped jobs did not succeed" based on the wrong condition — it's now tied to allowed-skips as intended, not allowed-failures.

💪 New Contributors

• @​Corbynx010💰 lurked in GHSA-gj76-h2ch-5m76 before everyone else 😉
• @​illera88 made their first contribution in #37 and GHSA-gj76-h2ch-5m76
• @​krokofant and @​max-sixty first contributed in #23
• @​tomasr8 and @​hugovk in #31

🪞 Full Diff: re-actors/alls-green@v1.2.2...v1.3.0

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

Commits

• b5b5b37 Merge pull request #38 from re-actors/pre-commit-ci-update-config
• bd6edd6 [pre-commit.ci] pre-commit autoupdate
• 3967c81 💅 Make the output easier to scan
• e68df08 💅 Style job statuses title with a 🔮
• 62d37b2 🧪 Unxfail 'success-of-some-allowed-to-skip-or-fail'
• 7b5df6d 💅 Add a Codecov badge to README
• 2410c4c 🐛 Correct reporting failed skipped jobs
• 6457593 💅 Add a GH Sponsors badge
• a617895 💅 Add a pre-commit.ci badge
• 8de05dc 🧪 Force ctrace core in coveragepy
• Additional commits viewable in compare view

Updates release-drafter/release-drafter from 7.6.0 to 7.7.0

Release notes

Sourced from release-drafter/release-drafter's releases.

v7.7.0

What's Changed

New

• feat: no new contributor template (#1687) @​cchanche
• feat: categorize PRs based on conventional title (#1556) @​cchanche
• feat: log all config sources (#1674) @​jetersen

Dependency Updates

• build(deps-dev): bump postcss from 8.5.17 to 8.5.23 (#1683) @​dependabot[bot]
• chore(deps): update npm tool constraint to 12.0.1 (#1668) @​renovate[bot], @​cchanche
• chore(deps): update npm tool constraint to 11.18.0 (#1665) @​renovate[bot], @​cchanche
• chore(deps): update node.js to v24.18.0 (#1664) @​renovate[bot]
• build(deps): support GraphQL 17 (#1678) @​jetersen
• build(deps-dev): Update js-yaml to 4.3.0 (#1677) @​jetersen
• build(deps-dev): bump shell-quote from 1.8.4 to 1.10.0 (#1676) @​dependabot[bot]
• build(deps): bump immutable from 5.1.5 to 5.1.9 (#1675) @​dependabot[bot]
• build(deps-dev): bump brace-expansion from 5.0.6 to 5.0.7 (#1672) @​dependabot[bot]

Bug Fixes

• fix: preserve proxy-aware fetch in octokit client (#1682) @​jetersen

Maintenance

• chore: update references to branch master to main (#1686) @​cchanche
• ci: rely on conventional pr titles (#1685) @​cchanche

New Contributors

• No new contributors

Full Changelog: release-drafter/release-drafter@v7.6.0...v7.7.0

Commits

• 34d8067 chore: release v7.7.0
• cd773d2 style: format and lint docs
• 14d2d94 feat: no new contributor template (#1687)
• 94daa9e chore: update references to branch master to main (#1686)
• b195e66 ci: rely on conventional pr titles (#1685)
• 246878a build(deps-dev): bump postcss from 8.5.17 to 8.5.23 (#1683)
• c3acaa7 fix: preserve proxy-aware fetch in octokit client (#1682)
• 22a22c8 chore(deps): update npm tool constraint to 12.0.1 (#1668)
• 133e592 chore(deps): update npm tool constraint to 11.18.0 (#1665)
• b806fc0 chore(deps): update node.js to v24.18.0 (#1664)
• Additional commits viewable 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