Bump com.google.cloud:spring-cloud-gcp-dependencies from 7.4.5 to 8.0.1

[dependabot]

Bumps com.google.cloud:spring-cloud-gcp-dependencies from 7.4.5 to 8.0.1.

Release notes

Sourced from com.google.cloud:spring-cloud-gcp-dependencies's releases.

v8.0.1

8.0.1 (2026-03-09)

Spring Boot 4.0 / Spring 7 Migration This release marks a major architectural upgrade, moving the project baseline to Java 17 (with JDK 25 for Native Image) and Jakarta EE 11. This version focuses on achieving compatibility with the new modular architecture of Spring Boot 4.0, the refactored SpEL evaluation engine in Spring Data 2025.1, and enhanced AOT support for GraalVM. For a comprehensive overview of upstream changes, please refer to the official Spring Boot 4.0 Migration Guide.

⚠️ Breaking Changes

• Spring Data 4.0 (SpEL Evaluation): Multiple constructors removed due to the removal of QueryMethodEvaluationContextProvider. Users must migrate to constructors accepting ValueExpressionDelegate. Affected Classes: DatastoreQueryLookupStrategy, GqlDatastoreQuery, SpannerQueryLookupStrategy, SqlSpannerQuery. User Action: If you manually instantiate these classes (e.g., in custom repository implementations), you must replace the QueryMethodEvaluationContextProvider parameter with ValueExpressionDelegate.

• Mapping Exceptions: In Spring Data 4.0 (2025.1), metadata discovery and entity mapping failures are now uniformly wrapped in a top-level org.springframework.data.mapping.MappingException. Impact: Previously caught module-specific exceptions (e.g., SpannerDataException) may now be nested inside a MappingException. User Action: Update error handling logic to check for the underlying cause. "Use NestedExceptionUtils.getMostSpecificCause() to retrieve specific error message details.."

• Nested Exceptions: Following Spring Framework 7.0's changes to NestedRuntimeException, nested exception messages are no longer automatically appended to the top-level getMessage() output. User Action: When constructing custom error messages, you must now explicitly access the cause. "Use NestedExceptionUtils.getMostSpecificCause() to retrieve specific error message details."

• Actuator Health API: The Actuator Health API has been restructured to support better grouping through the org.springframework.boot.health.contributor package. PubSubHealthIndicator and SpannerHealthIndicator are now registered as HealthContributor beans. User Action: These indicators are now always wrapped into a CompositeHealthContributor by the framework's auto-configuration. Users who previously injected PubSubHealthIndicator or HealthIndicator directly must now inject HealthContributor and navigate the composite hierarchy if direct access is needed.

Dependencies

• bump org.springframework.boot:spring-boot-dependencies from 3.5.3 to 4.0.0
• bump org.springframework.cloud:spring-cloud-dependencies from 2025.0.0 to 2025.1.0
• bump com.google.cloud:cloud-sql-socket-factory-bom from 1.25.0 to 1.28.0
• bump io.r2dbc:r2dbc-postgresql from 1.0.7.RELEASE to 1.1.1.RELEASE
• bump org.graalvm.buildtools:native-maven-plugin from 0.10.5 to 0.11.3
• bump jakarta.annotation:jakarta.annotation-api from 1.3.5 to 2.1.1
• bump com.fasterxml.jackson:jackson-bom from 2.18.2 to 3.0.2 (via tools.jackson)

Changelog

Sourced from com.google.cloud:spring-cloud-gcp-dependencies's changelog.

[8.0.1] Spring Boot 4.0 / Spring 7 Migration

This release marks a major architectural upgrade, moving the project baseline to Java 17 (with JDK 25 for Native Image) and Jakarta EE 11. This version focuses on achieving compatibility with the new modular architecture of Spring Boot 4.0, the refactored SpEL evaluation engine in Spring Data 2025.1, and enhanced AOT support for GraalVM. For a comprehensive overview of upstream changes, please refer to the official Spring Boot 4.0 Migration Guide.

⚠️ Breaking Changes

• Spring Data 4.0 (SpEL Evaluation): Multiple constructors removed due to the removal of QueryMethodEvaluationContextProvider. Users must migrate to constructors accepting ValueExpressionDelegate.
  • Affected Classes: DatastoreQueryLookupStrategy, GqlDatastoreQuery, SpannerQueryLookupStrategy, SqlSpannerQuery.
  • User Action: If you manually instantiate these classes (e.g., in custom repository implementations), you must replace the QueryMethodEvaluationContextProvider parameter with ValueExpressionDelegate.
• Mapping Exceptions: In Spring Data 4.0 (2025.1), metadata discovery and entity mapping failures are now uniformly wrapped in a top-level org.springframework.data.mapping.MappingException.
  • Impact: Previously caught module-specific exceptions (e.g., SpannerDataException) may now be nested inside a MappingException.
  • User Action: Update error handling logic to check for the underlying cause. "Use NestedExceptionUtils.getMostSpecificCause() to retrieve specific error message details.."
• Nested Exceptions: Following Spring Framework 7.0's changes to NestedRuntimeException, nested exception messages are no longer automatically appended to the top-level getMessage() output.
  • User Action: When constructing custom error messages, you must now explicitly access the cause. "Use NestedExceptionUtils.getMostSpecificCause() to retrieve specific error message details."
• Actuator Health API: The Actuator Health API has been restructured to support better grouping through the org.springframework.boot.health.contributor package. PubSubHealthIndicator and SpannerHealthIndicator are now registered as HealthContributor beans.
  • User Action: These indicators are now always wrapped into a CompositeHealthContributor by the framework's auto-configuration. Users who previously injected PubSubHealthIndicator or HealthIndicator directly must now inject HealthContributor and navigate the composite hierarchy if direct access is needed.

Dependencies

• bump org.springframework.boot:spring-boot-dependencies from 3.5.3 to 4.0.0
• bump org.springframework.cloud:spring-cloud-dependencies from 2025.0.0 to 2025.1.0
• bump com.google.cloud:cloud-sql-socket-factory-bom from 1.25.0 to 1.28.0
• bump io.r2dbc:r2dbc-postgresql from 1.0.7.RELEASE to 1.1.1.RELEASE
• bump org.graalvm.buildtools:native-maven-plugin from 0.10.5 to 0.11.3
• bump jakarta.annotation:jakarta.annotation-api from 1.3.5 to 2.1.1
• bump com.fasterxml.jackson:jackson-bom from 2.18.2 to 3.0.2 (via tools.jackson)

Commits

• 0a98082 chore(main): release 8.0.1 (#4364)
• 1f7395f fix(deps): remove versionless Jackson 3 dependencies from BOM (#4363)
• 580ebfd chore(main): release 8.0.1-SNAPSHOT (#4362)
• 4112bd3 chore(main): release 8.0.0 (#4337)
• a9ac189 feat!: Migrate Spring Cloud GCP to Spring Boot 4.0 and Spring Framework 7.0 b...
• cac7213 chore: add 7.x branch to CI and release configurations (#4356)
• 87153c1 chore: Add multi-branch release automation script (#4338)
• 5bf1b41 docs: update latest versions in README (#4335)
• 003fdbd chore(main): release 7.4.6-SNAPSHOT (#4334)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)