chore(master): release fleet-agent 0.1.4

[arcbox-labs]

🤖 I have created a release beep boop

0.1.4 (2026-08-10)

Features

• fleet: add the restart CLI subcommand (bc71299)
• fleet: restart the agent process in place (c8649a5)

Bug Fixes

• fleet: compute the draining flag under the watch write lock (732b05a)
• fleet: derive the draining flag from one reason cell (4c1ef9e)
• fleet: keep a restart from swallowing a termination signal (32d8133)
• fleet: self-update on a version-refused control-plane enroll (#500) (01f4990)

Code Refactoring

• fleet: exec only from main (6ddb60f)
• fleet: give the handover one owner (f35f58e)
• fleet: one quiesce primitive for handover waits (50a5777)
• rpc,daemon,fleet: prost becomes test support only (CORE-73 follow-up) (#540) (3b24286)

---

This PR was generated with Release Please. See documentation.

[pullfrog]

✅ 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, and fleet/arcbox-fleet-agent/Cargo.toml (the x-release-please-version-tagged line) all move 0.1.3 → 0.1.4.
• fleet/CHANGELOG.md gains a 0.1.4 section referencing the sole change since 0.1.3 (#500, the version-refused control-plane enroll self-update fix, commit 01f4990), prepended above the existing 0.1.3 entry.

Generated by release-please; the version is coherent everywhere and the changelog matches the one commit landed since the previous release. Nothing to address.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

[greptile-apps]

Greptile Summary

Updates the Fleet Agent release metadata to version 0.1.4.

• Synchronizes the release manifest, crate manifest, and Cargo lockfile version.
• Adds the generated 0.1.4 release notes to the Fleet changelog.

Confidence Score: 5/5

The release metadata update appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Advances the Fleet release version from 0.1.3 to 0.1.4.
Cargo.lock	Synchronizes the locked arcbox-fleet-agent package version with the crate manifest.
fleet/CHANGELOG.md	Adds the generated Fleet Agent 0.1.4 feature, fix, and refactoring notes.
fleet/arcbox-fleet-agent/Cargo.toml	Advances the Fleet Agent crate version from 0.1.3 to 0.1.4.

_{Reviews (13): Last reviewed commit: "chore: update lockfiles for release" | Re-trigger Greptile}

[pullfrog]

✅ 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.md grew from one bullet to nine, adding ### Features and ### Code Refactoring sections: the restart CLI subcommand and in-place agent restart, three draining/SIGTERM fixes, and the handover/exec/quiesce refactors. The nine bullets match git log origin/master -- fleet/ over 01f4990..4c1ef9e one-for-one — nothing missing, nothing invented.
• Version bump stayed 0.1.3 → 0.1.4 across all four files despite the two new feat commits, which is correct: release-please-config.json sets bump-patch-for-minor-pre-major: true, so feat maps to a patch bump pre-1.0. None of the nine commits carries a ! or BREAKING CHANGE footer, so the bump-minor-pre-major: true path to 0.2.0 correctly did not fire.
• Cargo.lock carries only the arcbox-fleet-agent version line, with no dependency churn riding along, and the manifest's "." root entry stays at 0.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.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

[pullfrog]

Run failed. View the logs →

  ^{｜ Rerun failed job ➔ ｜ View workflow run ｜ via Pullfrog ｜ Using Claude Opus ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes — release-please regenerated this PR onto master tip 72f0e74 (root now 0.6.3). Against the previous branch head e46e672 the four-path delta is date-only, but against the last pullfrog review (1e12bac, when the section held nine bullets) the release content grew by one entry.

• fleet/CHANGELOG.md gained a tenth 0.1.4 bullet — 3b24286 (#540, refactor(rpc,daemon,fleet): prost becomes test support only). It belongs in the fleet component's notes: git show --stat 3b242865 confirms it really touches fleet/arcbox-fleet-agent/Cargo.toml, src/control/image.rs, and src/vm.rs (112 lines).
• Changelog header date refreshed 2026-08-03 → 2026-08-07; the other nine bullets are byte-identical.
• Version bump is unchanged and still correct — 0.1.3 → 0.1.4 in .release-please-manifest.json, Cargo.lock, and the x-release-please-version line of fleet/arcbox-fleet-agent/Cargo.toml. A refactor entry does not move the version, and the two feat commits still map to a patch bump under bump-patch-for-minor-pre-major: true.
• Cargo.lock still carries a single arcbox-fleet-agent hunk — the workspace-wide 0.6.1 → 0.6.3 block, the arcbox-boot 0.7.0 → 0.8.0 registry bump, and arcbox-migration picking up chrono are all base content, absent from the PR's own diff.

Completeness re-checked: git log --grep fleet -i origin/master returns only 3b242865 (recorded) and ecf11af4 docs(rpc) (does not touch fleet/). git log origin/master -- fleet/ also lists dbb24f27, but that is this run's shallow-checkout graft commit — its --stat covers the entire repo — not a real fleet change. Master's manifest still reads "fleet": "0.1.3", so the release is uncut, and rg '0\.1\.3' fleet/ turns up only historical changelog lines. Nothing to address.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

[pullfrog]

Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an ANTHROPIC_API_KEY repo secret — Pullfrog routes around an exhausted subscription automatically when one is present.

Add repo secret → · Model settings → · Setup docs → · Ask in Discord →

  ^{｜ Rerun failed job ➔ ｜ View workflow run ｜ via Pullfrog ｜ Using Claude Opus ｜ 𝕏}