Skip to content

chore(master): release fleet-agent 0.1.7 - #727

Merged
AprilNEA merged 2 commits into
masterfrom
release-please--branches--master--components--fleet-agent
Oct 3, 2026
Merged

AprilNEA merged 2 commits into
masterfrom
release-please--branches--master--components--fleet-agent

Conversation

@arcbox-labs

@arcbox-labs arcbox-labs Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.7 (2026-10-03)

Features

  • fleet-agent: complete the host facts after the handshake instead of waiting for them (06775e1)

Bug Fixes

  • fleet-agent: probe host facts off the runtime and never let them hold an attach (963541a)

Tests

  • fleet: compare emptiness assertions against an empty value (b049d30)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Low risk] Version bump and changelog for a release.

The release metadata appears safe to merge.

Summary

This PR prepares the Fleet Agent 0.1.7 release by aligning its version metadata and adding the release notes.

  • The crate version, lockfile, and release manifest agree.
  • The changelog records the host-facts feature, fix, and test change.

Reviews (5) · Last reviewed commit: "chore: update lockfiles for release"

pullfrog[bot]
pullfrog Bot previously approved these changes Oct 2, 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 cutting fleet-agent 0.1.7: a mechanical, automation-generated release (2 commits, 4 files, no behavioral surface in the PR itself).

  • Version bump — fleet/arcbox-fleet-agent/Cargo.toml 0.1.6 → 0.1.7 on the annotated line, mirrored into Cargo.lock and the fleet key of .release-please-manifest.json.
  • Changelog — fleet/CHANGELOG.md gains the 0.1.7 entry attributing one commit, 963541a — fix(fleet-agent): probe host facts off the runtime and never let them hold an attach.
  • Lockfile sync — the chore: update lockfiles for release follow-up mirrors the bump into Cargo.lock; that is the established fleet pattern (release-please doesn't regenerate this component's lockfile) and it is load-bearing because release-fleet-agent.yml builds with --locked.

Checks performed:

  • Attribution: all six files of 963541a live under fleet/arcbox-fleet-agent/ — correct.
  • Tag prefix: compare links use fleet-agent-v*, matching the release-fleet-agent.yml trigger.
  • Consistency: manifest and Cargo.lock both say 0.1.7, so the --locked release build is coherent.

Pullfrog  | View workflow run | Using glm-5.3-flash | 𝕏

@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--fleet-agent branch 2 times, most recently from 81adf95 to a464c0c Compare October 2, 2026 13:27
@arcbox-labs
arcbox-labs Bot force-pushed the release-please--branches--master--components--fleet-agent branch from 11baf12 to 123d34c Compare October 3, 2026 16:37
@AprilNEA
AprilNEA merged commit 65594b3 into master Oct 3, 2026
18 checks passed
@AprilNEA
AprilNEA deleted the release-please--branches--master--components--fleet-agent branch October 3, 2026 19:32
@arcbox-labs

arcbox-labs Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

1 participant