Bump the ci-dependencies group with 4 updates

[dependabot]

Bumps the ci-dependencies group with 4 updates: astral-sh/setup-uv, CodSpeedHQ/action, hynek/build-and-inspect-python-package and pypa/gh-action-pypi-publish.

Updates astral-sh/setup-uv from 9.0.0 to 10.0.1

Release notes

Sourced from astral-sh/setup-uv's releases.

v10.0.1 🌈 Tolerate transient manifest timeouts

Changes

Thank you @​arguile- for making this action more resilient.

🐛 Bug fixes

• Tolerate transient manifest timeouts @​arguile- (#1016)

🧰 Maintenance

• chore: update known checksums for 0.12.4 @github-actions[bot] (#1017)

📚 Documentation

• docs: update version references to v10.0.0 @github-actions[bot] (#1014)

v10.0.0 🌈 Disable automatic caching for sensitive events and new QOL features

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 astral-sh/setup-uv#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"
</tr></table> 

... (truncated)

Commits

• 20cfd1b chore: update known checksums for 0.12.4 (#1017)
• d73a0ca Tolerate transient manifest timeouts (#1016)
• ae3b92d docs: update version references to v10.0.0 (#1014)
• ae62891 chore(deps): roll up Dependabot updates (#1013)
• f9cdb47 Reject paths in .tool-versions (#1007)
• 4f6036f Require pull requests for Dependabot rollups (#1005)
• 8d6402c chore(deps): roll up Dependabot updates (#1004)
• 46f427b Read Python version from .tool-versions (#996)
• 8ed89c5 ci: pin Alpine container image (#995)
• 8473c7f chore(deps): roll up Dependabot updates (#994)
• Additional commits viewable in compare view

Updates CodSpeedHQ/action from 4.18.5 to 5.2.1

Release notes

Sourced from CodSpeedHQ/action's releases.

v5.2.1

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

• feat: add simulation-track-subprocess input by @​adriencaccia in CodSpeedHQ/action#235
• chore: bump runner version to 5.2.1 by @​github-actions[bot] in CodSpeedHQ/action#236

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

v5.2.0

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

🚀 Features

• Add a --simulation-track-subprocess flag that enables tracking benchmark subprocesses, along with per-thread dumps by @​GuillaumeLagrange in #493 and #513
• Collect RSS via rss_stat and folio-rmap reconstruction by @​not-matthias in #453
• Support CircleCI for GitHub repositories by @​fargito in #482

🐛 Bug Fixes

• Fix cache behavior that was causing an apt reinstall of the libc debug symbols despite cache restore by @​GuillaumeLagrange in #509

⚙️ Internals

• Bump pinned valgrind-codspeed to 3.26.0-0codspeed7 by @​adriencaccia in #515
  • fix(callgrind): represent os threads under --separate-threads=yes by @​GuillaumeLagrange in CodSpeedHQ/valgrind-codspeed#24
  • feat(callgrind): track subprocesses across fork and exec by @​GuillaumeLagrange in CodSpeedHQ/valgrind-codspeed#25
• Stop skipping the rustup wrapper for valgrind by @​GuillaumeLagrange in #493

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

What's Changed

• fix: add the distribution to the instruments cache key by @​GuillaumeLagrange in CodSpeedHQ/action#233
• chore: bump runner version to 5.1.0 by @​github-actions[bot] in CodSpeedHQ/action#232
• chore: bump runner version to 5.2.0 by @​github-actions[bot] in CodSpeedHQ/action#234

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

v5.0.3

... (truncated)

Commits

• 373d686 Release v5.2.1 🚀
• 5659c65 chore: bump runner version to 5.2.1 (#236)
• 22d40ad feat: add simulation-track-subprocess input (#235)
• 47f7ceb Release v5.2.0 🚀
• d9ce15a chore: bump runner version to 5.2.0 (#234)
• 994a9cf chore: bump runner version to 5.1.0 (#232)
• 15e6538 fix: add the distribution to the instruments cache key
• 4296e51 Release v5.0.3 🚀
• 271ae6a chore: bump runner version to 5.0.2 (#230)
• 0ca9cbb Release v5.0.2 🚀
• Additional commits viewable in compare view

Updates hynek/build-and-inspect-python-package from 2.18.0 to 3.0.1

Release notes

Sourced from hynek/build-and-inspect-python-package's releases.

v3.0.1

Fixed

• To avoid uv configuration interference with the project that is being built, the installation of our own tools is now ran in a different directory. Additionally, UV_EXCLUDE_NEWER is unset. #240

v3.0.0

Security

• Given the increase and supply-chain attacks and advancements in tooling (for example, pinact or GitHub's Dependabot), this action will stop force-tagging minor and micro releases. This means, there will be no @v3 or @v3.0 tag that gets updated and force-pushed with each update. Always tag with the full version and commit hash; use Zizmor to secure your actions if you can.

Changed

• Only updates of actions and build dependencies, notably including Twine 7 that adds support for packaging metadata 2.5 and PEP 794 – Import Name Metadata.

Changelog

Sourced from hynek/build-and-inspect-python-package's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

3.0.1 - 2026-07-30

Fixed

• To avoid uv configuration interference with the project that is being built, the installation of our own tools is now ran in a different directory. Additionally, UV_EXCLUDE_NEWER is unset. #240

3.0.0 - 2026-07-30

Security

• Given the increase and supply-chain attacks and advancements in tooling (for example, pinact or GitHub's Dependabot), this action will stop force-tagging minor and micro releases. This means, there will be no @v3 or @v3.0 tag that gets updated and force-pushed with each update. Always tag with the full version and commit hash; use Zizmor to secure your actions if you can.

Changed

• Only updates of actions and build dependencies, notably including Twine 7 that adds support for packaging metadata 2.5 and PEP 794 – Import Name Metadata.

2.18.0 - 2026-05-11

Added

• New input: skip-sdist to skip building the source distribution. #228

2.17.0 - 2026-03-27

Fixed

• The action now passes Zizmor in pedantic mode. #212

... (truncated)

Commits

• 2abe76d v3.0.1
• 24fa838 Switch to /tmp/baipp when syncing our tools (#240)
• c6bb487 Start next cycle
• 12fab95 v3.0.0
• c1f438b Announce changes to versioning
• 444be5d Add changelog
• 86390fb update actions (#238)
• b21444c Bump Python dependencies (#237)
• fdf34a9 update actions
• 60bf0a2 docs: calm down section casing
• 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

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

[codspeed]

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:

• CodSpeed runner v5 changed how benchmarks are measured (base 4.18.4 → head 5.2.1). View release notes
• Cycle estimation (off → on) changes how benchmark performance is calculated. Learn more about cycle estimation

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

---

_{Comparing dependabot/github_actions/ci-dependencies-0603fa888e (ebf3a7b) with main (6a20dd4)}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.29%. Comparing base (6a20dd4) to head (ebf3a7b).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #168   +/-   ##
=======================================
  Coverage   88.29%   88.29%           
=======================================
  Files           3        3           
  Lines          94       94           
=======================================
  Hits           83       83           
  Misses         11       11           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.