The GitHub Actions job "Build" on rocketmq-clients.git/ci/rust-relax-blocking-checks has succeeded. Run started by GitHub user lizhimins (triggered by lizhimins).
Head commit for run: 750b021f9a0d9391f0b5eb5d189f3d59d78603f3 / lizhimins <[email protected]> [ISSUE #1412] [CI] Stop gating build-result on the Rust build `build-result` is the required status check on master, and it aggregates `rust-build`. That gates every Rust PR on a Rust baseline which is currently red for reasons unrelated to any open change: - rust/Cargo.lock is gitignored, so each run resolves dependencies from scratch and now pulls hyper-util >= 0.1.16 (edition 2024, needs rustc >= 1.85) and powerfmt >= 0.2.1 (needs rustc >= 1.79). Both break the 1.74 toolchain that the `msrv` and `build` jobs install. - Stable clippy fails on two pre-existing `for_kv_map` warnings in rust/src/client.rs (lines 904 and 912), which `-D warnings` turns into errors. Since `build` declares `needs: [fmt, msrv]`, an msrv failure skips the whole Ubuntu/macOS/Windows matrix, and `build-result` then blocks every Rust PR whose head does not carry the dependency pins. Drop `rust-build` from `needs` and from the aggregation script. `rust_build.yml` is untouched: every Rust job still runs and still reports its true result, so the signal stays visible on the PR -- it just no longer gates the merge. Reviewers of Rust changes need to read `rust-build / *` directly until this is reverted. Restore `rust-build` here once the dependency pins (powerfmt < 0.2.1, hyper-util < 0.1.16, tokio < 1.47) and the `for_kv_map` fix land on master. #1404 contains both and is green. Report URL: https://github.com/apache/rocketmq-clients/actions/runs/39799023486 With regards, GitHub Actions via GitBox
