chore(master): release fleet-agent 0.1.4 - #501
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — an automated release-please PR cutting arcbox-fleet-agent 0.1.3 → 0.1.4.
- Version bump is consistent across all four files —
.release-please-manifest.json,Cargo.lock, andfleet/arcbox-fleet-agent/Cargo.toml(thex-release-please-version-tagged line) all move0.1.3→0.1.4. fleet/CHANGELOG.mdgains a0.1.4section referencing the sole change since0.1.3(#500, the version-refused control-plane enroll self-update fix, commit01f4990), prepended above the existing0.1.3entry.
Generated by release-please; the version is coherent everywhere and the changelog matches the one commit landed since the previous release. Nothing to address.
Claude Opus | 𝕏
Greptile SummaryUpdates the fleet agent release metadata to version 0.1.4.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| .release-please-manifest.json | Advances the fleet release manifest from 0.1.3 to 0.1.4. |
| Cargo.lock | Synchronizes the arcbox-fleet-agent package version with the release. |
| fleet/CHANGELOG.md | Adds the generated release notes and comparison link for fleet-agent 0.1.4. |
| fleet/arcbox-fleet-agent/Cargo.toml | Advances the fleet-agent crate version to 0.1.4. |
Reviews (9): Last reviewed commit: "chore: update Cargo.lock for release" | Re-trigger Greptile
b0a5d4f to
aad5b07
Compare
e2de00e to
9f66158
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — release-please regenerated this PR onto master tip 4c1ef9e. Since the prior pullfrog review (b0a5d4f, when the 0.1.4 section held a single bullet) eight fleet-scoped commits landed on master, so this is the first substantive delta on the branch rather than another date-only refresh.
fleet/CHANGELOG.mdgrew from one bullet to nine, adding### Featuresand### Code Refactoringsections: the restart CLI subcommand and in-place agent restart, three draining/SIGTERM fixes, and the handover/exec/quiesce refactors. The nine bullets matchgit log origin/master -- fleet/over01f4990..4c1ef9eone-for-one — nothing missing, nothing invented.- Version bump stayed
0.1.3→0.1.4across all four files despite the two newfeatcommits, which is correct:release-please-config.jsonsetsbump-patch-for-minor-pre-major: true, sofeatmaps to a patch bump pre-1.0. None of the nine commits carries a!orBREAKING CHANGEfooter, so thebump-minor-pre-major: truepath to0.2.0correctly did not fire. Cargo.lockcarries only thearcbox-fleet-agentversion line, with no dependency churn riding along, and the manifest's"."root entry stays at0.5.4.
Also checked: no other file pins the fleet-agent version (0.1.3 appears elsewhere only in unrelated third-party entries and historical changelog lines), and the resulting fleet-agent-v0.1.4 tag matches the fleet-agent-v* trigger in .github/workflows/release-fleet-agent.yml. Substantively this release ships the fleet agent's handover/drain/re-exec rewrite, all of which was reviewed on master in its own PRs; this PR itself contains no code. Nothing to address.
Claude Opus | 𝕏
0777c09 to
66d3414
Compare
d20b175 to
8851c8b
Compare
|
Run failed. View the logs →
|

🤖 I have created a release beep boop
0.1.4 (2026-08-03)
Features
Bug Fixes
Code Refactoring
This PR was generated with Release Please. See documentation.