Update publish-on-release.yaml and see what happens when manually tri…

…ggered

.github/workflows/publish-on-release.yaml

@@ -7,36 +7,33 @@ name: Create and publish a Docker image on release
 on:
   push:
     branches: ['release']
+  workflow_dispatch:
 
 env:
-  REGISTRY: ghcr.io
+  REGISTRY: us-docker.pkg.dev/uwit-mci-iam/containers
   IMAGE_NAME: ${{ github.repository }}
 
 jobs:
-  build-and-push-image-to-ghcr:
+  build-and-push-image-to-gar:
     runs-on: ubuntu-latest
     permissions:
       contents: read
       packages: write
 
     steps:
       - name: Checkout repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
-      - name: Login to ghcr.io Container registry
-        # should this be pinned?
-        # https://github.com/docker/login-action
-        uses: docker/[email protected]
+      - name: Auth to Cloud
+        uses: 'uwit-iam/action-auth-artifact-registry@main'
         with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GHCR_TOKEN }}
+          credentials: "${{ secrets.MCI_GCLOUD_AUTH_JSON }}"
 
       - name: Extract metadata (tags + labels) for Docker
         id: meta
         # should this be pinned?
         # https://github.com/docker/metadata-action
-        uses: docker/metadata-action@v4.4.0
+        uses: docker/metadata-action@v5.5.1
         with:
           images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}