chore(master): release 0.6.4

[arcbox-labs]

🤖 I have created a release beep boop

0.6.4 (2026-08-03)

Bug Fixes

• release: resume partial crates.io publishes (#548) (34a5e64)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This release PR consistently advances Arcbox from 0.6.3 to 0.6.4.

• Updates the release manifest and changelog.
• Bumps the workspace version and internal dependency pins.
• Regenerates Cargo.lock with matching workspace package versions.

Confidence Score: 5/5

The PR appears safe to merge because its release metadata, workspace dependency pins, and lockfile versions are consistent.

The changes are limited to a coherent 0.6.4 release bump and changelog update, with intentional independently versioned crates left unchanged and no external dependency versions altered.

Important Files Changed

Filename	Overview
Cargo.toml	Consistently bumps the workspace version and release-managed internal dependency requirements to 0.6.4 while preserving intentional independent-version exceptions.
Cargo.lock	Updates workspace package versions to 0.6.4 without changing external dependency resolution.
.release-please-manifest.json	Advances the root release version to 0.6.4 while leaving the independently managed fleet version unchanged.
CHANGELOG.md	Adds the 0.6.4 release entry describing the crates.io publishing fix.

_{Reviews (1): Last reviewed commit: "chore: update Cargo.lock for release" | Re-trigger Greptile}

[pullfrog]

✅ No new issues found.

Reviewed changes — the full release-please diff at 4b1bef1, covering both the generated release commit and the follow-up Cargo.lock regeneration.

• Manifest bump — .release-please-manifest.json moves the root "." component 0.6.3 → 0.6.4; the "fleet" component correctly stays at 0.1.3 (separate release train via exclude-paths: ["fleet"]).
• Changelog — one ## [0.6.4] section with a single ### Bug Fixes entry for #548. This matches git log v0.6.3..master exactly, which contains only 34a5e641 — no entries dropped.
• Cargo.toml — workspace.package.version plus every dep pin carrying # x-release-please-version. The three manually-cadenced pins are correctly left alone: arcbox-hv = 0.3.20, arcbox-helper = 1.0.2, arcbox-boot = 0.8.0.
• Cargo.lock — all workspace member versions bumped by the Update Cargo.lock on release PRs step. cargo metadata --locked --no-deps exits 0, so the tagged commit will satisfy the cargo publish --workspace --no-verify --locked in release.yml.

A repo-wide grep for 0.6.3 finds no stale references outside CHANGELOG.md history and an unrelated third-party objc2 0.6.3 line in NOTICE.md.

ℹ️ This tag is the first to run the new crates.io publish-resume logic

The only commit in 0.6.4 is #548, which added the crate <name>@<ver> already exists on crates.io index → add-to-excludes → retry loop to release.yml's publish-crates job. Nothing in this diff can change that, but on a clean 0.6.4 no crate is pre-published, so the resume branch only engages if the publish partially fails mid-run — worth watching the publish job once this merges rather than assuming the fix is proven.

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