chore: release - #5598
chore: release#5598ironclaw-ci[bot] wants to merge 1 commit into
Conversation
Coverage ratchetReborn integration-tier coverageLine coverage (Reborn crates): 86.17% — 328145 / 380805 lines Per-crate breakdown (64 crates, lowest-covered first)
This table itself is informational and never gates the PR on its own — not the percentage, not the per-crate holes, not the 0-coverage callout. A separate coverage ratchet (dry-run until enforce=true; see tests/integration/coverage-floor.toml) can fail the build on specific configured floors. Exemptions (18 entry/entries excluded from the accounting above)
|
3d7b5c5 to
94a5950
Compare
🔎 IronLoop Review StatusHead: Current reviewers:
Reviewer summaries
Recent activity
Available commands
Run metadataAdmission: webhook accepted the request and IronLoop persisted reviewer state before this projection. |
08efa4e to
f0f12b9
Compare
8947962 to
41fc1ea
Compare
There was a problem hiding this comment.
✅ IronLoop Review: reviewer
Review at a glance
| Verdict | Blocking | Notes | Inline | Head |
|---|---|---|---|---|
| ✅ Approved | 0 | 1 | 1 | b87d4523d9da |
Head: b87d4523d9da5e059404c8c34495972ac66b8297
Next: No reviewer action needed.
Run details
Status: Current
Needs human: no
Needs validation: no
Summary
The release versions, workspace dependency constraints, changelogs, and primary lockfile are consistent. One non-blocking reproducibility issue remains in the standalone latency harness lockfile.
Findings
Blocking: 0 / Notes: 1
Non-blocking notes (1)
1. 💬 [LOW] Regenerate the standalone latency harness lockfile
Location: Cargo.lock:4150
The release bumps ironclaw_common, ironclaw_safety, and ironclaw_skills, but harness/latency/runner/Cargo.lock still records versions 0.4.2, 0.2.2, and 0.3.0 respectively. Because that harness is a separate workspace using these path dependencies transitively, its first normal run will rewrite a tracked lockfile and any --locked invocation will fail before building. Regenerate the harness lockfile alongside these version changes.
Developer follow-up
After fixing this feedback:
- Push the fix to this PR branch.
- Re-run this reviewer with
@ironloopai review --agent reviewerif you only changed this reviewer's findings. - Re-run all reviewers with
@ironloopai reviewwhen the fix may affect multiple areas.
| [[package]] | ||
| name = "ironclaw_common" | ||
| version = "0.4.2" | ||
| version = "0.5.0" |
There was a problem hiding this comment.
The standalone harness/latency/runner/Cargo.lock still records ironclaw_common 0.4.2, ironclaw_safety 0.2.2, and ironclaw_skills 0.3.0. Since that separate workspace reaches these path packages transitively, normal runs will rewrite its tracked lockfile and --locked runs will fail. Please regenerate that lockfile with these release bumps.
🤖 New release
ironclaw_common: 0.4.2 -> 0.5.0 (⚠ API breaking changes)ironclaw_safety: 0.2.2 -> 0.2.3 (✓ API compatible changes)ironclaw_skills: 0.3.0 -> 0.4.0 (⚠ API breaking changes)⚠
ironclaw_commonbreaking changes⚠
ironclaw_skillsbreaking changesChangelog
ironclaw_commonironclaw_safetyironclaw_skillsThis PR was generated with release-plz.