bermudalamb 30859703d2 spike(ci): authenticate with a package-scoped PAT instead of the Actions token (#237) ...

Iteration 2 got as far as the registry and was refused with a 401, not a certificate error, which established that everything except the credential already worked: the docker CLI installs, the daemon is reachable through the mounted socket, the container registry answers on /v2/, and TLS to the Gitea host is trusted from the runner.

The token Actions injects automatically is scoped for the repository API and is not accepted by the package registry. This switches to REGISTRY_TOKEN, a personal access token carrying write:package, which is the one thing the workflow could not arrange for itself.

Ref #237

2026-08-30 16:32:19 -05:00

..

workflows

spike(ci): authenticate with a package-scoped PAT instead of the Actions token (#237)

2026-08-30 16:32:19 -05:00