Skip to content

chore(master): release fleet-agent 0.1.4 - #501

Open
arcbox-labs[bot] wants to merge 2 commits into
masterfrom
release-please--branches--master--components--fleet-agent
Open

chore(master): release fleet-agent 0.1.4#501
arcbox-labs[bot] wants to merge 2 commits into
masterfrom
release-please--branches--master--components--fleet-agent

Conversation

@arcbox-labs

@arcbox-labs arcbox-labs Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.4 (2026-08-03)

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 pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes — an automated release-please PR cutting arcbox-fleet-agent 0.1.30.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.30.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.

Pullfrog  | Fix it ➔View workflow run | Using Claude Opus𝕏

@greptile-apps

greptile-apps Bot commented Jul 27, 2026

Copy link
Copy Markdown

Greptile Summary

Updates the fleet agent release metadata to version 0.1.4.

  • Synchronizes the release manifest, crate metadata, and lockfile version.
  • Adds the generated 0.1.4 fleet-agent changelog.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

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

@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--fleet-agent branch from b0a5d4f to aad5b07 Compare July 30, 2026 13:31
@pullfrog pullfrog Bot mentioned this pull request Jul 30, 2026
@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--fleet-agent branch 2 times, most recently from e2de00e to 9f66158 Compare July 31, 2026 13:12
pullfrog[bot]
pullfrog Bot previously approved these changes Jul 31, 2026

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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.30.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.

Pullfrog  | View workflow run | Using Claude Opus𝕏

@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--fleet-agent branch 3 times, most recently from 0777c09 to 66d3414 Compare August 3, 2026 06:46
@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--fleet-agent branch from d20b175 to 8851c8b Compare August 3, 2026 10:40
@pullfrog

pullfrog Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Run failed. View the logs →

Pullfrog  | Rerun failed job ➔View workflow run | via Pullfrog | Using Claude Opus𝕏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants