Bump the gh-actions-packages group across 3 directories with 5 updates

[dependabot]

Bumps the gh-actions-packages group with 3 updates in the / directory: softprops/action-gh-release, peter-evans/create-pull-request and github/codeql-action.
Bumps the gh-actions-packages group with 1 update in the /.github/actions/create-system-test-docker-base-images directory: docker/build-push-action.
Bumps the gh-actions-packages group with 1 update in the /.github/actions/publish-debug-symbols directory: actions/setup-node.

Updates softprops/action-gh-release from 2.6.1 to 3.0.0

Release notes

Sourced from softprops/action-gh-release's releases.

v3.0.0

3.0.0 is a major release that moves the action runtime from Node 20 to Node 24. Use v3 on GitHub-hosted runners and self-hosted fleets that already support the Node 24 Actions runtime. If you still need the last Node 20-compatible line, stay on v2.6.2.

What's Changed

Other Changes 🔄

• Move the action runtime and bundle target to Node 24
• Update @types/node to the Node 24 line and allow future Dependabot updates
• Keep the floating major tag on v3; v2 remains pinned to the latest 2.x release

v2.6.2

What's Changed

Other Changes 🔄

• chore(deps): bump picomatch from 4.0.3 to 4.0.4 by @​dependabot[bot] in softprops/action-gh-release#775
• chore(deps): bump brace-expansion from 5.0.4 to 5.0.5 by @​dependabot[bot] in softprops/action-gh-release#777
• chore(deps): bump vite from 8.0.0 to 8.0.5 by @​dependabot[bot] in softprops/action-gh-release#781

Full Changelog: softprops/action-gh-release@v2...v2.6.2

Changelog

Sourced from softprops/action-gh-release's changelog.

3.0.0

3.0.0 is a major release that moves the action runtime from Node 20 to Node 24. Use v3 on GitHub-hosted runners and self-hosted fleets that already support the Node 24 Actions runtime. If you still need the last Node 20-compatible line, stay on v2.6.2.

What's Changed

Other Changes 🔄

• Move the action runtime and bundle target to Node 24
• Update @types/node to the Node 24 line and allow future Dependabot updates
• Keep the floating major tag on v3; v2 remains pinned to the latest 2.x release

2.6.2

What's Changed

Other Changes 🔄

• chore(deps): bump picomatch from 4.0.3 to 4.0.4 by @​dependabot[bot] in softprops/action-gh-release#775
• chore(deps): bump brace-expansion from 5.0.4 to 5.0.5 by @​dependabot[bot] in softprops/action-gh-release#777
• chore(deps): bump vite from 8.0.0 to 8.0.5 by @​dependabot[bot] in softprops/action-gh-release#781

2.6.1

