Update formatters to latest version. Move versions to catalog. Minor reformatting of code.

[AlexeyKuznetsov-DD]

What Does This Do

Update formatters to latest version. Move versions to catalog. Minor reformatting of code.

Motivation

Keep latest tooling up to date.
Simplify future updates.

Additional Notes

Latest Scala formatter produced a little bit of noise, but not that much.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[sarahchen6]

TIL we have chinese in the repo

[sarahchen6]

pre-approving (looks like spotless failed) 🙂

[AlexeyKuznetsov-DD]

pre-approving (looks like spotless failed) 🙂

@sarahchen6 Yep, that was my fault, I forgot to provide that AKKA key locally
Fxied.

[datadog-prod-us1-3]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 57.92% (-0.02%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 96bbdb4 | Docs | Datadog PR Page | Give us feedback!}

[datadog-prod-us1-3]

More details

The formatter catalog resolves from Kotlin DSL, Groovy DSL, applied scripts, child projects, and a reused configuration cache; whitespace-only source comparisons and version-alignment checks found no behavioral hazard.

Was this helpful? React 👍 or 👎

_{📊 Validated against 10 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit da9008b · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.92 s	[-0.1%; +1.5%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	12.99 s	[-1.0%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	17.49 s	17.35 s	[-0.3%; +1.9%] (no difference)
startup:petclinic:iast:Agent	17.43 s	17.54 s	[-1.5%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	17.22 s	17.49 s	[-2.5%; -0.6%] (maybe better)
startup:petclinic:sca:Agent	17.48 s	17.32 s	[-0.1%; +1.9%] (no difference)
startup:petclinic:tracing:Agent	16.61 s	16.61 s	[-1.1%; +1.0%] (no difference)

Commit: 96bbdb4c · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[AlexeyKuznetsov-DD]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-07 20:36:35 UTC ℹ️ Start processing command /merge

---

2026-08-07 20:36:39 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-08-07 21:31:43 UTC ℹ️ MergeQueue: This merge request was merged