[release] Update release.json and Go modules for 7.62.0-rc.4

[github-actions]

No description provided.

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 234771bfeff3cdf8a1209e4be7be4f069346b3b1

Diff per package

package	diff	status	size	ancestor	threshold
datadog-heroku-agent-amd64-deb	0.07MB	⚠️	505.28MB	505.21MB	70.00MB
datadog-agent-x86_64-rpm	0.02MB	⚠️	1200.36MB	1200.34MB	140.00MB
datadog-agent-x86_64-suse	0.02MB	⚠️	1200.36MB	1200.34MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.01MB	⚠️	113.42MB	113.42MB	10.00MB
datadog-iot-agent-x86_64-suse	0.01MB	⚠️	113.42MB	113.42MB	10.00MB
datadog-iot-agent-amd64-deb	0.01MB	⚠️	113.35MB	113.35MB	10.00MB
datadog-iot-agent-arm64-deb	0.01MB	⚠️	108.82MB	108.81MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	108.89MB	108.88MB	10.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.57MB	78.57MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.77MB	55.77MB	10.00MB
datadog-dogstatsd-x86_64-rpm	-0.00MB	✅	78.65MB	78.65MB	10.00MB
datadog-dogstatsd-x86_64-suse	-0.00MB	✅	78.65MB	78.65MB	10.00MB
datadog-agent-amd64-deb	-0.01MB	✅	1191.05MB	1191.05MB	140.00MB
datadog-agent-aarch64-rpm	-0.02MB	✅	944.59MB	944.61MB	140.00MB
datadog-agent-arm64-deb	-0.05MB	✅	935.29MB	935.34MB	140.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a408f03f-fc44-459c-8d06-55b0fbc67d26

Baseline: 7177c2b
Comparison: d3718e0
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+0.84	[-2.43, +4.12]	1	Logs
➖	file_tree	memory utilization	+0.54	[+0.40, +0.67]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.35	[-0.33, +1.03]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.32	[+0.23, +0.41]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.24	[-0.53, +1.02]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.20	[-0.27, +0.66]	1	Logs
➖	quality_gate_idle	memory utilization	+0.13	[+0.09, +0.16]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	+0.07	[-0.70, +0.83]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.06	[-0.74, +0.86]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.03	[-0.61, +0.68]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.00	[-0.86, +0.87]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	-0.01	[-0.89, +0.88]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.13, +0.11]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.05	[-0.74, +0.64]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.45	[-0.51, -0.39]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	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_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_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	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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

CI Pass/Fail Decision

✅ Passed. All Quality Gates 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, bounds check memory_usage: 10/10 replicas passed. Gate passed.