Add Spring Data MongoDB 5 dependency alignment

[Kyran121]

What changed

• This branch is based directly on the current upstream main; the Spring Data 4 foundation from Introduce Spring Data 4 migration foundation #1087 is already merged.

• Add org.openrewrite.java.spring.data.MigrateSpringDataMongoDb5.

• Compose it into UpgradeSpringData_4_0.

• Scope the recipe to modules that resolve org.springframework.data:spring-data-mongodb, including transitive use through Spring Boot MongoDB starters.

• Upgrade explicitly versioned or unmanaged spring-data-mongodb 4.x dependencies to 5.0.x.

• Align explicitly pinned, supported MongoDB Java Driver dependencies below 5.6 to 5.6.x.

• Keep managed, versionless dependencies versionless and remove stale explicit overrides when Spring Boot supplies the compatible target.

• Preserve compatible forward overrides.

• Leave MongoDB driver-only modules and deliberately excluded driver artifacts unchanged.

• Regenerate src/main/resources/META-INF/rewrite/recipes.csv using recipeCsvGenerate.

Explicit MongoDB allow-list

The recipe aligns only these explicitly declared artifacts to 5.6.x:

• org.mongodb:mongodb-driver-bom
• org.mongodb:mongodb-driver-core
• org.mongodb:mongodb-driver-sync
• org.mongodb:mongodb-driver-reactivestreams
• org.mongodb:mongodb-crypt
• org.mongodb:bson
• org.mongodb:bson-record-codec
• org.mongodb:mongodb-driver-legacy

Boundary decisions

• mongodb-driver-bom is upgraded first, while dependencies managed by the BOM remain versionless.
• mongodb-driver-legacy is version-aligned but is not replaced with mongodb-driver-sync; artifact and API replacement belongs in a separate source migration.
• The removed org.mongodb:mongo-java-driver uber JAR is not rewritten to a nonexistent 5.6 line.
• Individually pinned Kotlin and Scala driver artifacts are not changed by this Spring Data-specific recipe.
• Driver-only modules that do not resolve Spring Data MongoDB are outside the recipe precondition.

Dependency behaviour covered

• Explicit unmanaged Maven and Gradle dependencies are upgraded.
• An explicitly imported MongoDB Driver BOM is upgraded while its managed components remain versionless.
• Spring Boot-managed versionless dependencies remain unchanged.
• Stale explicit versions that become redundant with Boot management are removed.
• Explicit driver overrides are upgraded when Spring Data MongoDB is present transitively through a Boot starter.
• Spring Data MongoDB and driver versions newer than the target lines are not downgraded.
• Excluded Java, Kotlin, and Scala driver artifacts remain unchanged.

Tests

The clean rebased branch passed all of the following in GitHub Actions run 29866417761:

./gradlew recipeCsvValidateCompleteness --stacktrace

./gradlew test \
  --tests org.openrewrite.java.spring.data.MigrateSpringDataMongoDb5Test \
  --tests org.openrewrite.java.spring.data.UpgradeSpringData_4_0Test \
  --stacktrace

./gradlew --console=plain --info --stacktrace --warning-mode=all --no-daemon build

Test coverage includes Maven and Gradle dependencies, managed and unmanaged versions, MongoDB Driver BOM management, transitive Spring Boot starter use, compatible forward overrides, excluded artifacts, unrelated driver-only modules, and integration through UpgradeSpringData_4_0.

Metadata

recipeCsvGenerate added MigrateSpringDataMongoDb5 with a recipe count of 10 and updated UpgradeSpringData_4_0 from 21 to 31 composed recipes.

• closes [Spring Data MongoDB 5.0] Add migration composite and dependency alignment #1082.
• Part of [Tracking] Add Spring Data MongoDB 5.0 migration support #1081.

[timtebeek]

It's not immediately clear to me how this relates to some of the newly opened issues:

• [Spring Data 4.0] Align stale Spring Data release-train BOM overrides #1091
• [Spring Data MongoDB 5.0] Replace removed MongoDB Java Driver uber JARs #1092
• [Spring Data MongoDB 5.0] Migrate MongoDB legacy API usage to the current sync API #1093

Since we also already had

• [Spring Data MongoDB 5.0] Add migration composite and dependency alignment #1082
• [Tracking] Add Spring Data MongoDB 5.0 migration support #1081

From our side we're fine to only have a single high over issue, with details only in the PR. That saves us from repeatedly triaging issues when the work is relatively straightforward.

[timtebeek]

Thanks for the change here! I've applied a slight bit of polish, but we can merge once CI passes.

[Kyran121]

It's not immediately clear to me how this relates to some of the newly opened issues:

• [Spring Data 4.0] Align stale Spring Data release-train BOM overrides #1091
• [Spring Data MongoDB 5.0] Replace removed MongoDB Java Driver uber JARs #1092
• [Spring Data MongoDB 5.0] Migrate MongoDB legacy API usage to the current sync API #1093

Since we also already had

• [Spring Data MongoDB 5.0] Add migration composite and dependency alignment #1082
• [Tracking] Add Spring Data MongoDB 5.0 migration support #1081

From our side we're fine to only have a single high over issue, with details only in the PR. That saves us from repeatedly triaging issues when the work is relatively straightforward.

That makes sense. My intention was:

#1082 covered the dependency alignment implemented by this PR.
#1092 and #1093 captured the two follow-up areas deliberately left outside this PR: replacing the removed uber JARs and migrating legacy driver API usage.
#1091 is datastore-neutral and relates to the broader UpgradeSpringData_4_0 work rather than specifically to MongoDB.

I’m happy to simplify this. I can close #1091, #1092, and #1093, keep the MongoDB roadmap consolidated under #1081, and put the detailed scope for each future change in its implementation PR instead.