Skip to content

chore: migrate flyway to 12.10.0 - #135

Draft
TaurMorchant wants to merge 1 commit into
mainfrom
chore/update-flyway-to-12.10.x
Draft

chore: migrate flyway to 12.10.0#135
TaurMorchant wants to merge 1 commit into
mainfrom
chore/update-flyway-to-12.10.x

Conversation

@TaurMorchant

Copy link
Copy Markdown
Collaborator

No description provided.

@sonarqubecloud

Copy link
Copy Markdown

@TaurMorchant
TaurMorchant marked this pull request as draft July 24, 2026 11:18
TaurMorchant added a commit that referenced this pull request Aug 17, 2026
Bring the change from PR #135 into the Spring Boot 4.1.0 migration so both land
together. Flyway is pinned in core-internal-bom, which is imported before the
Spring Boot and Quarkus BOMs, so the version applies to both stacks.

Drop the competing pin from dbaas-client-bom-internal. It declared Flyway
11.20.3 directly, and a direct entry wins over an imported BOM, so the dbaas
modules would have stayed on 11.x. The public dbaas-client-bom does not manage
Flyway, so consumers keep resolving it through core-internal-bom.
TaurMorchant added a commit that referenced this pull request Aug 17, 2026
Bring the change from PR #135 into the Spring Boot 4.1.0 migration so both land
together. Flyway is pinned in core-internal-bom, which is imported before the
Spring Boot and Quarkus BOMs, so the version applies to both stacks.

Drop the competing pin from dbaas-client-bom-internal. It declared Flyway
11.20.3 directly, and a direct entry wins over an imported BOM, so the dbaas
modules would have stayed on 11.x. The public dbaas-client-bom does not manage
Flyway, so consumers keep resolving it through core-internal-bom.
TaurMorchant added a commit that referenced this pull request Aug 18, 2026
Spring Boot 4.1.0 and Quarkus 3.33.3.1 manage several shared libraries at
different versions. Shared pure-Java modules compile against whatever this BOM
manages, while the Quarkus runtime then supplies its own version, so the gap
surfaces at runtime rather than at build time. The Micrometer pin already covers
one instance of this; these pins cover the rest.

Follow the Quarkus version in each case: Kafka 4.1.2, OpenTelemetry 1.57.0,
MongoDB driver 5.6.4, Caffeine 3.2.3, PostgreSQL 42.7.13, SnakeYAML 2.5,
Byte Buddy 1.17.8, Hamcrest 2.2, Protobuf 4.33.2, gRPC 1.81.0, JAXB 4.0.8,
ClassMate 1.7.1, JBoss Logging 3.6.2.Final, Jakarta JSON Bind 3.0.1 and
Kotlin 2.3.10. Every pin carries the version each platform ships, so the next
platform upgrade shows whether it is still needed.

Move Flyway down from 12.10.0 to the Quarkus version 12.0.0. The 11.x to 12.x
migration from PR #135 stays; what goes is the only pin that ran ahead of both
platforms.

spring-kafka-test pulls kafka-clients with the test classifier, which is a
separate managed key, so it gets its own entry on kafka.version.

Drop the local mongodb.version from mongo-evolution-java. It held
mongodb-driver-sync at 5.6.5 while driver-core resolved from the BOM at 5.6.4,
leaving the driver split across two versions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
TaurMorchant added a commit that referenced this pull request Aug 18, 2026
Bring the change from PR #135 into the Spring Boot 4.1.0 migration so both land
together. Flyway is pinned in core-internal-bom, which is imported before the
Spring Boot and Quarkus BOMs, so the version applies to both stacks.

Drop the competing pin from dbaas-client-bom-internal. It declared Flyway
11.20.3 directly, and a direct entry wins over an imported BOM, so the dbaas
modules would have stayed on 11.x. The public dbaas-client-bom does not manage
Flyway, so consumers keep resolving it through core-internal-bom.
TaurMorchant added a commit that referenced this pull request Aug 18, 2026
Spring Boot 4.1.0 and Quarkus 3.33.3.1 manage several shared libraries at
different versions. Shared pure-Java modules compile against whatever this BOM
manages, while the Quarkus runtime then supplies its own version, so the gap
surfaces at runtime rather than at build time. The Micrometer pin already covers
one instance of this; these pins cover the rest.

Follow the Quarkus version in each case: Kafka 4.1.2, OpenTelemetry 1.57.0,
MongoDB driver 5.6.4, Caffeine 3.2.3, PostgreSQL 42.7.13, SnakeYAML 2.5,
Byte Buddy 1.17.8, Hamcrest 2.2, Protobuf 4.33.2, gRPC 1.81.0, JAXB 4.0.8,
ClassMate 1.7.1, JBoss Logging 3.6.2.Final, Jakarta JSON Bind 3.0.1 and
Kotlin 2.3.10. Every pin carries the version each platform ships, so the next
platform upgrade shows whether it is still needed.

Move Flyway down from 12.10.0 to the Quarkus version 12.0.0. The 11.x to 12.x
migration from PR #135 stays; what goes is the only pin that ran ahead of both
platforms.

spring-kafka-test pulls kafka-clients with the test classifier, which is a
separate managed key, so it gets its own entry on kafka.version.

Drop the local mongodb.version from mongo-evolution-java. It held
mongodb-driver-sync at 5.6.5 while driver-core resolved from the BOM at 5.6.4,
leaving the driver split across two versions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants