Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 15, 2025

Bumps actions/upload-artifact from 4.4.3 to 6.0.0.

Release notes

Sourced from actions/upload-artifact's releases.

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/upload-artifact@v4...v5.0.0

v4.6.2

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.6.2

v4.6.1

What's Changed

... (truncated)

Commits
  • b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
  • e516bc8 docs: correct description of Node.js 24 support in README
  • ddc45ed docs: update README to correct action name for Node.js 24 support
  • 615b319 chore: release v6.0.0 for Node.js 24 support
  • 017748b Merge pull request #744 from actions/fix-storage-blob
  • 38d4c79 chore: rebuild dist
  • 7d27270 chore: add missing license cache files for @​actions/core, @​actions/io, and mi...
  • 5f643d3 chore: update license files for @​actions/artifact@​5.0.1 dependencies
  • 1df1684 chore: update package-lock.json with @​actions/artifact@​5.0.1
  • b5b1a91 fix: update @​actions/artifact to ^5.0.0 for Node.js 24 punycode fix
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.4.3 to 6.0.0.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@b4b15b8...b7c566a)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-version: 6.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested review from a team as code owners December 15, 2025 20:13
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Dec 15, 2025
@agent-platform-auto-pr
Copy link
Contributor

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor ad46512

Successful checks

Info

Quality gate Delta On disk size (MiB) Delta On wire size (MiB)
agent_deb_amd64 $${+0.03}$$ $${706.33}$$ < $${707.13}$$ $${+0.01}$$ $${173.29}$$ < $${174.16}$$
agent_deb_amd64_fips $${+0.03}$$ $${702.55}$$ < $${702.86}$$ $${-0.03}$$ $${172.57}$$ < $${173.5}$$
agent_heroku_amd64 $${0}$$ $${327.51}$$ < $${327.92}$$ $${+0}$$ $${87.24}$$ < $${88.21}$$
agent_msi $${0}$$ $${570.41}$$ < $${982.08}$$ $${+0}$$ $${142.5}$$ < $${143.49}$$
agent_rpm_amd64 $${+0.03}$$ $${706.31}$$ < $${707.12}$$ $${+0.05}$$ $${176.42}$$ < $${177.29}$$
agent_rpm_amd64_fips $${+0.03}$$ $${702.53}$$ < $${702.85}$$ $${-0.08}$$ $${175.38}$$ < $${176.32}$$
agent_rpm_arm64 $${+0.02}$$ $${688.02}$$ < $${691.67}$$ $${+0.04}$$ $${159.45}$$ < $${160.7}$$
agent_rpm_arm64_fips $${+0.02}$$ $${685.06}$$ < $${687.54}$$ $${-0.02}$$ $${159.16}$$ < $${160.11}$$
agent_suse_amd64 $${+0.03}$$ $${706.31}$$ < $${707.12}$$ $${+0.05}$$ $${176.42}$$ < $${177.29}$$
agent_suse_amd64_fips $${+0.03}$$ $${702.53}$$ < $${702.85}$$ $${-0.08}$$ $${175.38}$$ < $${176.32}$$
agent_suse_arm64 $${+0.02}$$ $${688.02}$$ < $${691.67}$$ $${+0.04}$$ $${159.45}$$ < $${160.7}$$
agent_suse_arm64_fips $${+0.02}$$ $${685.06}$$ < $${687.54}$$ $${-0.02}$$ $${159.16}$$ < $${160.11}$$
docker_agent_amd64 $${+0.03}$$ $${768.57}$$ < $${769.38}$$ $${+0.01}$$ $${261.17}$$ < $${262.06}$$
docker_agent_arm64 $${+0.02}$$ $${774.81}$$ < $${778.35}$$ $${-0}$$ $${250.27}$$ < $${251.72}$$
docker_agent_jmx_amd64 $${+0.03}$$ $${959.45}$$ < $${960.26}$$ $${-0}$$ $${329.8}$$ < $${330.69}$$
docker_agent_jmx_arm64 $${+0.02}$$ $${954.41}$$ < $${957.95}$$ $${-0}$$ $${314.89}$$ < $${316.35}$$
docker_cluster_agent_amd64 $${+0}$$ $${179.41}$$ < $${179.56}$$ $${+0}$$ $${63.44}$$ < $${64.14}$$
docker_cluster_agent_arm64 $${0}$$ $${195.36}$$ < $${196.79}$$ $${+0.01}$$ $${59.75}$$ < $${60.69}$$
docker_cws_instrumentation_amd64 $${0}$$ $${7.13}$$ < $${7.18}$$ $${+0}$$ $${2.99}$$ < $${3.33}$$
docker_cws_instrumentation_arm64 $${+0}$$ $${6.69}$$ < $${6.92}$$ $${+0}$$ $${2.73}$$ < $${3.09}$$
docker_dogstatsd_amd64 $${+0}$$ $${38.75}$$ < $${39.38}$$ $${-0}$$ $${15.0}$$ < $${15.82}$$
docker_dogstatsd_arm64 $${0}$$ $${37.06}$$ < $${37.94}$$ $${+0}$$ $${14.33}$$ < $${14.83}$$
dogstatsd_deb_amd64 $${0}$$ $${29.97}$$ < $${30.61}$$ $${-0}$$ $${7.93}$$ < $${8.79}$$
dogstatsd_deb_arm64 $${0}$$ $${28.13}$$ < $${29.11}$$ $${+0}$$ $${6.81}$$ < $${7.71}$$
dogstatsd_rpm_amd64 $${0}$$ $${29.97}$$ < $${30.61}$$ $${+0}$$ $${7.94}$$ < $${8.8}$$
dogstatsd_suse_amd64 $${0}$$ $${29.97}$$ < $${30.61}$$ $${+0}$$ $${7.94}$$ < $${8.8}$$
iot_agent_deb_amd64 $${0}$$ $${42.73}$$ < $${43.29}$$ $${-0}$$ $${11.19}$$ < $${12.04}$$
iot_agent_deb_arm64 $${0}$$ $${39.87}$$ < $${40.92}$$ $${+0}$$ $${9.57}$$ < $${10.45}$$
iot_agent_deb_armhf $${0}$$ $${40.44}$$ < $${41.03}$$ $${-0}$$ $${9.76}$$ < $${10.62}$$
iot_agent_rpm_amd64 $${0}$$ $${42.73}$$ < $${43.29}$$ $${+0}$$ $${11.21}$$ < $${12.06}$$
iot_agent_suse_amd64 $${0}$$ $${42.73}$$ < $${43.29}$$ $${+0}$$ $${11.21}$$ < $${12.06}$$

