fix(ci): resolve HOME before writing the registry token, unblocking main #505
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
gmackie/ForgeGraph!505
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/npmrc-home-on-runners"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
main has not deployed since #499. Every
deployjob is skipped because itstestdependency fails withERR_PNPM_FETCH_401fetching@preflight/runreport.The token was never missing. The
FG_REGISTRY_TOKEN unsetwarning #499 added never fired, so the secret is present. These runners start without HOME, so"$HOME/.npmrc"wrote to/.npmrc, while pnpm resolved~through the passwd entry and read/root/.npmrc. The auth line landed somewhere nothing reads.That is why the error is so misleading: pnpm reports "No authorization header was set" and then lists the
@preflight:registryscope mapping — which reads like a missing secret rather than a file written to the wrong path.This is the same HOME-less-runner gotcha
release-agent.ymlalready works around (it burned a 30-minute release run earlier today). Applies the same resolution before the npmrc write, in all five places:ci.ymlx2,deploy.ymlx2,deploy-staging.yml.Verified with
scripts/test-workflow-yaml.mjs(added by #499) — 7 workflows parse cleanly.🤖 Generated with Claude Code
https://claude.ai/code/session_01CMpzX1b6swjezEptw3T71f