[arcbox-labs]

🤖 I have created a release beep boop

0.2.0 (2026-11-01)

⚠ BREAKING CHANGES

• runner: rename Fleet to ArcBox Runners

Bug Fixes

• runner-agent: reach ArcBox's Docker socket through HostLayout (76c464e)

Code Refactoring

• runner: rename Fleet to ArcBox Runners (1c544b7)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Confidence Score: 5/5

[Low impact] The release appears safe to merge; the two previous changelog issues remain non-blocking.

Findings

1.  Release comparison uses wrong tag ▶
2.  Upgrade steps are missing ▶

Summary

Prepares the independent runner-agent release for 0.2.0.

• Runner release records now identify version 0.2.0.

_{Reviews (7) · Last reviewed commit: "chore: update lockfiles for release" · Reviewed by Greptile}

[greptile-apps]

Release comparison uses wrong tag

The comparison starts at runner-agent-v0.1.7, but the previous release used fleet-agent-v0.1.7. Readers cannot follow this link to inspect the changes across the rename. Use fleet-agent-v0.1.7...runner-agent-v0.2.0 instead.

Suggested change

	## [0.2.0](https://github.com/arcboxlabs/arcbox/compare/runner-agent-v0.1.7...runner-agent-v0.2.0) (2026-10-25)
	## [0.2.0](https://github.com/arcboxlabs/arcbox/compare/fleet-agent-v0.1.7...runner-agent-v0.2.0) (2026-10-25)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Upgrade steps are missing

The breaking-change note describes only a rename. The linked rename commit also says enrolled hosts must re-enroll, state moves to ~/.arcbox/runner, and environment variables change to ARCBOX_RUNNER_*. Include those upgrade steps here so operators do not mistake this for a name-only change.

[pullfrog]

ℹ️ No critical issues — one minor suggestion inline.

Reviewed changes — generated release-please PR cutting runner-agent 0.2.0 from current master:

• Version bumps — .release-please-manifest.json (runner 0.1.7 → 0.2.0), the annotated version line in runner/arcbox-runner-agent/Cargo.toml, and the arcbox-runner-agent block in Cargo.lock.
• Changelog entry — new runner/CHANGELOG.md 0.2.0 entry. Attribution verified: both listed commits touch runner/, while the same-day fleet/ restore, ADR, and docs commits don't and are correctly absent. Bump semantics check out: the refactor(runner)! breaking change minors 0.1.7 → 0.2.0 under bump-minor-pre-major. The release commit's parent is master HEAD (18fb66c9), so the range is current, and the runner-agent-v* tag prefix matches release-runner-agent.yml's trigger.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using glm-5.3-flash ｜ 𝕏}

[pullfrog]

The compare link's from-side tag doesn't exist: 0.1.7 was tagged fleet-agent-v0.1.7 before the component rename, and no runner-agent-v* tag exists yet. Once runner-agent-v0.2.0 is pushed, this link — and the GitHub release body generated from it — will 404.

Technical details

# Dead compare link after the fleet-agent → runner-agent rename

## Affected sites
- runner/CHANGELOG.md:3 — compare link `runner-agent-v0.1.7...runner-agent-v0.2.0`; the from-side tag was never created
- The GitHub release body for `runner-agent-v0.2.0` (generated from this entry once merged) — same dead link

## Required outcome
- Decide whether the 404 matters: it's cosmetic (the breaking-change note already tells 0.1.7 hosts to re-enroll), or make `runner-agent-v0.1.7` resolve before merging.

## Suggested approach (optional)
- release-please derives the previous tag from the current component prefix plus the prior manifest version, so the rename orphaned the old prefix: the real 0.1.7 tag is `fleet-agent-v0.1.7` (65594b3f14c6643fc6c79e78ecf4f48bfad18d64). Pushing `runner-agent-v0.1.7` as an alias tag on that commit before merging makes the link resolve — but note `release-runner-agent.yml` triggers on `runner-agent-v*` pushes, so the alias also kicks off a 0.1.7 build/publish under the new naming. That may be desirable (keeps the version resolvable under the new prefix) or unwanted (a spurious release run); if unwanted, skip the alias. `runner/CHANGELOG.md` is release-please generated — don't hand-edit the link.