RUNTIME UPGRADE: go runtime go1.24.0 → go1.25.7 [tools/v2fix]

[campaigner-prod]

Summary: Security update — 1 package upgraded (MAJOR changes included)

Manifests changed:

• tools/v2fix (go)

Runtime Upgrade

This update includes a go runtime upgrade. Runtime updates require:

• Reviewing dependency compatibility with the new runtime version
• Validating critical workflows after upgrade
• Monitoring performance metrics post-deployment

Updates

Package	From	To	Type
go runtime	go1.24.0	go1.25.7	runtime

---

Security Details

⚠️ Dependencies that have Reached EOL (1)

Dependency	Unsafe Version	EOL Date	New Version	Path
go runtime	go1.24.0	Feb 11, 2026	go1.25.7	tools/v2fix/go.mod

---

Review Checklist

Standard review:

• Review changes for compatibility with your code
• Check for breaking changes in release notes
• Run tests locally or wait for CI

---

Update Mode: Runtime EOL Upgrade

🤖 Generated by DataDog Automated Dependency Management System

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-02-12 21:00:04

Comparing candidate commit 92594df in PR branch engraver-auto-version-upgrade/eol-runtime/go/v2fix/4-1770928788 with baseline commit ab547c3 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 158 metrics, 6 unstable metrics.

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 ----------------------------------'