Fixed GitLab cache key for Gradle dependencies.

[AlexeyKuznetsov-DD]

What Does This Do

Update GitLab cache key.

Motivation

This key should be in sync with actual Gradle version we are using to build project.

Additional Notes

We should re-populate caches once merged.

[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.02 s	13.94 s	[-0.4%; +1.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.92 s	13.00 s	[-1.3%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	16.90 s	16.77 s	[-0.2%; +1.9%] (no difference)
startup:petclinic:iast:Agent	16.83 s	16.16 s	[-5.0%; +13.4%] (unstable)
startup:petclinic:profiling:Agent	16.99 s	17.00 s	[-1.6%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	16.33 s	16.31 s	[-1.4%; +1.7%] (no difference)

Commit:d7fad56c · 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 -f --reason "GitLab cache fixed, no need to pass MQ"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-03 17:45:25 UTC ℹ️ Start processing command /merge -f --reason "GitLab cache fixed, no need to pass MQ"

---

2026-06-03 17:45:29 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-03 17:45:39 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: GitLab cache fixed, no need to pass MQ

[bric3]

👍