chore(build): resolve OpenTelemetry instrumentation BOM from the version catalog - #217
Open
adityamparikh wants to merge 1 commit into
Open
adityamparikh wants to merge 1 commit into
adityamparikh wants to merge 1 commit into
Conversation
adityamparikh
force-pushed
the
chore/otel-bom-version-catalog
branch
from
September 24, 2026 14:37
eadfa4a to
61364f3
Compare
…ion catalog opentelemetry-instrumentation-bom and opentelemetry-spring-boot-starter were hardcoded string literals in build.gradle.kts, invisible to catalog-driven dependency tooling. PR #82 bumped gradle/libs.versions.toml's opentelemetry-instrumentation-bom to 2.26.1 (a CVE fix) but never took effect, because build.gradle.kts still pinned the literal 2.11.0. Wire both through libs.versions.toml so future bumps to the catalog entry actually apply. The catalog version stays at 2.11.0: 2.26.1 needs io.opentelemetry.common.ComponentLoader, which Spring Boot 3.5.x's managed OTel SDK doesn't ship, and breaks native AOT (see dev-docs/graalvm-native-image.md, "Why not just bump OTel?"). This is a build-wiring fix only, no functional version change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Aditya Parikh <aditya.m.parikh@gmail.com>
adityamparikh
force-pushed
the
chore/otel-bom-version-catalog
branch
from
September 26, 2026 17:45
61364f3 to
943b7d0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
opentelemetry-instrumentation-bomandopentelemetry-spring-boot-starterwere hardcoded string literals inbuild.gradle.kts, invisible to catalog-driven dependency tooling. #82 bumpedgradle/libs.versions.toml'sopentelemetry-instrumentation-bomto2.26.1(a CVE fix) but that bump never took effect, becausebuild.gradle.ktsstill pinned the literal2.11.0— the catalog entry was silently orphaned.This wires both dependencies through the version catalog (
libs.opentelemetry.instrumentation.bom,libs.opentelemetry.spring.boot.starter) so future catalog bumps actually apply.The catalog version stays at
2.11.0— this is a build-wiring fix only, no functional version change.2.26.1needsio.opentelemetry.common.ComponentLoader, which Spring Boot 3.5.x's managed OTel SDK doesn't ship yet, and breaks native AOT (documented indev-docs/graalvm-native-image.md, "Why not just bump OTel?"). I added a comment on the catalog entry pointing at that doc so the pin doesn't look like an oversight again.Test plan
./gradlew assemble— builds clean./gradlew build -x rat(JDK 25 on PATH) — full build, all tests,spotlessApplyall pass:ratfailure is pre-existing/local-only (untracked.playwright-mcp/*.ymlfiles), unrelated to this change