ci: Changing the naming structure of releases to match expected relea…

…ses (#1389)

.github/workflows/merge.yml

@@ -79,6 +79,7 @@ jobs:
       environment: prod
       tag: ${{ needs.vars.outputs.pr }}
       release: prod
+      params: |
         --set-string global.license='c28f0c' \
         --set-string global.zone='prod' \
         --set-string global.vault.role='prod' \
@@ -110,9 +111,35 @@ jobs:
     env:
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
     steps:
+      - name: Generate release tag
+        id: generate_release_tag
+        uses: amitsingh-007/[email protected]
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          tag_prefix: '${{ github.repository }}-Release-'
+          tag_template: 'i'
+
       - name: Create Release
         run: |
-          gh release create "${{ needs.vars.outputs.pr }}" \
+          gh release create "${{ steps.generate_release_tag.outputs.next_release_tag }}" \
           --repo=${{ github.repository }} \
           --title="${{ github.repository }}-${{ needs.vars.outputs.pr }}" \
           --generate-notes
+
+  promote-images-release:
+    name: Promote Images - Release
+    needs: [create-release]
+    runs-on: ubuntu-22.04
+    permissions:
+      packages: write
+    strategy:
+      matrix:
+        package: [dops, vehicles, frontend, scheduler]
+    timeout-minutes: 2
+    steps:
+      - uses: shrink/actions-docker-registry-tag@v4
+        with:
+          registry: ghcr.io
+          repository: ${{ github.repository }}/${{ matrix.package }}
+          target: prod 
+          tags: ${{ needs.create-release.outputs.generate_release_tag.outputs.next_release_tag }}  #Promote images AFTER successful deploy