Ops: hourly release pulse GITEA_TOKEN authentication regression #37

Closed
opened 2026-08-05 11:01:08 +00:00 by timmy · 0 comments
Owner

The 2026-08-05 hourly release pulse failed its first release-engine dry run with HTTP 401 (user does not exist [uid: 0, name: ]). A freshly generated scoped token restored API access. Acceptance: replace or refresh the stale cron GITEA_TOKEN, then verify the scheduled dry run authenticates without per-run token generation.

The 2026-08-05 hourly release pulse failed its first release-engine dry run with HTTP 401 (`user does not exist [uid: 0, name: ]`). A freshly generated scoped token restored API access. Acceptance: replace or refresh the stale cron `GITEA_TOKEN`, then verify the scheduled dry run authenticates without per-run token generation.
timmy self-assigned this 2026-08-05 11:01:08 +00:00
timmy closed this issue 2026-08-05 12:03:03 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
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: stackchain/stackchain-dashboard#37
No description provided.