[release] Update release.json and Go modules for 7.58.1-rc.1

[kacper-murzyn]

[pr-commenter[bot]]

Regression Detector

Regression Detector Results

Run ID: 91ac7f12-e718-4acc-bd7b-348170611d68 Metrics dashboard Target profiles

Baseline: c84ce81df517874ef43cf646ba00054ec2e1fed1 Comparison: b1242de3fe563320f695a39b6855453810965cf5

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	file_tree	memory utilization	+0.97	[+0.86, +1.08]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+0.41	[-0.42, +1.24]	1	Logs
➖	basic_py_check	% cpu utilization	+0.21	[-2.52, +2.94]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	idle	memory utilization	-0.02	[-0.07, +0.02]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.39	[-0.44, -0.34]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.17	[-1.90, -0.44]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	-1.21	[-3.89, +1.47]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
❌	idle	memory_usage	4/10

Explanation

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