Merge pull request 'Promote dev to uat (CAR-1034 - auth *.farh.net trustedOrigins fix)' (#27 ) from dev into uat

Merge pull request 'Add *.farh.net origins to trustedOrigins (CAR-1034)' (#26 ) from betty/car-1034-trustedorigins-fix into dev
fix(ci): use REGISTRY_TOKEN for container registry auth (CAR-973)
2026-05-25 21:28:19 +00:00 · 2026-05-25 21:27:53 +00:00 · 2026-05-25 00:04:25 +00:00 · 2026-05-24 20:52:35 +00:00 · 2026-05-24 20:46:48 +00:00 · 2026-05-24 20:38:35 +00:00
1 changed files with 1 additions and 1 deletions
@@ -47,7 +47,7 @@ jobs:
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
-          password: ${{ secrets.GITEA_TOKEN }}
+          password: ${{ secrets.REGISTRY_TOKEN }}

      - name: Extract metadata
        id: meta
Author	SHA1	Message	Date
Savannah Savings	ca423073f1	Merge pull request 'Promote dev to uat (CAR-1034 - auth *.farh.net trustedOrigins fix)' (#27 ) from dev into uat CI / build-and-push (push) Failing after 7s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details	2026-05-25 21:28:19 +00:00
Savannah Savings	d066c14d4b	Merge pull request 'Add *.farh.net origins to trustedOrigins (CAR-1034)' (#26 ) from betty/car-1034-trustedorigins-fix into dev CI / build-and-push (push) Failing after 8s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details CI / build-and-push (pull_request) Has been skipped Details CI / deploy-uat (pull_request) Has been skipped Details CI / deploy-dev (pull_request) Has been skipped Details	2026-05-25 21:27:53 +00:00
Savannah Savings	8bf80a9890	fix(ci): use REGISTRY_TOKEN for container registry auth (CAR-973) CI / build-and-push (push) Failing after 7s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details The REGISTRY_TOKEN secret has write:package scope for git.farh.net. This fixes the unauthorized error at docker login. Related: CAR-1023 (REGISTRY_TOKEN setup), CAR-1009 (CI registry token standardization) Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-05-25 00:04:25 +00:00
Savannah Savings	359d108fee	Merge pull request 'ci: use REGISTRY_TOKEN for docker login (CAR-1024)' (#24 ) from car-1023-use-registry-token into dev CI / build-and-push (push) Failing after 6s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details	2026-05-24 20:52:35 +00:00
Barcode Betty	f0291e8827	ci: use REGISTRY_TOKEN instead of GITEA_TOKEN for docker login (CAR-1024) CI / build-and-push (pull_request) Has been skipped Details CI / deploy-dev (pull_request) Has been skipped Details CI / deploy-uat (pull_request) Has been skipped Details Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-05-24 20:46:48 +00:00
Savannah Savings	a520a65f1b	fix(ci): use GITEA_TOKEN secret for docker login CI / build-and-push (push) Failing after 4s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details The github.token (automatic workflow token) in Gitea Actions doesn't inherit packages:write permission for container registry. Use the GITEA_TOKEN secret instead with direct docker login. Ref: CAR-973, CAR-1009	2026-05-24 20:38:35 +00:00
Savannah Savings	bb8d7f159c	fix(ci): use direct docker login with github.token for registry auth (CAR-973) CI / build-and-push (push) Failing after 6s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details docker/login-action@v3 fails with Gitea's automatic token. Use direct docker login with github.token instead, which has the necessary write:package scope for the container registry. Related: CAR-1009 (CI registry token standardization)	2026-05-24 20:37:22 +00:00
Barcode Betty	a92f578dcf	chore: re-trigger CI after DNS fix (CAR-968) CI / build-and-push (push) Failing after 5s Details CI / deploy-dev (push) Has been skipped Details CI / deploy-uat (push) Has been skipped Details	2026-05-24 20:34:39 +00:00