@cit-pr-commenter
Copy link

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: f0aa2eb2-bfd1-4816-b6ac-30fc38e9e279

Baseline: d1bd251
Comparison: 4a046d0
Diff

❌ Experiments with retried target crashes

This is a critical error. One or more replicates failed with a non-zero exit code. These replicates may have been retried. See Replicate Execution Details for more information.

  • docker_containers_memory

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI trials links
docker_containers_cpu % cpu utilization +0.73 [-2.31, +3.78] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_logs % cpu utilization +1.33 [-0.13, +2.80] 1 Logs bounds checks dashboard
docker_containers_cpu % cpu utilization +0.73 [-2.31, +3.78] 1 Logs
otlp_ingest_logs memory utilization +0.45 [+0.35, +0.54] 1 Logs
ddot_metrics memory utilization +0.18 [-0.06, +0.42] 1 Logs
ddot_logs memory utilization +0.13 [+0.05, +0.20] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.06 [-0.31, +0.44] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.01 [-0.11, +0.14] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.08, +0.07] 1 Logs
uds_dogstatsd_to_api_v3 ingress throughput -0.00 [-0.13, +0.12] 1 Logs
ddot_metrics_sum_cumulativetodelta_exporter memory utilization -0.01 [-0.24, +0.21] 1 Logs
file_to_blackhole_100ms_latency egress throughput -0.01 [-0.06, +0.03] 1 Logs
file_to_blackhole_1000ms_latency egress throughput -0.02 [-0.41, +0.38] 1 Logs
file_to_blackhole_0ms_latency egress throughput -0.04 [-0.44, +0.36] 1 Logs
quality_gate_idle_all_features memory utilization -0.13 [-0.17, -0.09] 1 Logs bounds checks dashboard
uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization -0.16 [-0.22, -0.10] 1 Logs
docker_containers_memory memory utilization -0.23 [-0.30, -0.16] 1 Logs
otlp_ingest_metrics memory utilization -0.25 [-0.41, -0.10] 1 Logs
file_tree memory utilization -0.27 [-0.33, -0.22] 1 Logs
quality_gate_idle memory utilization -0.29 [-0.34, -0.25] 1 Logs bounds checks dashboard
ddot_metrics_sum_delta memory utilization -0.30 [-0.49, -0.10] 1 Logs
ddot_metrics_sum_cumulative memory utilization -0.36 [-0.51, -0.21] 1 Logs
quality_gate_metrics_logs memory utilization -0.86 [-1.06, -0.66] 1 Logs bounds checks dashboard
tcp_syslog_to_blackhole ingress throughput -1.18 [-1.25, -1.11] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed links
docker_containers_cpu simple_check_run 10/10
docker_containers_memory memory_usage 10/10
docker_containers_memory simple_check_run 10/10
file_to_blackhole_0ms_latency lost_bytes 10/10
file_to_blackhole_0ms_latency memory_usage 10/10
file_to_blackhole_1000ms_latency lost_bytes 10/10
file_to_blackhole_1000ms_latency memory_usage 10/10
file_to_blackhole_100ms_latency lost_bytes 10/10
file_to_blackhole_100ms_latency memory_usage 10/10
file_to_blackhole_500ms_latency lost_bytes 10/10
file_to_blackhole_500ms_latency memory_usage 10/10
quality_gate_idle intake_connections 10/10 bounds checks dashboard
quality_gate_idle memory_usage 10/10 bounds checks dashboard
quality_gate_idle_all_features intake_connections 10/10 bounds checks dashboard
quality_gate_idle_all_features memory_usage 10/10 bounds checks dashboard
quality_gate_logs intake_connections 10/10 bounds checks dashboard
quality_gate_logs lost_bytes 10/10 bounds checks dashboard
quality_gate_logs memory_usage 10/10 bounds checks dashboard
quality_gate_metrics_logs cpu_usage 10/10 bounds checks dashboard
quality_gate_metrics_logs intake_connections 10/10 bounds checks dashboard
quality_gate_metrics_logs lost_bytes 10/10 bounds checks dashboard
quality_gate_metrics_logs memory_usage 10/10 bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment Variant Replicates Failure Logs Debug Dashboard
experiment_with_failures baseline 0 (x8) 1 (x6) Oom killed Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Normal Replicate Execution Failures (non-profiling)

Experiment Variant Replicates Failure Debug Dashboard
docker_containers_memory baseline 8 Crashed (exit code: 1) Debug Dashboard

CI Pass/Fail Decision

Passed. All Quality Gates passed.

  • quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.

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

Labels

changelog/no-changelog dependencies PRs that bump a dependency dependencies-github-actions dev/tooling qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly team/agent-devx

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant