profile-cards nightly fails 10/10: the Forgejo API call has no token #2

New issue

Closed

opened 2026-09-14 15:53:04 +00:00 by Phil · 0 comments

Phil commented

2026-09-14 15:53:04 +00:00

Owner

P3. profile-cards.yml has failed 10 of 10 scheduled runs in the last 10 days, always within ~12 seconds:

error: GET /user/repos?limit=50&page=1 → 401 {"message":"token is required", ...}
  at generator/src/forgejo.ts:23:15
  at generator/src/forgejo.ts:62:25
  at generator/src/main.ts:56:46

The generator calls the Forgejo API with no credential, so it 401s on the first request and the job dies before producing any card.

Fix

Give the job a Forgejo token in its env (the other scheduled workflows on this instance read theirs from the runner job env — see flow.raven-deployment/.forgejo/workflows/deploy-raven-dev-sweep.yml for the pattern) and have forgejo.ts fail with a named "no token configured" message rather than surfacing a raw 401 from a GET /user/repos.

Why this is worth filing at all

Alone it is cosmetic. It matters because it is one of six scheduled workflows failing nightly into the same alert, and that alert's issue now carries 158 bot comments — the noise is what let a genuine unpatched-n8n finding sit unread. Each of the six needs to go green for the alert to mean something again.

Acceptance

profile-cards.yml exits 0 on its next scheduled run.

**P3.** `profile-cards.yml` has failed **10 of 10** scheduled runs in the last 10 days, always within ~12 seconds: ``` error: GET /user/repos?limit=50&page=1 → 401 {"message":"token is required", ...} at generator/src/forgejo.ts:23:15 at generator/src/forgejo.ts:62:25 at generator/src/main.ts:56:46 ``` The generator calls the Forgejo API with no credential, so it 401s on the first request and the job dies before producing any card. ### Fix Give the job a Forgejo token in its env (the other scheduled workflows on this instance read theirs from the runner job env — see `flow.raven-deployment/.forgejo/workflows/deploy-raven-dev-sweep.yml` for the pattern) and have `forgejo.ts` fail with a named "no token configured" message rather than surfacing a raw 401 from a `GET /user/repos`. ### Why this is worth filing at all Alone it is cosmetic. It matters because it is one of six scheduled workflows failing nightly into the same alert, and that alert's issue now carries **158 bot comments** — the noise is what let a genuine unpatched-n8n finding sit unread. Each of the six needs to go green for the alert to mean something again. ### Acceptance - `profile-cards.yml` exits 0 on its next scheduled run.

Phil referenced this issue from a commit

2026-09-15 06:52:34 +00:00

fix(profile): read the Forgejo token from the runner env, not a missing secret

Phil referenced this issue from a pull request that will close it,

2026-09-15 06:52:53 +00:00

fix(profile): read the Forgejo token from the runner env, not a missing secret #3

Phil closed this issue

2026-09-15 07:02:27 +00:00