Skip to content

Update CodSpeedHQ/action action to v5.6.0 - #4515

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/github-actions
Oct 27, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
CodSpeedHQ/action action minor v5.2.1 → v5.6.0

Release Notes

CodSpeedHQ/action

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 enabled auto-merge (rebase) October 27, 2026 00:49
@netlify

netlify Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for nf-core-main-site ready!

Name Link
🔨 Latest commit 21f08d9
🔍 Latest deploy log https://app.netlify.com/projects/nf-core-main-site/deploys/6ae0332f4de987df5429aa45
😎 Deploy Preview https://deploy-preview-4515--nf-core-main-site.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot deleted a comment from netlify Bot Oct 27, 2026
@renovate
renovate Bot force-pushed the renovate/github-actions branch from e62f435 to 21f08d9 Compare October 27, 2026 05:14
@renovate
renovate Bot merged commit ac36dcf into main Oct 27, 2026
12 checks passed
@renovate
renovate Bot deleted the renovate/github-actions branch October 27, 2026 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants