chore(master): release 0.5.4

[arcbox-labs]

🤖 I have created a release beep boop

0.5.4 (2026-07-30)

Bug Fixes

• core: disable the idle balloon — no macOS backend reclaims ballooned memory (#504) (6cb174a)

Tests

• e2e: VirtioFS guest-vs-native benchmark driver (#507) (4e5f676)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Updates the workspace release metadata to version 0.5.4.

• Bumps workspace crates and internal dependency constraints from 0.5.3 to 0.5.4.
• Regenerates the lockfile with matching workspace package versions.
• Adds the 0.5.4 release notes and updates the Release Please manifest.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
Cargo.toml	Consistently bumps the workspace package version and release-managed internal dependency constraints to 0.5.4.
Cargo.lock	Updates workspace package versions to 0.5.4 without changing resolved third-party dependencies.
.release-please-manifest.json	Advances the root package release version from 0.5.3 to 0.5.4.
CHANGELOG.md	Adds the generated 0.5.4 release entry covering the included fix and test change.

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

[pullfrog]

✅ No new issues found.

Reviewed changes — the automated release-please bump for the root component, plus the bot's follow-up Cargo.lock regeneration commit. Purely mechanical; no source changes.

• .release-please-manifest.json — root component 0.5.3 → 0.5.4; "fleet" correctly left at 0.1.3, since it is a separate release-please component.
• CHANGELOG.md — new 0.5.4 section with a single Bug Fixes entry for #504 (fix(core): disable the idle balloon).
• Cargo.toml — workspace.package.version plus every internal dep pin carrying # x-release-please-version.
• Cargo.lock — 51 workspace-member version entries bumped. Exactly 51 removed and 51 added lines, all of them version = "0.5.…" — no third-party dependency movement, consistent with release-please.yml:57 using cargo update --workspace.

What I checked and confirmed:

• cargo metadata --locked passes, so the v0.5.4 tag can build with --locked — which is the stated purpose of the bot's lock-regen commit.
• No stale 0.5.3 references repo-wide. The one remaining Cargo.lock hit is the unrelated third-party tower 0.5.3.
• Independently-versioned crates correctly untouched: arcbox-hv 0.3.20 (its workspace pin deliberately carries no annotation), arcbox-helper 1.0.2, arcbox-fleet-agent 0.1.3.
• Changelog completeness. Two commits landed since the 0.5.3 release commit. 6cb174a (#504) is captured here; 01f4990d (#500, fix(fleet)) touches only fleet/arcbox-fleet-agent and is correctly excluded by the root package's "exclude-paths": ["fleet"], landing instead in the companion PR #501 (release fleet-agent 0.1.4). Nothing is dropped between the two changelogs.

ℹ️ What 0.5.4 ships behaviorally

The sole functional change in this release is #504, which disables the idle balloon because no macOS backend actually reclaims ballooned memory. Host phys_footprint now stays at the configured memory_mb for the VM's whole lifetime rather than appearing to shrink when idle. That is a user-visible memory-behavior change, and the changelog line describes it accurately — flagging it only so release notes and any published idle-memory claims are read with that in mind. No action needed on this PR.

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

[pullfrog]

✅ No new issues found.

Reviewed changes — release-please force-pushed this branch onto the new master head (4e5f676), which regenerated the changelog and re-applied the bot's Cargo.lock bump. The prior pullfrog review at 87d34bf was dismissed by that force-push; this run re-verifies the whole PR against 18bca974.

• CHANGELOG.md — the 0.5.4 section gained a ### Tests entry for #507 (test(e2e): VirtioFS guest-vs-native benchmark driver) alongside the existing Bug Fixes entry for #504. test is a configured changelog section in release-please-config.json, and it does not itself drive the bump — the fix does, so 0.5.3 → 0.5.4 is still the right patch increment.
• Cargo.lock — regenerated on the new base. Still exactly 51 removed and 51 added lines, every one a version = "0.5.…" on a workspace member; no third-party dependency moved.
• .release-please-manifest.json / Cargo.toml — unchanged from the previously reviewed round: root component 0.5.3 → 0.5.4, "fleet" left at 0.1.3, workspace.package.version plus every internal pin carrying # x-release-please-version.

What I re-checked and confirmed at 18bca974:

• cargo metadata --locked passes, so the v0.5.4 tag can build with --locked — the stated purpose of the bot's lock-regen commit.
• No workspace member was skipped. cargo metadata reports 54 members; 3 are independently versioned (arcbox-hv 0.3.20, arcbox-helper 1.0.2, arcbox-fleet-agent 0.1.3), leaving 51 at 0.5.4 — matching the 51 changed lock lines exactly.
• No stale 0.5.3 references repo-wide. The single remaining Cargo.lock hit is third-party tower 0.5.3.
• No new crate needs annotating. 4e5f676 touches only tests/bench-virtiofs/** and tests/e2e/tests/, with no Cargo.toml anywhere, so it introduces no workspace member that would need a # x-release-please-version pin.
• Changelog attribution is complete. 01f4990d (#500, fix(fleet)) is still correctly excluded by the root package's "exclude-paths": ["fleet"] and routed to the companion PR #501. Nothing is dropped between the two changelogs.

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

[arcbox-labs]

🤖 Created releases:

• v0.5.4

🌻