Skip to content

chore(deps): drop redundant version pins managed by parent BOMs - #142

Open
TaurMorchant wants to merge 1 commit into
mainfrom
chore/clean-up-internal-boms
Open

chore(deps): drop redundant version pins managed by parent BOMs#142
TaurMorchant wants to merge 1 commit into
mainfrom
chore/clean-up-internal-boms

Conversation

@TaurMorchant

@TaurMorchant TaurMorchant commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

Remove third-party version pins that merely duplicated versions already provided by the managing BOMs, giving each library a single source of truth:

  • httpcore5, httpclient5, commons-dbcp2, jedis, freemarker, HikariCP: managed by spring-boot-dependencies via core-spring-internal-bom
  • wagon-provider-api: managed by quarkus-bom via core-quarkus-internal-bom, and not referenced by any module

Also fix a typo in the micrometer version property name (io.micrometer.verion -> io.micrometer.version) in cloud-core-java-bom.

@TaurMorchant
TaurMorchant force-pushed the chore/clean-up-internal-boms branch from f915741 to b338535 Compare August 10, 2026 12:06
Several third-party versions were pinned twice: once in one of our BOMs and
once in the BOM that one imports. Remove the duplicates so each library has a
single source of truth:

- commons-dbcp2, jedis, httpcore5, freemarker, HikariCP: managed by
  spring-boot-dependencies via core-spring-internal-bom
- wagon-provider-api: managed by quarkus-bom via core-quarkus-internal-bom

httpclient5 keeps its pin in core-internal-bom, at the version it already had.
quarkus-bom manages the HttpComponents 4.x line only and never provides a
version for httpclient5, while the Quarkus extension dbaas-opensearch-client
compiles against it through dbaas-client-opensearch-base. Dropping the pin
would leave that version unmanaged in the Quarkus reactor.

Consumers now import the internal BOMs at 1.1.0-SNAPSHOT instead of the
released 1.0.3. The reactor then builds the BOMs it consumes, so CI exercises
BOM changes in the same build rather than only after a release.

Also fix a typo in a micrometer property name in cloud-core-java-bom
(io.micrometer.verion -> io.micrometer.version).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@TaurMorchant
TaurMorchant force-pushed the chore/clean-up-internal-boms branch from b338535 to f913805 Compare August 10, 2026 13:01
@sonarqubecloud

Copy link
Copy Markdown

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.

3 participants