fix(ci): use REGISTRY_TOKEN for build-and-push registry login (CAR-1330)
CI / lint (pull_request) Failing after 4s
CI / typecheck (pull_request) Failing after 17s
CI / test (pull_request) Successful in 23s
CI / build-and-push (pull_request) Has been skipped

Parity fix with uat. Prevents reintroduction on next dev->uat promotion.
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:27:08 +00:00
parent 3860a5d061
commit 14b0e73cee
+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