Commit Graph
4 Commits
Author SHA1 Message Date
aneurin a3b44907b8 use secrets.GITEA_TOKEN explicitly
Build / build-and-push (push) Failing after 5s
2026-09-05 13:35:12 +01:00
aneurin d0abd683cc Revert "Fix container registry login: GITEA_TOKEN never grants package access"
CI / frontend-build (pull_request) Has been cancelled
CI / php-tests (pull_request) Has been cancelled
Build / build-and-push (push) Failing after 7s
This reverts commit 8bb9f05559.
2026-09-05 13:21:51 +01:00
aneurinandClaude Sonnet 5 8bb9f05559 Fix container registry login: GITEA_TOKEN never grants package access
CI / php-tests (pull_request) Successful in 22s
CI / frontend-build (pull_request) Successful in 35s
Build / build-and-push (push) Failing after 13m53s
The auto-injected secrets.GITEA_TOKEN doesn't work for pushing to
Gitea's container registry regardless of the workflow's own
permissions: block -- a known Gitea limitation, not a config mistake
(go-gitea/gitea#23642). Switch to a manually-configured
CONTAINER_REGISTRY_PASSWORD secret (a personal access token with
write:package scope) instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-05 12:58:03 +01:00
aneurinandClaude Sonnet 5 950d116e53 Add image build/push workflows, scoped to test/build/push only
CI / php-tests (pull_request) Successful in 19s
CI / frontend-build (pull_request) Successful in 37s
Build / build-and-push (push) Failing after 4s
Builds and pushes to Gitea's container registry on push to main
("latest"/"previous", to avoid accumulating per-commit tags) and on
git tag push (tagged to match). Deployment is intentionally out of
scope here -- that work is being split into a separate project.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-05 12:38:05 +01:00