Provision FORGEJO_AGENT_TOKEN for dev install publication #22
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Run 1101 built the exact dev source successfully but
publish-device-installfailed because the repository Actions secretFORGEJO_AGENT_TOKENwas absent. The repository Actions secret list was empty, and the authorized HTTPS API write returned HTTP 400 (invalid). The exact-source device release and README QR were then published through the local agent credential and merged todevby PR #21.Configure this secret in repository Settings → Actions → Secrets so future
dev-device.ymlruns can merge their generated device-installation PR automatically. Do not put token values in this issue. Verify the next automation run end to end.Resolved: the dev-device workflow uses the existing repository Actions secret AGENT_TOKEN. The secret is present by name, and dev-device run 1103 succeeded for source
3d681ea9b4; build and publish jobs succeeded and produced the device install artifact. The actual release QR PNG decodes to the same payload as the release install-qr.url.txt and live-dev docs/install-qr.url.txt.