chore(release): agent 0.1.66 — root deployed nix store paths; full CI queue reporting #577

Merged

gmackie merged 1 commit from release/agent-0.1.66 into main

2026-09-14 16:06:38 +00:00

gmackie commented

2026-09-14 15:54:25 +00:00

Owner

Release PR for agent 0.1.66. It follows the same shape as 0.1.64 (#517): the four npm/agent* version bumps, with the wrapper's optionalDependencies repinned, plus a CHANGELOG.md section.

What ships

Only two changes since 0.1.65 touch the agent binary (agent/cmd/agent, agent/internal). Neither has ever been released.

PR	change
#565	Deployed nix store paths become GC roots: `forgegraph-<service>-live`, plus `-previous` for rollback, swapped atomically. The hourly store prune deleted the live registry's binary on 2026-09-09 and again on 2026-09-13.
#556	The CI runner reports the full Forgejo job queue straight from the job table (up to 500 jobs, separate waiting/running totals), busy/idle/offline runner state, and each node's runner slot config in the heartbeat.

The other commits since 0.1.65 are CLI-only (fg contract publish #569, log help text). They ship through release-cli.yml, not this release.

After merge

Dispatch .forgejo/workflows/release-agent.yml with version: 0.1.66. It checks these manifests, builds the linux-x64, linux-arm64 and darwin-arm64 binaries, publishes to npm.forgegraf.com, points the fleet update policy at 0.1.66 with per-architecture checksums, and tags v0.1.66. Like 0.1.65, it's unsigned: Forgejo runners have no OIDC identity for keyless cosign, and the agent checks the npm checksum.

Every auto-updating node takes it on its next poll and restarts its agent. hetzner-fg is no longer self-update-pinned, so it will update too.

Independently of this release, #565's prune-script half is already installed by hand on all five nix nodes.

🤖 Generated with Claude Code

Release PR for agent **0.1.66**. It follows the same shape as 0.1.64 (#517): the four `npm/agent*` version bumps, with the wrapper's `optionalDependencies` repinned, plus a `CHANGELOG.md` section. ## What ships Only two changes since 0.1.65 touch the agent binary (`agent/cmd/agent`, `agent/internal`). Neither has ever been released. | PR | change | |---|---| | #565 | Deployed nix store paths become GC roots: `forgegraph-<service>-live`, plus `-previous` for rollback, swapped atomically. The hourly store prune deleted the live registry's binary on 2026-09-09 and again on 2026-09-13. | | #556 | The CI runner reports the full Forgejo job queue straight from the job table (up to 500 jobs, separate waiting/running totals), busy/idle/offline runner state, and each node's runner slot config in the heartbeat. | The other commits since 0.1.65 are CLI-only (`fg contract publish` #569, log help text). They ship through `release-cli.yml`, not this release. ## After merge Dispatch `.forgejo/workflows/release-agent.yml` with `version: 0.1.66`. It checks these manifests, builds the linux-x64, linux-arm64 and darwin-arm64 binaries, publishes to npm.forgegraf.com, points the fleet update policy at 0.1.66 with per-architecture checksums, and tags `v0.1.66`. Like 0.1.65, it's unsigned: Forgejo runners have no OIDC identity for keyless cosign, and the agent checks the npm checksum. Every auto-updating node takes it on its next poll and restarts its agent. hetzner-fg is no longer self-update-pinned, so it will update too. Independently of this release, #565's prune-script half is already installed by hand on all five nix nodes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

gmackie added 1 commit

2026-09-14 15:54:25 +00:00

chore(release): agent 0.1.66 — root deployed nix store paths; full CI queue reporting

CI / gitleaks (pull_request) Successful in 7s

Details

CI / storybook (pull_request) Successful in 1m36s

Details

CI / web-build (pull_request) Successful in 3m25s

Details

forgegraph/ci CI passed

CI / ci (pull_request) Successful in 11m23s

Details

989648f802

Bumps the four agent packages to 0.1.66 and adds the changelog section.
Two agent-binary changes have landed since 0.1.65 and never shipped:

- #565: deployed nix store paths become GC roots (live + previous), so the
  hourly store prune cannot delete a running service's files. The registry
  lost its binary to exactly that on 2026-09-09 and again on 2026-09-13.
- #556: the CI runner reports the full Forgejo job queue with separate
  totals, busy/idle/offline runner state, and each node's runner slot
  configuration in the heartbeat.

After this merges, dispatch .forgejo/workflows/release-agent.yml with
version 0.1.66 to build, publish, set the fleet policy and tag main.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

gmackie commented

2026-09-14 16:05:13 +00:00

Author

Owner

Preview environment is live: https://pr-577-forgegraph.forgegraf.com

Deployed 989648f8 with the beta stage's environment. It redeploys on every push and is destroyed when this PR closes.

Preview environment is live: https://pr-577-forgegraph.forgegraf.com Deployed `989648f8` with the beta stage's environment. It redeploys on every push and is destroyed when this PR closes.

gmackie merged commit 206d421674 into main

2026-09-14 16:06:38 +00:00

gmackie referenced this pull request from a commit

2026-09-14 16:06:39 +00:00

Merge pull request 'chore(release): agent 0.1.66 — root deployed nix store paths; full CI queue reporting' (#577) from release/agent-0.1.66 into main