FrankChen021 commented on PR #20281: URL: https://github.com/apache/druid/pull/20281#issuecomment-5582977885
Compatibility review for exact head `de89cdf56d28135b15f68c7ac8bf7d6169d2df97` against base `9b90983fd291f26935af934383ce360473179e4d`. Release inventory and transition: - Maven Central metadata publishes `2.75.0` and `2.76.0` as the only stable releases in the requested interval; there are no intermediate releases. The single reviewed transition is `2.75.0 -> 2.76.0`. - The PR changes only the test-scoped version in `indexing-service/pom.xml`. - Published artifact comparison: the 2.75.0 and 2.76.0 POMs differ only in their version; both retain Apache-2.0 licensing and the same `protobuf-java:4.33.6` dependency. The source JARs contain the same 462 files and identical source content outside Maven metadata, and the binary class content is identical outside META-INF metadata. - Druid effective dependency resolution keeps `protobuf-java:4.36.1` through the root dependency management. The production `druid-google-extensions` graph remains on `proto-google-common-protos:2.75.0`; this PR is test scope only. Compatibility result: API/ABI SAFE; runtime SAFE; configuration SAFE; serialization/wire SAFE; persistence SAFE; clients SAFE; transitive dependencies SAFE; licenses SAFE; extension/plugin SPI SAFE. No Druid production/test call-site or SPI change is required. CI result for this exact head: the complete GraphQL statusCheckRollup is terminal SUCCESS with 29/29 CheckRuns completed SUCCESS and no StatusContexts. Historical attempt 1 had one flaky test failure, `TaskQueueScaleTest` (`expected 1000 but was 986`) in job 101894303636; coverage and docker jobs were skipped after that failure. The eligible rerun completed successfully as job 101972311096 on attempt 2. No current failed or non-success job remains, and no additional rerun or source fix is justified. -- 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]
