Skip to content

Update github-actions - #9952

Merged
radarhere merged 1 commit into
mainfrom
renovate/github-actions
Sep 3, 2026
Merged

Update github-actions#9952
radarhere merged 1 commit into
mainfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
CodSpeedHQ/action action major v4.19.1 → v5.2.1
astral-sh/setup-uv action major v9.0.0 → v10.0.1
google/oss-fuzz (changelog) action digest 95272c1 → 404549d
pypa/gh-action-pypi-publish action patch v1.14.1 → v1.14.2
release-drafter/release-drafter action minor v7.6.0 → v7.7.0

Release Notes

CodSpeedHQ/action (CodSpeedHQ/action)

v5.2.1

Compare Source

Bumps the CodSpeed runner to v5.2.1.

🚀 Features
  • Add a simulation-track-subprocess input, which enables measuring the subprocesses spawned by the benchmarked process in simulation mode by @​adriencaccia in #​235
  • Bump the go-runner to v1.3.0, adding Go 1.26 and 1.27 support by @​adriencaccia in #​516

Full Runner Changelog:
https://github.com/CodSpeedHQ/codspeed/blob/main/CHANGELOG.md

What's Changed

Full Changelog: CodSpeedHQ/action@v5.2.0...v5.2.1

v5.2.0

Compare Source

Bumps the CodSpeed runner to v5.2.0, including v5.1.0.

🚀 Features
🐛 Bug Fixes
⚙️ Internals

Full Runner Changelog:
https://github.com/CodSpeedHQ/codspeed/blob/main/CHANGELOG.md

What's Changed

Full Changelog: CodSpeedHQ/action@v5.0.3...v5.2.0

v5.0.3

Compare Source

Bumps the CodSpeed runner to v5.0.2.

🐛 Bug Fixes

Full Runner Changelog:
https://github.com/CodSpeedHQ/codspeed/blob/main/CHANGELOG.md

What's Changed

Full Changelog: CodSpeedHQ/action@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: CodSpeedHQ/action@v5.0.1...v5.0.2

v5.0.1

Compare Source

🚀 Highlights

More precise measurements by default

cycle-estimation is now enabled by default, giving more precise benchmark cycle estimation in Simulation mode. See docs.

New: allocation exclusion

Opt in to exclude-allocations to remove allocator time from benchmarks in Simulation mode and reduce variance. See docs.

samply-based profiler by default on Linux

The walltime profiler now uses samply on all OSes. Set CODSPEED_WALLTIME_PROFILER=perf to restore the previous behavior.

⚠️ Breaking changes

  • cycle-estimation is now enabled by default (see above)
  • The samply-based profiler is now the default on Linux; set CODSPEED_WALLTIME_PROFILER=perf to revert

Details

🚀 Features
🐛 Bug Fixes
💼 Other
🏗️ Refactor
🧪 Testing
⚙️ Internals

Install codspeed-runner 5.0.1

Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/CodSpeedHQ/codspeed/releases/download/v5.0.1/codspeed-runner-installer.sh | sh

Download codspeed-runner 5.0.1

File Platform Checksum
codspeed-runner-aarch64-apple-darwin.tar.gz Apple Silicon macOS checksum
codspeed-runner-aarch64-unknown-linux-musl.tar.gz ARM64 MUSL Linux checksum
codspeed-runner-x86_64-unknown-linux-musl.tar.gz x64 MUSL Linux checksum

Full Runner Changelog: https://github.com/CodSpeedHQ/codspeed/blob/main/CHANGELOG.md

Full Changelog: CodSpeedHQ/action@v4.19.1...v5.0.1

v5.0.0

Compare Source

astral-sh/setup-uv (astral-sh/setup-uv)

v10.0.1: 🌈 Tolerate transient manifest timeouts

Compare 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 features

Compare 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: auto this will now DISABLE THE CACHE to protect against cache poisoning for the following events:

  • pull_request_target
  • workflow_run
  • release

You can read the full reasoning in #​984

version: latest-known
- name: Install the latest version of uv known to setup-uv
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version: "latest-known"

This will now install the latest version with a checksum that is known by this action. The known uv checksums 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-versions
- name: Install uv based on the version defined in .tool-versions and also set python
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version-file: "pyproject.toml"

Will 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
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)

v1.14.2

Compare 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.

[!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..

The rest of the updates bump things related to pypi-attestations and sigstore, 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.

Edge Cake XKCD feels just like this release

🫶 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.

GH Sponsors badge

release-drafter/release-drafter (release-drafter/release-drafter)

v7.7.0

Compare Source

What's Changed

New

Dependency Updates

9 changes

Bug Fixes

Maintenance

New Contributors

  • No new contributors

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • On day 3 of the month (* * 3 * *)
  • Automerge
    • At any time (no schedule defined)

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the Dependency label Sep 3, 2026
@radarhere
radarhere enabled auto-merge (squash) September 3, 2026 03:57
@radarhere
radarhere merged commit 43fe58f into main Sep 3, 2026
85 of 115 checks passed
@radarhere
radarhere deleted the renovate/github-actions branch September 3, 2026 03:58
@codspeed-hq

codspeed-hq Bot commented Sep 3, 2026

Copy link
Copy Markdown

Hooray! CodSpeed harness just leveled up!

The base and head of this comparison were measured with different runner settings, so their benchmark values are not directly comparable.

What changed between base and head:

Re-run the base with the same settings to get a valid performance comparison.

Comparing renovate/github-actions (1752bc0) with main (ecfbdd6)1

Open in CodSpeed

Footnotes

  1. No successful run was found on main (3d99acd) during the generation of this report, so ecfbdd6 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Dependency

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@radarhere