Closed burkedavison closed 3 months ago
If Spring Cloud GCP 5.x aims to maintain compatibility with Spring Boot 3.2.x and 3.3.x, it could be dangerous to upgrade to Spring Boot 3.3.x. Sticking with 3.2.x would avoid accidentally using API which is not available in Spring Boot 3.2.x.
Or will compatibility with Spring Boot 3.2.x be guaranteed in some other way?
@breun : Agreed with your concern. We'll have an answer before merging.
Compatibility table updates from https://github.com/GoogleCloudPlatform/spring-cloud-gcp/pull/3000 merged here + added an exception for trace module compatibility. Main branch testing now include Spring Boot 3.2 sample tests.
Issues
6 New issues
0 Accepted issues
Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code
Fixes #2917
Spring Boot 3.3.x upgraded Brave and Zipkin dependencies by a major version with significant backward incompatibilities. For this reason, the trace module which uses them is unable to be maintained with support for Spring Boot 3.2.x.
Testing has been added to ensure Spring Boot 3.2.x support is maintained for all modules except Trace.