Battery audit dev build blocked by missing repo Actions secret FORGEJO_AGENT_TOKEN #14

Closed
opened 2026-10-07 02:04:22 +03:00 by agent · 0 comments
Collaborator

The current live dev run 1086 for 21c36cde19 built successfully (job 1105; ZPK SHA256 86a6664d757f82aef9c8bb853d24b9c95ae5981ac251c8c6a436daad4fb605b5), but publish job 1106 stopped before creating install artifact/release because tools/linux-device-release.py requires the repository Actions secret FORGEJO_AGENT_TOKEN for generated README PR merge. The exact failure is Missing required repo Actions secret FORGEJO_AGENT_TOKEN for installation PR merge. The current local Forgejo credential is not verified as the dedicated automation bot: /api/v1/user returns 403 (missing read:user), and the repository reports only push/pull permissions, not admin; secrets API previously returned 403 owner-only. Owner/admin action: provision a verified repository-scoped bot credential with only required PR creation/merge rights, and configure it as the repository Actions secret FORGEJO_AGENT_TOKEN. Do not put it in a workflow, commit, issue, or artifacts. Then rerun the dev-device workflow for the latest dev commit. Until then no installable package/QR exists for that SHA; build-only artifact is not installable proof.

The current live dev run 1086 for 21c36cde19714cf3593e5c427ae6aeac567a1c9e built successfully (job 1105; ZPK SHA256 86a6664d757f82aef9c8bb853d24b9c95ae5981ac251c8c6a436daad4fb605b5), but publish job 1106 stopped before creating install artifact/release because tools/linux-device-release.py requires the repository Actions secret FORGEJO_AGENT_TOKEN for generated README PR merge. The exact failure is `Missing required repo Actions secret FORGEJO_AGENT_TOKEN for installation PR merge`. The current local Forgejo credential is not verified as the dedicated automation bot: `/api/v1/user` returns 403 (missing read:user), and the repository reports only push/pull permissions, not admin; secrets API previously returned 403 owner-only. Owner/admin action: provision a verified repository-scoped bot credential with only required PR creation/merge rights, and configure it as the repository Actions secret FORGEJO_AGENT_TOKEN. Do not put it in a workflow, commit, issue, or artifacts. Then rerun the dev-device workflow for the latest dev commit. Until then no installable package/QR exists for that SHA; build-only artifact is not installable proof.
danil closed this issue 2026-10-07 08:18:16 +03:00
Sign in to join this conversation.
No labels
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
danil/bip-max-watch-faces#14
No description provided.