chore(release): agent 0.1.56 — check-events v2 from CI (progress, fg-check on PATH, CTRF, forge ci checks) #430

Closed
gmackie wants to merge 1 commit from release/agent-0.1.56-main into main
Owner

The 0.1.56 bump recut on post-#427 main so the fleet binary includes the fg-check embed. Supersedes branch release/agent-0.1.56 (same bump, pre-#427 base). After merge: tag v0.1.56 → .github/workflows/release.yaml builds, signs (cosign keyless), publishes to npm.forgegraf.com, and sets the update policy.

🤖 Generated with Claude Code

The 0.1.56 bump recut on post-#427 main so the fleet binary includes the fg-check embed. Supersedes branch release/agent-0.1.56 (same bump, pre-#427 base). After merge: tag v0.1.56 → .github/workflows/release.yaml builds, signs (cosign keyless), publishes to npm.forgegraf.com, and sets the update policy. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
chore(release): agent 0.1.56 — check-events v2 progress and summaries from CI
All checks were successful
CI / gitleaks (pull_request) Successful in 6s
CI / storybook (pull_request) Successful in 1m25s
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 9m44s
912615f3e5
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Author
Owner

Heads-up from the other release track: 0.1.56 is already tagged and published — v0.1.56 on main f9fa8b37 (post-#423, pre-#427), packages are live on npm.forgegraf.com and the fleet policy points at 0.1.56 (hetzner-bob/master/worker already converged). npm will reject a second 0.1.56 and the tag already exists, so this recut needs to become 0.1.57. I'm cutting 0.1.57 on current main (which includes #427) and moving the agent release pipeline onto a Forgejo workflow per Graham's direction ("we use forgegraph/forgejo"), so this PR can be closed once that lands.

Heads-up from the other release track: **0.1.56 is already tagged and published** — `v0.1.56` on main `f9fa8b37` (post-#423, pre-#427), packages are live on npm.forgegraf.com and the fleet policy points at 0.1.56 (hetzner-bob/master/worker already converged). npm will reject a second 0.1.56 and the tag already exists, so this recut needs to become **0.1.57**. I'm cutting 0.1.57 on current main (which includes #427) and moving the agent release pipeline onto a Forgejo workflow per Graham's direction ("we use forgegraph/forgejo"), so this PR can be closed once that lands.
Author
Owner

Superseded by #434 (0.1.57 on current main + Forgejo release workflow). Closing.

Superseded by #434 (0.1.57 on current main + Forgejo release workflow). Closing.
gmackie closed this pull request 2026-08-25 02:48:06 +00:00
All checks were successful
CI / gitleaks (pull_request) Successful in 6s
Required
Details
CI / storybook (pull_request) Successful in 1m25s
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 9m44s
Required
Details

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gmackie/ForgeGraph!430
No description provided.