Skip to content

chore(deps): update github actions - #391

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
CodSpeedHQ/action action minor v5.2.1 → v5.6.3
actions/deploy-pages action patch v5.0.0 → v5.0.1
actions/download-artifact action patch v8.0.1 → v8.0.2
actions/setup-node action minor v7.0.0 → v7.1.0
actions/setup-python action minor v7.0.0 → v7.1.0
actions/upload-artifact action patch v7.0.1 → v7.0.2
amannn/action-semantic-pull-request action patch v6.1.1 → v6.1.2
astral-sh/setup-uv action minor v10.0.1 → v10.3.3
codecov/codecov-action action minor v7.0.0 → v7.1.1
j178/prek-action action minor v3.0.0 → v3.1.0
pypa/gh-action-pypi-publish action patch v1.14.2 → v1.14.3
python uses-with minor 3.12 → 3.15
raven-actions/repo-files-sync action patch v0.1.0-rc.17 → v0.1.0-rc.18
release-drafter/release-drafter action minor v7.7.0 → v7.10.0

Release Notes

CodSpeedHQ/action

v5.6.3

Compare Source

Bumps the CodSpeed runner to v5.6.3, including v5.6.2.

Highlights
Go benchmark times match go test

b.Loop() benchmarks that stop and restart the timer inside an iteration now report all of their timed work. A round previously counted only the time since the most recent StartTimer, so results for those benchmarks will move.

Unsupported go test flags no longer fail the run

go test -p 1 ./... -bench . used to strip -p, parse 1 as a package, and fail with package 1 is not in std after every benchmark had passed. Flags and their values are now dropped together.

Fixed randomness in CPU Simulation

getrandom(), /dev/urandom, AT_RANDOM and hardware RNG instructions now return the same values on every CPU Simulation run, removing one source of run-to-run variance.

