loadingalias opened a new pull request, #3999: URL: https://github.com/apache/iggy/pull/3999
## Which issue does this PR address? Closes #(N/A) ## Rationale I am the maintainer of Cargo-Rail. I simply wanted to alleviate the extra work for the Iggy team across the latest (v0.25.0 release). Iggy's pre-merge workflow consumes a retired Cargo-Rail plan format, while post-merge image selection maintains a separate affected-change policy. These paths can drift from Cargo-Rail's dep graph and from each other. Planning remains an optimization; invalid/unavailable plans must preserve Iggy's existing workspace wide and all-image behavior. ## What Changed? Pre-merge and post-merge planning now use `cargo-rail-action` v8.2.0, pinned by commit, w/ its validated v8 plan reader. Test selection uses typed Cargo arguments, and integration tests include their exact runtime bin and connector-lib prereq's. Edge-image selection now comes from a five-variant Cargo-Rail catalog instead of separate shell and publish-config gates. Action, checkout, plan, reader, and matrix failures fall back to full workspace testing or building all five images. ## Local Execution - Passed - Pre-commit hooks not run; the applicable checks were run directly Validation performed locally: - Cargo-Rail v0.25.0 plan and checkout validation - scoped, workspace, skipped, planner-failure, reader-failure, selected-image, and all-image paths - `cargo fmt --all -- --check` - `cargo clippy --all-targets --all-features -- -D warnings` - `cargo check --all --all-features` - `cargo build --locked` - `cargo test --locked --no-run` - doctests and docs - repo Taplo, ShellCheck, YAML, JSON, & Actionlint The full external-service integration suite was NOT completed locally. Its Docker-backed connector fixtures require services and resources beyond this workflow-planning change; all Rust test targets compiled successfully. ## AI Usage 1. **Tool:** Codex 2. **Scope:** Analysis of the workflows within Iggy that were touched, fallback integration/testing, and some validation. 3. **Verification:** I reviewed everything I felt necessary. The applicable Rust, workflow, config, and repo checks listed above passed locally. 4. **Can you explain every line if asked?** Yes. I am the maintainer of Cargo-Rail. -- 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]
