Bumps the github-actions group with 2 updates: CodSpeedHQ/action and pypa/gh-action-pypi-publish.

Updates CodSpeedHQ/action from 4.18.5 to 5.0.1

Sourced from CodSpeedHQ/action's releases.

v5.0.1

🚀 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

• Load eBPF through a delegated BPF token by @​GuillaumeLagrange
• Enable cycle estimation and allocation exclusion by default by @​not-matthias in #461
• Make samply profiler default for all OSes (#472) by @​GuillaumeLagrange in #475

🐛 Bug Fixes

• Classify mapped libraries without init-userns privilege by @​GuillaumeLagrange
• Disable allocator exclusion by default (#489) by @​not-matthias in #489

💼 Other

• Bump the memtrack pin to 1.4.0 by @​adriencaccia in #484

🏗️ Refactor

• Hook-based CPU isolation for the walltime runner by @​GuillaumeLagrange

🧪 Testing

• Run every tracking test under both BPF variants by @​GuillaumeLagrange

⚙️ Internals

• chore: bump runner version to 5.0.1 by @​github-actions[bot] in CodSpeedHQ/action#228
• docs: bump documented action version to v5 by @​adriencaccia in CodSpeedHQ/action#227
• Bump submodule to reduce debug info server timeouts by @​GuillaumeLagrange
• Make tests run release builds of the binaries by @​GuillaumeLagrange in #456
• Update submodule to fix fmt and ignore ubuntu debuginfod serv by @​GuillaumeLagrange

Install codspeed-runner 5.0.1

Install prebuilt binaries via shell script

</tr></table> 

... (truncated)

• 8847237 Release v5.0.1 🚀
• 81795c3 fix: remove yanked 5.0.0 version hash
• eaace14 docs: bump documented action version to v5
• a3e4fe0 chore: bump runner version to 5.0.1
• f87ba88 Release v5.0.0 🚀
• 7ab72f2 chore: bump runner version to 5.0.0
• f22792b Release v4.19.1 🚀
• b07ddfb chore: bump runner version to 4.19.1
• 9c498ab Release v4.19.0 🚀
• a65d9f0 chore: bump runner version to 4.19.0
• See full diff in compare view

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

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)

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

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