Fixes
  • Simulation: fix SIGILL on arm64 when programs read previously unsupported CPU ID registers or TPIDRRO_EL0 (#​59).
  • Go: benchmarks that draw from the global math/rand now start from the same seed on every run, so their results no longer vary between runs (#​596).
🚀 Features
🐛 Bug Fixes
⚙️ Internals

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

What's Changed

Full Changelog: CodSpeedHQ/action@v5.6.1...v5.6.3

v5.6.1

Compare Source

Bumps the CodSpeed runner to v5.6.1.

Fixes
  • Walltime: the runner no longer hangs after the benchmark exits when a Python process forks and leaves a corrupted perf jitdump (#​599)
  • Simulation: stop the libpython symlink warning from firing falsely (#​594)
🐛 Bug Fixes
💼 Other

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

What's Changed

New Contributors

Full Changelog: CodSpeedHQ/action@v5.6.0...v5.6.1

v5.6.0

Compare Source

Bumps the CodSpeed runner to v5.6.0.

Highlights
More consistent CPU Simulation results

Changes to your CI environment, like a different path or an extra environment variable, no longer change the performance. Each benchmark now starts with the same memory layout, reducing the chance of false regressions.

🐛 Bug Fixes
⚙️ Internals

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

What's Changed

Full Changelog: CodSpeedHQ/action@v5.5.0...v5.6.0

v5.5.0

Compare Source

Bumps the CodSpeed runner to v5.5.0.

This release adds support for Ubuntu 26.04, on both x86_64 and arm64. The officially supported distributions are now Ubuntu 22.04, 24.04 and 26.04, and Debian 12.

Profile uploads are also faster on GitHub-hosted runners, and archives larger than 5 GiB can now be uploaded.

Results from the Memory instrument are processed much faster and with less memory on large benchmarks.

This release also fixes a crash that could affect some pytest-codspeed benchmarks since v5.4.2.

🚀 Features
🐛 Bug Fixes
⚡ Performance
⚙️ Internals

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

What's Changed
New Contributors

Full Changelog: CodSpeedHQ/action@v5.4.2...v5.5.0

v5.4.2

Compare Source

Bumps the CodSpeed runner to v5.4.2, including v5.4.1.

This release improves and adds support for memory flamegraphs in C++, Python and Node.js.

Fixes flamegraphs for Python in simulation mode in the exec CLI.

🚀 Features
  • Name Python and Node.js frames in memory flamegraphs: emit their perf maps in memory mode, and harvest perf maps and JIT unwind data for memory tracking, by @​not-matthias in #​556
  • Launch node with the codspeed-node V8 flags for the current mode in codspeed exec, including through npm, npx and #!/usr/bin/env node scripts, by @​not-matthias in #​556
🐛 Bug Fixes
  • Always set PYTHONPERFSUPPORT, so Python codspeed exec targets keep their Python frames in simulation-mode flamegraphs, by @​not-matthias in #​577
  • Fix memory flamegraph stacks: restore return addresses hijacked by uretprobes in nested allocator calls, compare mapped modules against their mapping, and keep every placement of a module mapped more than once, by @​not-matthias in #​564, #​563 and #​556
  • Only pass --interpreted-frames-native-stack to node in analysis mode by @​not-matthias in #​556
  • Label dropped benchmarks in the comparison table by @​adriencaccia in #​570
⚙️ Internals

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

What's Changed

Full Changelog: CodSpeedHQ/action@v5.4.0...v5.4.2

v5.4.0

Compare Source

Bumps the CodSpeed runner to v5.4.0, including v5.3.0 and v5.3.1.

The Memory instrument now tracks physical (resident) memory and captures allocation call stacks to build memory flamegraphs. Both are enabled by default and can be turned off with the new disable-memory-track-physical and disable-memory-capture-stack inputs. Serialization is also faster on large memory benchmarks.

The action now exposes the id of the CodSpeed run as a run-id output, and CodSpeed now works on non-Ubuntu/Debian distributions such as Arch Linux.

🚀 Features
  • Track physical memory and capture allocation call stacks for memory flamegraphs, both enabled by default by @​not-matthias in #​529, #​522 and #​553
  • Expose the run id as a GitHub Actions step output by @​moha-bekh in #​551
  • Add an --experimental-disable-pythonmalloc-override flag (CODSPEED_EXPERIMENTAL_DISABLE_PYTHONMALLOC_OVERRIDE) to stop overriding the Python allocator, which can break free-threaded Python in simulation mode, by @​not-matthias in #​539
  • Apply kernel memory tunables before memory-mode runs, and fail early when the kernel has no BTF by @​not-matthias in #​507 and #​524
  • Pause producers under ring buffer pressure in memory mode, and log process stops per reason by @​not-matthias in #​543
  • Log which authentication method the run uses by @​fargito in #​521
🐛 Bug Fixes
⚡ Performance
⚙️ Internals

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

What's Changed

New Contributors

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

actions/deploy-pages

v5.0.1

Compare Source

Changelog


See details of all code changes since previous release.

⚠️ For use with products other than GitHub.com, such as GitHub Enterprise Server, please consult the compatibility table.

actions/download-artifact

v8.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/download-artifact@v8.0.1...v8.0.2

actions/setup-node

v7.1.0

Compare Source

What's Changed
Enhancements:
Bug fixes:
Documentation updates:
Dependency updates:
New Contributors

Full Changelog: actions/setup-node@v7.0.0...v7.1.0

actions/setup-python

v7.1.0

Compare Source

What's Changed
Enhancements
Dependency Upgrade
New Contributors

Full Changelog: actions/setup-python@v7.0.0...v7.1.0

actions/upload-artifact

v7.0.2

Compare Source

What's Changed
  • Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
  • Updates @​actions/artifact to v6.3.1.
New Contributors

Full Changelog: actions/upload-artifact@v7.0.1...v7.0.2

amannn/action-semantic-pull-request

v6.1.2

Compare Source

Bug Fixes
astral-sh/setup-uv

v10.3.3: 🌈 Use Astral mirror for version manifests with GitHub fallback

Compare Source

Changes

This release contains something that should have been included a very long time ago. Sorry for sleeping on that.

This action now retrieves the release manifest that contains the available versions, their download links and checksums from the Astral mirror, rather than trying GitHub first. This should present much more stable.
(Known checksums are still checked, so the security impact does not change)

Also a big thank you to @​soujasK for a set of bugfixes 👏

🐛 Bug fixes
🧰 Maintenance
📚 Documentation

v10.3.2: 🌈 update known checksums for 0.13.5

Compare Source

Changes
🧰 Maintenance
📚 Documentation

v10.3.1: 🌈 preserve cache error class names in save-cache bundle

Compare Source

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates

v10.3.0: 🌈 Add Python architecture selection

Compare Source

Changes

This release adds the python-arch input to select a Python architecture independently of the Python version. With uv 0.13.0 or later, set python-arch: x86_64 to use x64 Python on Windows ARM64 runners.

It also includes embedded checksums for uv releases through 0.13.0.

🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates

v10.2.0: 🌈 Disable automatic cache saves for merge queues

Compare Source

Changes

This release contains the known-checksum of the most recent uv releases and also disabled the uploading(saving) of the cache when in a merge queue since theses caches would almost never be used.

🚀 Enhancements

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates

v10.1.0: 🌈 New output python-runtime-idand respect NO_PROXY

Compare Source

Changes

This release adds more bheind the scene security improvements and also 2 small improvements.

NO_PROXY

This action now respects no_proxy/NO_PROXY environment variables which were previously ignored.

New output python-runtime-id

The new output python-runtime-id can be used to know which python version exactly was installed if you use activate-environment. See pyca/cryptography#15572 (comment) for details on why this can be useful.

🐛 Bug fixes

🚀 Enhancements

🧰 Maintenance

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/London)

  • Branch creation
    • Between 12:00 AM and 06:59 AM, only on Monday (* 0-6 * * 1)
  • 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 requested a review from worgarside as a code owner October 19, 2026 03:04
@worgarside-dev worgarside-dev added the github-actions Pull requests that update GitHub Actions code label Oct 19, 2026
@renovate
renovate Bot force-pushed the renovate/github-actions branch 2 times, most recently from b9f074d to 9980028 Compare October 24, 2026 13:13
@renovate
renovate Bot force-pushed the renovate/github-actions branch 2 times, most recently from 249cba4 to db49789 Compare November 1, 2026 04:02
@renovate
renovate Bot force-pushed the renovate/github-actions branch from db49789 to 79d89ec Compare November 7, 2026 03:48

This branch has not been deployed

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

Labels

github-actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant