fix(ci): use REGISTRY_TOKEN for build-and-push registry login (CAR-1330)
CI / lint (pull_request) Successful in 6s
CI / typecheck (pull_request) Successful in 18s
CI / test (pull_request) Successful in 22s
CI / build-and-push (pull_request) Has been skipped

Unblocks CAR-1132 production deploy. The automatic github.token has no
package/registry write scope; auth's proven-green ci.yml uses
secrets.REGISTRY_TOKEN instead.

cc @cpfarhood
This commit is contained in:
cs_betty
2026-06-09 17:26:39 +00:00
parent 8ace5f0f30
commit 44a89d9c61
+1 -1
View File
@@ -118,7 +118,7 @@ jobs:
echo "CalVer tag: $VERSION"
- name: Log in to Gitea Container Registry
run: echo "${{ github.token }}" | docker login git.farh.net -u ${{ github.actor }} --password-stdin
run: echo "${{ secrets.REGISTRY_TOKEN }}" | docker login git.farh.net -u ${{ github.actor }} --password-stdin
- name: Extract metadata
id: meta