chore(release): agent 0.1.63 — registry credential travels with the deployment #515

Merged
gmackie merged 1 commit from release/agent-0.1.63 into main 2026-08-28 11:05:58 +00:00
Owner

Version bump so #514 reaches the fleet.

Until this ships, #513's registry fix works only because FG_NPM_TOKEN is hand-written into /etc/forgegraph/agent.env on hetzner-fg — invisible, unreproducible, and absent on every other node. 0.1.63 makes the credential arrive with the deployment instead.

Dispatch release-agent.yml with 0.1.63 once merged; the hand-set env line comes out after the fleet is on it.

🤖 Generated with Claude Code

Version bump so #514 reaches the fleet. Until this ships, #513's registry fix works only because `FG_NPM_TOKEN` is hand-written into `/etc/forgegraph/agent.env` on hetzner-fg — invisible, unreproducible, and absent on every other node. 0.1.63 makes the credential arrive with the deployment instead. Dispatch release-agent.yml with 0.1.63 once merged; the hand-set env line comes out after the fleet is on it. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
chore(release): agent 0.1.63 — registry credential travels with the deployment
All checks were successful
CI / gitleaks (pull_request) Successful in 6s
CI / storybook (pull_request) Successful in 2m11s
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 10m39s
146c93ee7a
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!515
No description provided.