Enhance Docker publish workflow for multi-platform support

Updated Docker publish workflow to support multiple platforms and removed unused job.

Author: ThomasJejkal

.github/workflows/docker-publish.yml

@@ -12,22 +12,19 @@ on:
     # Publish `v1.2.3` tags as releases.
     tags:
       - v*
-      - '*-v*'
 
 # Defines two custom environment variables for the workflow. 
 # These are used for the Container registry domain, and a 
 # name for the Docker image that this workflow builds.
 env:
   REGISTRY: ghcr.io
   IMAGE_NAME: ${{ github.repository }}
+  DOCKER_PLATFORMS: linux/amd64,linux/arm64
 
-# Two jobs for creating and pushing Docker image
-# - build-and-push-image -> triggered by commits on main and tagging with semantic version (e.g.: v1.2.3)
-# - build-and-push-image-of-branch -> triggered by tags matching '*-v*' (e.g.: Version_1-v1.2.3)
+# Only one job for creating and pushing Docker image
 jobs:
   build-and-push-image:
     runs-on: ubuntu-latest
-    if: ${{ contains(github.ref_name, '-')  == failure() }}
     # Sets the permissions granted to the `GITHUB_TOKEN` 
     # for the actions in this job.
     permissions:
@@ -36,83 +33,42 @@ jobs:
       # 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v4
       # Uses the `docker/login-action` action to log in to the Container 
       # registry using the account and password that will publish the packages. 
       # Once published, the packages are scoped to the account defined here.
       - name: Log in to the Container registry
-        uses: docker/login-action@v3
+        uses: docker/login-action@327cd5a69de6c009b9ce71bce8395f28e651bf99
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
+
+       # Add support for more platforms with QEMU
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+        
       # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) 
       # to extract tags and labels that will be applied to the specified image. 
       # The `id` "meta" allows the output of this step to be referenced in a 
       # subsequent step. The `images` value provides the base name for the tags 
       # and labels.
       - name: Extract metadata (tags, labels) for Docker
         id: meta
-        uses: docker/metadata-action@v5
+        uses: docker/metadata-action@8e1d5461f02b7886d3c1a774bfbd873650445aa2
         with:
           images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
       # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
       # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
       # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
       - name: Build and push Docker image
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@ca877d9245402d1537745e0e356eab47c3520991
         with:
           context: .
           push: true
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
-  build-and-push-image-of-branch:
-    runs-on: ubuntu-latest
-    if: contains(github.ref_name, '-')
-    # Sets the permissions granted to the `GITHUB_TOKEN` 
-    # for the actions in this job.
-    permissions:
-      contents: read
-      packages: write
-      # 
-    steps:
-      - name: Split first part 
-        env:
-          TAG: ${{ github.ref_name }}
-        id: split
-        run: echo "branch=${TAG%-v*}" >> $GITHUB_OUTPUT
-      - name: Test variable
-        run: |
-          echo ${{ steps.split.outputs.branch }}
-      - name: Checkout repository
-        uses: actions/checkout@v6
-      # Uses the `docker/login-action` action to log in to the Container 
-      # registry using the account and password that will publish the packages. 
-      # Once published, the packages are scoped to the account defined here.
-      - name: Log in to the Container registry
-        uses: docker/login-action@v3
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-      # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) 
-      # to extract tags and labels that will be applied to the specified image. 
-      # The `id` "meta" allows the output of this step to be referenced in a 
-      # subsequent step. The `images` value provides the base name for the tags 
-      # and labels.
-      - name: Extract metadata (tags, labels) for Docker
-        id: meta-branch
-        uses: docker/metadata-action@v5
-        with:
-          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-${{steps.split.outputs.branch}}
-      # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
-      # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
-      # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          push: true
-          tags: ${{ steps.meta-branch.outputs.tags }}
-          labels: ${{ steps.meta-branch.outputs.labels }}
-        
+          platforms: ${{ env.DOCKER_PLATFORMS }}