FrankChen021 commented on PR #20137: URL: https://github.com/apache/druid/pull/20137#issuecomment-5404596363
Codex dependency triage at exact head b2db7ce302bfc41294e30e9adb315cacfa572fd0, compared with upstream master 20d733e735b7b4691624b93e4efba760ac6525ee: - The maven-resolver-connector-basic 1.3.1 -> 2.0.22 bump leaves Resolver API/SPI/util/transport modules at 1.3.1 while connector transitive dependencies require 2.0.22. - All five terminal failed checks are PR-caused deterministic RequireUpperBoundDeps failures in packaging, validate-dist, strict-compilation, static-checks-maven, and openrewrite. - Druid directly constructs Resolver services and legacy sessions in PullDependencies. Resolver's 1.x-to-2.x migration requires coordinated companion-version, provider, and session-lifecycle work; dependency pulling, packaging, and extension resolution are unsafe as submitted. - No Druid data, wire, configuration API, or stored-data change was found, but the required migration is broader and riskier than a two-line dependency bump. Closing this PR as high effort / not safe to approve. No merge was performed. -- 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]
