Jackie-Jiang opened a new pull request, #19772:
URL: https://github.com/apache/pinot/pull/19772
## Summary
Upgrades the Google libraries and tidies the related dependency management
in the root POM.
Upgrades:
- `libraries-bom` 26.89.0 → 26.90.0.
- Guava 33.6.0-jre → 33.7.2-jre, through a new `guava-bom` import placed
ahead of `libraries-bom`. `libraries-bom` otherwise pins Guava through
`first-party-dependencies` → `gapic-generator-java-bom` →
`guava-bom:33.6.0-jre`, and the first imported BOM wins.
Dependency management cleanup:
- Drop the explicit `protobuf-java`, `protobuf-java-util` and
`protobuf-kotlin` pins. The `protobuf-bom` import manages exactly these three
artifacts at the same `${protobuf.version}` and is imported ahead of
`libraries-bom` (which brings `protobuf-bom:4.33.6`), so protobuf still
resolves to 4.36.2. Protobuf now follows the same import-first approach as gRPC
and Guava; the pins from #18322 only silenced Maven 4's BOM-import conflict
warnings, which Maven 4 builds will report again for protobuf as they already
do for gRPC and Guava.
- Pin `com.google.cloud.opentelemetry:detector-resources-support` (new
`google.cloud.opentelemetry.version` property) and group it with
`opentelemetry-gcp-resources`. In `libraries-bom` 26.90.0,
`google-cloud-storage` 2.75.0 and `google-cloud-nio` 0.139.0 request different
versions of both (0.31.0 / 0.33.0 and 1.37.0-alpha / 1.45.0-alpha), which fails
dependency convergence.
- Pin `org.jspecify:jspecify` 1.0.1. Guava 33.7.2 requests 1.0.1 while
`pulsar-client` 4.0.13 requests 1.0.0.
- Manage `jsr305` and `jspecify` next to `checker-qual` as nullness
annotations instead of as convergence pins. Every generated `package-info.java`
is annotated with `@javax.annotation.ParametersAreNonnullByDefault` and
`@org.jspecify.annotations.NullMarked`, so both are core dependencies of every
module. The `google.jsr305.version` property is renamed to `jsr305.version`.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
