Add missing repositories to Update Gradle dependencies workflow

[sarahchen6]

What Does This Do

Add missing repositories to check when verifying age of dependencies we need to upgrade. Also add a note for future reference if other dependencies are reported as unverifiable.

Motivation

Previously, these dependency ages were reported as "unverifiable" and thus reverted, such as in: #11687.

Additional Notes

I tested the new URLs locally, but the overall workflow can be tested on master due to the trust policy (example failure).

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
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[datadog-official]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

Update Gradle dependencies | Update Gradle dependencies

Useful? React with 👍 / 👎

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

[AlexeyKuznetsov-DD]

Cool!

[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	13.99 s	13.98 s	[-0.5%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	12.88 s	12.97 s	[-1.5%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	16.34 s	16.56 s	[-5.8%; +3.2%] (no difference)
startup:petclinic:iast:Agent	16.74 s	16.81 s	[-1.3%; +0.5%] (no difference)
startup:petclinic:profiling:Agent	16.53 s	16.83 s	[-3.1%; -0.5%] (maybe better)
startup:petclinic:sca:Agent	16.81 s	16.18 s	[-0.6%; +8.4%] (no difference)
startup:petclinic:tracing:Agent	15.57 s	16.02 s	[-6.8%; +1.3%] (no difference)

Commit:b36b2212 · 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.

[sarahchen6]

/merge -f --reason "Specific to a GHA workflow, so no need to pass additional MQ tests"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-22 18:30:31 UTC ℹ️ Start processing command /merge -f --reason "Specific to a GHA workflow, so no need to pass additional MQ tests"

---

2026-06-22 18:30:36 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-06-22 18:30:46 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: Specific to a GHA workflow, so no need to pass additional MQ tests

[sarahchen6]

Confirmed in #11700 that the dependency ages can be verified now! They previously failed in #11687