The GitHub Actions job "Build and Run Tests by Bazel" on rocketmq.git/develop has succeeded. Run started by GitHub user lizhimins (triggered by lizhimins).
Head commit for run: 6a9e84f1132df46f56168b1f40e009e38383e39a / rongtong <[email protected]> [ISSUE #10651] bump DLedger to 0.3.3.4 (maintenance line) (#10958) * chore: bump DLedger to 0.3.3.4 (maintenance line) Update the DLedger dependency from 0.3.2 to 0.3.3.4, the latest release on the 0.3.x maintenance line published on Maven Central. The 0.3.3.4 release is API-compatible with 0.3.2 and only carries dependency hygiene fixes (aligning fastjson2 and excluding fastjson1 from its rocketmq-remoting transitive path). Also update the Bazel WORKSPACE artifact coordinate to keep the two build systems in sync. * chore: fully remove fastjson1 from the build DLedger 0.3.3.4 already excludes com.alibaba:fastjson from its rocketmq-remoting dependency and its bytecode only references fastjson2, but rocketmq still declared fastjson1 itself, so it kept leaking onto every module compile classpath through rocketmq-common. - drop the com.alibaba:fastjson property and dependencyManagement entry from the root pom - drop the unused com.alibaba:fastjson dependency from rocketmq-common (no main source imports com.alibaba.fastjson.*) - drop the fastjson1 pin from WORKSPACE and the fastjson1 dep from the remoting test target in remoting/BUILD.bazel - migrate RemotingSerializableCompatTest to fastjson2: use the fastjson2 JSONField annotation (which is what the protocol classes actually carry) and round trip through RemotingSerializable instead of com.alibaba.fastjson.JSON fastjson1 wire-format coverage is retained by the frozen fastjson1 payload already asserted in testCompatibilityCheckWithBitSet. * fix(bazel): exclude rocketmq-remoting from coursier resolution dledger 0.3.3.4 depends on rocketmq-remoting:5.5.0, which Coursier fetches from Maven Central. That artifact transitively brings grpc-netty-shaded:1.53.0 with a strict [1.53.0] range on grpc-core, conflicting with the WORKSPACE-declared grpc 1.47.0 artifacts. Since rocketmq-remoting is built from source in this repo (//remoting), exclude it from external resolution — matching what PR #10947 already does for the DLedger 0.4.x line. --------- Co-authored-by: 通融 <[email protected]> Report URL: https://github.com/apache/rocketmq/actions/runs/32225696301 With regards, GitHub Actions via GitBox