2.6.1 is a patch release focused on restoring linked discussion thread creation when discussion_category_name is set. It fixes [#764](https://github.com/softprops/action-gh-release/issues/764), where the draft-first publish flow stopped carrying the discussion category through the final publish step.

If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.

What's Changed

Bug fixes 🐛

• fix: preserve discussion category on publish by @​chenrui333 in softprops/action-gh-release#765

2.6.0

2.6.0 is a minor release centered on previous_tag support for generate_release_notes, which lets workflows pin GitHub's comparison base explicitly instead of relying on the default range. It also includes the recent concurrent asset upload recovery fix, a working_directory docs sync, a checked-bundle freshness guard for maintainers, and clearer immutable-prerelease guidance where GitHub platform behavior imposes constraints on how prerelease asset uploads can be published.

If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.

What's Changed

... (truncated)

Commits

• b430933 release: cut v3.0.0 for Node 24 upgrade (#670)
• c2e35e0 chore(deps): bump the npm group across 1 directory with 7 updates (#783)
• 3bb1273 release 2.6.2
• c34030f chore: bump node to 24.14.1
• 8975bd0 chore(deps): bump vite from 8.0.0 to 8.0.5 (#781)
• f71937f chore(deps): bump brace-expansion from 5.0.4 to 5.0.5 (#777)
• 3f0d239 chore(deps): bump picomatch from 4.0.3 to 4.0.4 (#775)
• See full diff in compare view

Updates peter-evans/create-pull-request from 8.1.0 to 8.1.1

Release notes

Sourced from peter-evans/create-pull-request's releases.

Create Pull Request v8.1.1

What's Changed

• build(deps-dev): bump the npm group with 2 updates by @​dependabot[bot] in peter-evans/create-pull-request#4305
• build(deps): bump minimatch by @​dependabot[bot] in peter-evans/create-pull-request#4311
• build(deps): bump the github-actions group with 2 updates by @​dependabot[bot] in peter-evans/create-pull-request#4316
• build(deps): bump @​tootallnate/once and jest-environment-jsdom by @​dependabot[bot] in peter-evans/create-pull-request#4323
• build(deps-dev): bump undici from 6.23.0 to 6.24.0 by @​dependabot[bot] in peter-evans/create-pull-request#4328
• build(deps-dev): bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in peter-evans/create-pull-request#4334
• build(deps): bump picomatch by @​dependabot[bot] in peter-evans/create-pull-request#4339
• build(deps-dev): bump handlebars from 4.7.8 to 4.7.9 by @​dependabot[bot] in peter-evans/create-pull-request#4344
• build(deps-dev): bump the npm group with 3 updates by @​dependabot[bot] in peter-evans/create-pull-request#4349
• fix: retry post-creation API calls on 422 eventual consistency errors by @​peter-evans in peter-evans/create-pull-request#4356

Full Changelog: peter-evans/create-pull-request@v8.1.0...v8.1.1

Commits

• 5f6978f fix: retry post-creation API calls on 422 eventual consistency errors (#4356)
• d32e88d build(deps-dev): bump the npm group with 3 updates (#4349)
• 8170bcc build(deps-dev): bump handlebars from 4.7.8 to 4.7.9 (#4344)
• 0041819 build(deps): bump picomatch (#4339)
• b993918 build(deps-dev): bump flatted from 3.3.1 to 3.4.2 (#4334)
• 36d7c84 build(deps-dev): bump undici from 6.23.0 to 6.24.0 (#4328)
• a45d1fb build(deps): bump @​tootallnate/once and jest-environment-jsdom (#4323)
• 3499eb6 build(deps): bump the github-actions group with 2 updates (#4316)
• 3f3b473 build(deps): bump minimatch (#4311)
• 6699836 build(deps-dev): bump the npm group with 2 updates (#4305)
• See full diff in compare view

Updates github/codeql-action from 4.35.1 to 4.35.2

Release notes

Sourced from github/codeql-action's releases.

v4.35.2

• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
• The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
• Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
• Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807
• Update default CodeQL bundle version to 2.25.2. #3823

Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.35.2 - 15 Apr 2026

• The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
• The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
• Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
• Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807
• Update default CodeQL bundle version to 2.25.2. #3823

4.35.1 - 27 Mar 2026

• Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #3781

4.35.0 - 27 Mar 2026

• Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #3767
• Update default CodeQL bundle version to 2.25.1. #3773

4.34.1 - 20 Mar 2026

• Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762

4.34.0 - 20 Mar 2026

• Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
• We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #3584
• Update default CodeQL bundle version to 2.25.0. #3585

4.33.0 - 16 Mar 2026

• Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

  To opt out of this change:

  • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

• Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557

• The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #3559

• Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563

• Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564

• A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570

4.32.6 - 05 Mar 2026

... (truncated)

Commits

• 95e58e9 Merge pull request #3824 from github/update-v4.35.2-d2e135a73
• 6f31bfe Update changelog for v4.35.2
• d2e135a Merge pull request #3823 from github/update-bundle/codeql-bundle-v2.25.2
• 60abb65 Add changelog note
• 5a0a562 Update default bundle to codeql-bundle-v2.25.2
• 6521697 Merge pull request #3820 from github/dependabot/github_actions/dot-github/wor...
• 3c45af2 Merge pull request #3821 from github/dependabot/npm_and_yarn/npm-minor-345b93...
• f1c3393 Rebuild
• 1024fc4 Rebuild
• 9dd4cfe Bump the npm-minor group across 1 directory with 6 updates
• Additional commits viewable in compare view

Updates docker/build-push-action from 7.0.0 to 7.1.0

Release notes

Sourced from docker/build-push-action's releases.

v7.1.0

• Git context query format support by @​crazy-max in docker/build-push-action#1505
• Bump @​docker/actions-toolkit from 0.79.0 to 0.87.0 by @​crazy-max in docker/build-push-action#1505
• Bump brace-expansion from 1.1.12 to 1.1.13 in docker/build-push-action#1500
• Bump fast-xml-parser from 5.4.2 to 5.5.7 in docker/build-push-action#1489
• Bump flatted from 3.3.3 to 3.4.2 in docker/build-push-action#1491
• Bump glob from 10.3.12 to 10.5.0 in docker/build-push-action#1490
• Bump handlebars from 4.7.8 to 4.7.9 in docker/build-push-action#1497
• Bump lodash from 4.17.23 to 4.18.1 in docker/build-push-action#1510
• Bump picomatch from 4.0.3 to 4.0.4 in docker/build-push-action#1496
• Bump undici from 6.23.0 to 6.24.1 in docker/build-push-action#1486
• Bump vite from 7.3.1 to 7.3.2 in docker/build-push-action#1509

Full Changelog: docker/build-push-action@v7.0.0...v7.1.0

Commits

• bcafcac Merge pull request #1509 from docker/dependabot/npm_and_yarn/vite-7.3.2
• 18e62f1 Merge pull request #1510 from docker/dependabot/npm_and_yarn/lodash-4.18.1
• 46580d2 chore: update generated content
• 3f80b25 chore(deps): Bump lodash from 4.17.23 to 4.18.1
• efeec95 Merge pull request #1505 from crazy-max/refactor-git-context
• ddf04b0 Merge pull request #1511 from docker/dependabot/github_actions/crazy-max-dot-...
• db08d97 chore(deps): Bump the crazy-max-dot-github group with 2 updates
• ef1fb96 Merge pull request #1508 from docker/dependabot/github_actions/docker/login-a...
• 2d8f2a1 chore: update generated content
• 919ac7b fix test since secrets are not written to temp path anymore
• Additional commits viewable in compare view

Updates actions/setup-node from 6.3.0 to 6.4.0

Release notes

Sourced from actions/setup-node's releases.

v6.4.0

What's Changed

Dependency updates:

• Upgrade @​actions dependencies by @​Copilot in actions/setup-node#1525
• Update Node.js versions in versions.yml and bump package to v6.4.0 by @​priya-kinthali in actions/setup-node#1533

New Contributors

• @​Copilot made their first contribution in actions/setup-node#1525

Full Changelog: actions/setup-node@v6...v6.4.0

Commits

• 48b55a0 Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)
• ab72c7e Upgrade @​actions dependencies (#1525)
• 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

[andrewlock]

eep, should be ok, but always scary to see 😅

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-04-22 12:54:49

Comparing candidate commit 51810ac in PR branch dependabot/github_actions/gh-actions-packages-65ec814917 with baseline commit 3c003f8 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 27 metrics, 0 unstable metrics, 61 known flaky benchmarks, 26 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net6.0

• 🟩 throughput [+11744.691op/s; +13891.546op/s] or [+9.872%; +11.676%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

• 🟥 execution_time [+306.452ms; +308.712ms] or [+152.073%; +153.194%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

• 🟥 execution_time [+384.805ms; +386.819ms] or [+304.020%; +305.611%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

• 🟥 execution_time [+399.164ms; +400.782ms] or [+353.245%; +354.677%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net472

• 🟥 allocated_mem [+1.308KB; +1.308KB] or [+27.529%; +27.541%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net6.0

• 🟥 allocated_mem [+471 bytes; +472 bytes] or [+9.977%; +9.987%]
• 🟩 execution_time [-16.246ms; -12.068ms] or [-7.587%; -5.636%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody netcoreapp3.1

• 🟥 allocated_mem [+1.272KB; +1.272KB] or [+27.502%; +27.510%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net472

• 🟥 allocated_mem [+1.307KB; +1.307KB] or [+105.746%; +105.759%]
• 🟥 throughput [-259163.545op/s; -254025.862op/s] or [-26.462%; -25.937%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net6.0

• 🟥 allocated_mem [+471 bytes; +472 bytes] or [+38.558%; +38.566%]
• 🟩 execution_time [-26.487ms; -21.611ms] or [-11.812%; -9.637%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody netcoreapp3.1

• 🟥 allocated_mem [+1.272KB; +1.272KB] or [+105.292%; +105.304%]
• 🟥 throughput [-138972.600op/s; -123055.451op/s] or [-19.968%; -17.681%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net6.0

• 🟩 throughput [+9425.908op/s; +12352.235op/s] or [+5.998%; +7.860%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody netcoreapp3.1

• 🟩 throughput [+7338.821op/s; +9994.505op/s] or [+5.846%; +7.962%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net6.0

• 🟩 throughput [+462738.700op/s; +481275.103op/s] or [+15.430%; +16.048%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1

• 🟩 execution_time [-18.470ms; -14.123ms] or [-8.514%; -6.510%]
• 🟩 throughput [+196056.355op/s; +251798.663op/s] or [+7.782%; +9.995%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net472

• 🟥 execution_time [+300.333ms; +300.854ms] or [+150.066%; +150.327%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net6.0

• 🟥 execution_time [+300.073ms; +303.283ms] or [+151.327%; +152.946%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs netcoreapp3.1

• 🟥 execution_time [+299.716ms; +302.699ms] or [+150.974%; +152.476%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net472

• 🟥 execution_time [+297.148ms; +297.830ms] or [+145.948%; +146.282%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net6.0

• 🟥 execution_time [+294.879ms; +296.757ms] or [+144.156%; +145.074%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs netcoreapp3.1

• 🟥 execution_time [+301.678ms; +302.969ms] or [+150.778%; +151.424%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net6.0

• 🟥 execution_time [+26.269µs; +54.651µs] or [+6.025%; +12.534%]
• 🟥 throughput [-258.864op/s; -133.673op/s] or [-11.254%; -5.812%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net6.0

• 🟥 execution_time [+23.577µs; +47.198µs] or [+7.527%; +15.068%]
• 🟥 throughput [-438.098op/s; -239.350op/s] or [-13.657%; -7.461%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

• 🟥 execution_time [+299.857ms; +300.501ms] or [+149.659%; +149.981%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net6.0

• 🟥 execution_time [+408.044ms; +414.260ms] or [+443.356%; +450.111%]
• 🟩 throughput [+1087.841op/s; +1238.374op/s] or [+8.939%; +10.176%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest netcoreapp3.1

• 🟥 execution_time [+368.863ms; +372.500ms] or [+280.074%; +282.836%]
• 🟩 throughput [+740.335op/s; +939.925op/s] or [+7.167%; +9.099%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

• unstable execution_time [+358.169ms; +422.832ms] or [+164.683%; +194.414%]
• 🟥 throughput [-470.476op/s; -421.281op/s] or [-42.630%; -38.172%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

• unstable execution_time [+200.968ms; +334.167ms] or [+85.644%; +142.408%]
• 🟥 throughput [-744.462op/s; -661.045op/s] or [-49.656%; -44.092%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

• 🟥 execution_time [+335.509ms; +343.313ms] or [+200.673%; +205.341%]
• 🟥 throughput [-398.424op/s; -362.556op/s] or [-27.742%; -25.244%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net6.0

• 🟩 throughput [+26.363op/s; +37.582op/s] or [+5.204%; +7.419%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

• 🟥 execution_time [+302.336ms; +304.436ms] or [+152.251%; +153.308%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net6.0

• 🟥 execution_time [+301.844ms; +303.648ms] or [+151.254%; +152.158%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch netcoreapp3.1

• 🟥 execution_time [+299.851ms; +302.919ms] or [+150.632%; +152.174%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

• 🟥 execution_time [+302.041ms; +303.211ms] or [+151.675%; +152.263%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net6.0

• 🟥 execution_time [+298.761ms; +300.698ms] or [+147.724%; +148.682%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync netcoreapp3.1

• 🟥 execution_time [+302.633ms; +306.053ms] or [+153.388%; +155.121%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

• 🟥 execution_time [+300.401ms; +302.305ms] or [+150.774%; +151.730%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net6.0

• 🟥 execution_time [+298.168ms; +300.079ms] or [+148.610%; +149.562%]
• 🟩 throughput [+52140.517op/s; +58132.847op/s] or [+10.353%; +11.543%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync netcoreapp3.1

• 🟥 execution_time [+300.126ms; +302.788ms] or [+149.310%; +150.635%]

scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net6.0

• 🟩 execution_time [-16.001ms; -12.005ms] or [-7.441%; -5.582%]
• 🟩 throughput [+23989.716op/s; +31138.250op/s] or [+6.581%; +8.542%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net472

• unstable execution_time [+10.573µs; +52.068µs] or [+2.611%; +12.861%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net6.0

• 🟩 allocated_mem [-18.609KB; -18.588KB] or [-6.788%; -6.781%]
• unstable execution_time [-45.928µs; +6.531µs] or [-9.078%; +1.291%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark netcoreapp3.1

• 🟩 allocated_mem [-16.566KB; -16.551KB] or [-6.039%; -6.033%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net6.0

• 🟥 execution_time [+5.584µs; +9.677µs] or [+13.199%; +22.873%]
• 🟥 throughput [-4410.686op/s; -2645.641op/s] or [-18.568%; -11.137%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark netcoreapp3.1

• unstable execution_time [-13.172µs; -5.816µs] or [-20.435%; -9.024%]
• 🟩 throughput [+1481.969op/s; +3045.160op/s] or [+9.092%; +18.683%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

• 🟥 execution_time [+302.563ms; +304.708ms] or [+152.932%; +154.016%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net6.0

• 🟥 execution_time [+302.034ms; +304.271ms] or [+153.735%; +154.873%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog netcoreapp3.1

• 🟥 execution_time [+300.398ms; +302.266ms] or [+150.386%; +151.321%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net6.0

• 🟩 throughput [+36999.554op/s; +42876.823op/s] or [+7.003%; +8.116%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

• 🟥 execution_time [+300.952ms; +302.682ms] or [+149.998%; +150.860%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net6.0

• 🟥 execution_time [+301.697ms; +302.506ms] or [+151.498%; +151.904%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog netcoreapp3.1

• 🟥 execution_time [+304.182ms; +306.521ms] or [+154.261%; +155.448%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

• 🟥 execution_time [+299.743ms; +300.323ms] or [+149.513%; +149.803%]
• 🟩 throughput [+61127438.460op/s; +61386476.745op/s] or [+44.517%; +44.705%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net6.0

• unstable execution_time [+376.478ms; +409.837ms] or [+468.217%; +509.706%]
• 🟩 throughput [+1039.445op/s; +1214.913op/s] or [+8.035%; +9.392%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore netcoreapp3.1

• 🟥 execution_time [+299.252ms; +300.200ms] or [+149.260%; +149.733%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net6.0

• 🟩 throughput [+97305.438op/s; +106669.081op/s] or [+9.085%; +9.959%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1

• 🟩 throughput [+57236.578op/s; +77072.174op/s] or [+6.625%; +8.921%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net6.0

• 🟩 throughput [+88783.064op/s; +118287.558op/s] or [+6.872%; +9.156%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1

• 🟩 throughput [+97492.082op/s; +105793.155op/s] or [+9.683%; +10.507%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net6.0

• 🟩 throughput [+51904.739op/s; +57163.294op/s] or [+9.425%; +10.380%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes netcoreapp3.1

• 🟩 throughput [+33805.265op/s; +43485.416op/s] or [+7.567%; +9.733%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0

• 🟩 throughput [+59666.545op/s; +76457.691op/s] or [+6.666%; +8.542%]

Known flaky benchmarks without significant changes:

• scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472
• scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1
• scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net472
• scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net472
• scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net472
• scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark netcoreapp3.1
• scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net472
• scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack netcoreapp3.1
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net6.0
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool netcoreapp3.1
• scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice netcoreapp3.1
• scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net472
• scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog netcoreapp3.1
• scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net472
• scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net472
• scenario:Benchmarks.Trace.RedisBenchmark.SendReceive netcoreapp3.1
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net472
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net472
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1