Improve PR description report for gradle dependency upgrade workflow

[sarahchen6]

What Does This Do

Improve the PR description that's reported in the automatically generated PRs from the Update Gradle Dependencies workflow. Notably, the number of hours until meeting the 48h cooldown requirement is mentioned and downgrades to the existing version are mentioned as just "reverted" now.

Motivation

Additional Notes

Now the PR description from #11463 would look like:

  ## Dependency age policy

  - `io.dropwizard.metrics:metrics-core:4.2.39` is 24h away from meeting 48h
  cooldown, reverted
  - `io.vertx:vertx-core-logging:5.1.0` is 24h away from meeting 48h cooldown,
  updated to `io.vertx:vertx-core-logging:5.0.12`
  - `io.vertx:vertx-uri-template:5.1.0` is 24h away from meeting 48h cooldown,
  updated to `io.vertx:vertx-uri-template:5.0.12`
  - `io.vertx:vertx-web-common:5.1.0` is 24h away from meeting 48h cooldown,
  updated to `io.vertx:vertx-web-common:5.0.12`
  - `io.vertx:vertx-web:5.1.0` is 24h away from meeting 48h cooldown, updated to
  `io.vertx:vertx-web:5.0.12`
  - `io.vertx:vertx-auth-common:5.1.0` is 24h away from meeting 48h cooldown,
  reverted
  - `io.vertx:vertx-bridge-common:5.1.0` is 24h away from meeting 48h cooldown,
  reverted
  - `io.vertx:vertx-core:5.1.0` is 24h away from meeting 48h cooldown, reverted
  - `io.vertx:vertx-eventbus-bridge-common:5.1.0` is 24h away from meeting 48h
  cooldown, reverted
  - `io.vertx:vertx-web-client:5.1.0` is 24h away from meeting 48h cooldown,
  reverted

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
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[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

Startup Time

Scenario	This PR	master	Change
insecure-bank / iast	13,906 ms	13,962 ms	-0.4%
insecure-bank / tracing	12,890 ms	12,954 ms	-0.5%
petclinic / appsec	16,564 ms	16,397 ms	+1.0%
petclinic / iast	16,500 ms	16,631 ms	-0.8%
petclinic / profiling	16,390 ms	16,479 ms	-0.5%
petclinic / tracing	15,846 ms	15,835 ms	+0.1%

Commit: 00145768 · 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 "editing PR description for dependency upgrades"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-05-27 16:46:12 UTC ℹ️ Start processing command /merge -f --reason "editing PR description for dependency upgrades"

---

2026-05-27 16:46:17 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-05-27 16:46:27 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: editing PR description for dependency upgrades