chore: bump ben-manes versions plugin to 0.61.0

[devondragon]

Summary

Bumps the Gradle dependency-updates plugin and adopts its non-deprecated id.

• com.github.ben-manes.versions 0.60.0 → io.github.ben-manes.versions 0.61.0

The old com.github.ben-manes.versions id is deprecated; the build emitted a configuration-time warning on every run. Switching to io.github.ben-manes.versions and bumping to 0.61.0 clears it.

Context

Ran ./gradlew dependencyUpdates -Drevision=release. This plugin id/version was the only clean actionable update:

• Spring Boot is already at 4.1.0 (latest); the whole starter set resolved at latest.
• MariaDB / PostgreSQL / jackson-datatype-jsr310 are BOM-managed by Boot and move with a future Boot bump, not individually.
• assertj-core and jakarta.validation-api only offer 4.0.0-M1 milestones — deliberately held.

Verification

Re-ran ./gradlew dependencyUpdates -Drevision=release: build successful, deprecation warning gone, plugin reports 0.61.0 as latest.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[claude]

Review

This is a clean, minimal change — just a plugin id/version bump in build.gradle, with no impact on production code.

Code quality / correctness

• The change itself is correct: io.github.ben-manes.versions is the maintained, non-deprecated id for the same plugin (com.github.ben-manes.versions was the legacy Bintray-era id), and 0.61.0 is a straightforward patch bump. Since this only affects the dependencyUpdates Gradle task (a build-time reporting tool), there's no runtime or library-consumer impact — consistent with this being a build-tooling-only library repo.
• PR description is excellent: it documents the exact command run (./gradlew dependencyUpdates -Drevision=release), explains why other flagged dependencies (Spring Boot, MariaDB/PostgreSQL, jackson-datatype-jsr310, assertj-core, jakarta.validation-api) were deliberately left alone, and confirms verification that the deprecation warning is gone. This is exactly the kind of context that makes a dependency-bump PR easy to trust.

Security

• No security concerns — this only affects a build-time convenience task, not anything shipped to consumers of the library.

Test coverage

• No tests needed/applicable for a single-line plugin version bump; this isn't functional code.

Nit (non-blocking)

• Worth double-checking CI actually passes with the new plugin id before merge (in case any other build script or CI job references the old com.github.ben-manes.versions id/task name elsewhere), though a quick grep suggests build.gradle is the only place it's declared.

Overall: safe, well-documented, low-risk change. LGTM.