chore(cargo-each): release v0.4.0

[martin-kolinek]

🤖 Prepares cargo-each 0.4.0 for publication from the changes merged since cargo-each-v0.3.0.

Included changes

• optional {workspace-rust-version} resolution with strict validation for declared workspace floors
• JSON Lines record execution with {json:key} substitution
• bounded, ordered record scheduling with pre-spawn validation and streaming file input
• scheduler and process-boundary failure hardening from feat(cargo-gamma): improve campaign scheduling and UX #208
• deterministic parallel-output test coverage and internal failure-plumbing cleanup from fix: address cargo-gamma audit feedback #221
• simplified timeout cleanup from fix(cargo-each): simplify timeout cleanup #222

Release artifacts

• bumps crates/cargo-each/Cargo.toml to 0.4.0
• refreshes the workspace Cargo.lock
• generates the 0.4.0 changelog section with scripts/release-crate.ps1

The cargo-anvil tool pin remains at the currently published cargo-each version; adopting 0.4.0 belongs in the follow-up Anvil integration after this release is available on crates.io.

Validation

• cargo test --package cargo-each --all-features
• cargo clippy --package cargo-each --all-targets --all-features --locked -- -D warnings
• cargo publish --dry-run --package cargo-each --locked --allow-dirty
• ANVIL_IMPACT=off just anvil-pr-fast

[Copilot]

Copilot review overview

🟡 Changes recommended

The generated changelog advertises unrelated cargo-gamma functionality and omits clear cargo-each-specific release details.

Review effort: Balanced
Findings: 1

Open (1)

• Filter release notes to cargo-each changes · New

What changed in this PR

Prepares cargo-each 0.4.0 for publication.

Changes:

• Bumps the crate version to 0.4.0.
• Synchronizes the lockfile.
• Generates release notes, though some entries describe unrelated or unclear changes.

File	Description
crates/​cargo-each/​CHANGELOG.md	Adds the 0.4.0 release section.
crates/​cargo-each/​Cargo.toml	Bumps the package version.
Cargo.lock	Updates the resolved workspace package version.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Codecov Comments Bot (codecov-commenter)]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.3%. Comparing base (57679fa) to head (68822e3).
⚠️ Report is 1 commits behind head on main.

❌ Your project status has failed because the head coverage (99.3%) is below the target coverage (100.0%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #230   +/-   ##
=====================================
  Coverage   99.3%   99.3%           
=====================================
  Files        317     317           
  Lines      69150   69150           
=====================================
  Hits       68694   68694           
  Misses       456     456           

Flag	Coverage Δ
linux	99.3% <ø> (ø)
linux-arm	99.3% <ø> (ø)
scheduled	?
windows	99.2% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[martintmk]

Posted by an AI agent

Fast-path approval withheld at checked head 799fd45deaf03d26cdbf1fea3ba39ff6053396c1: the cargo-each 0.4.0 notes describe #208's cargo-gamma campaign scheduling/UX as a cargo-each feature (review finding). Please correct/verify crate-specific release notes and obtain human review before publishing.

[martintmk]

Posted by an AI agent

Review preparation has started for #230 at pinned head 68822e32db30a2e14b34d2dd17c7ff546b9c0d5e, targeting microsoft/ox-tools:main.

The submitted review will contain the result.

[martintmk]

Posted by an AI agent

Verdict: Changes requested

I reviewed behavior, public contract, tests, naming, and code/documentation consistency. Performance, telemetry, and recovery behavior were not applicable; cargo-each has no library public API to audit.

The existing release-notes finding remains unresolved: the cargo-each 0.4.0 notes include unrelated cargo-gamma changes. Please correct the crate-specific release notes. I found no additional issues and have not repeated the inline comment.

The required Anvil, tests/coverage, MSRV, mutation, runtime, CodeQL, and regeneration checks passed. I did not run local tests or benchmarks.

[Copilot]

Copilot review overview

🟢 Approval recommended

The release metadata is complete, internally consistent, and matches the documented release scope.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Filter release notes to cargo-each changes

[martintmk]

Posted by an AI agent

Verdict: Changes requested

I reviewed the 0.4.0 release metadata, behavior, public contract, tests, naming, and code/documentation consistency. Performance, telemetry, and recovery were not applicable; the binary-only crate has no library public API to audit.

One new release-note claim needs correction below. The prior #208 release-note issue was corrected, and its thread is resolved.

I did not run local tests or benchmarks under this review's limits. At revalidation, CI fast checks, Linux tests/MSRV/mutation, CodeQL, and regeneration had passed; some runtime and Windows tests were still in progress.

[Copilot]

Copilot review overview

🟢 Approval recommended

The release artifacts are complete, consistent, and match the documented release process.

Review effort: Balanced
Findings: None

[martintmk]

Posted by an AI agent

Verdict: Approve with one non-blocking release-note clarification. I reviewed the 0.4.0 version and changelog changes for public contract, correctness, tests, naming, and documentation. The earlier #221 concern is resolved. There is no public library API (this crate is executable-only); performance, telemetry, and resilience do not apply to this change. I did not run local Rust tests, builds, benchmarks, or API generation. As of 09:32 UTC, Linux tests/MSRV, fast and mutation checks, CodeQL, and regeneration had passed, but runtime and Windows checks were still in progress.