Seriously considering farming

.github/workflows/build-and-release.yaml → .github/workflows/build-sign-and-release.yaml

@@ -46,7 +46,7 @@ jobs:
           name: ForceBindIPGUI
           path: dist/windows/ForceBindIP-GUI.exe
 
-  release:
+  sign-and-release:
     runs-on: [ubuntu-latest]
     needs: build
     permissions:
@@ -66,20 +66,20 @@ jobs:
         id: get_short_sha
         run: echo "short_sha=$(echo ${{ github.sha }} | cut -c1-10)" >> $GITHUB_ENV
 
-    # https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/#step-9-trusted-signing-in-ci-github
-    - name: Azure Trusted Signing
-      uses: azure/trusted-signing-action@v0.3.16
-      with:
-        azure-tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-        azure-client-id: ${{ secrets.AZURE_CLIENT_ID }}
-        azure-client-secret: ${{ secrets.AZURE_CLIENT_SECRET }}
-        endpoint: ${{ secrets.AZURE_ENDPOINT }}
-        trusted-signing-account-name: ${{ secrets.AZURE_CODE_SIGNING_NAME }}
-        certificate-profile-name: ${{ secrets.AZURE_CERT_PROFILE_NAME }}
-
-        # Sign all exes inside the folder
-        files-folder: ./dist 
-        files-folder-filter: exe
+      # https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/#step-9-trusted-signing-in-ci-github
+      - name: Azure Trusted Signing
+        uses: azure/trusted-signing-action@v0.3.16
+        with:
+          azure-tenant-id: ${{ secrets.AZURE_TENANT_ID }}
+          azure-client-id: ${{ secrets.AZURE_CLIENT_ID }}
+          azure-client-secret: ${{ secrets.AZURE_CLIENT_SECRET }}
+          endpoint: ${{ secrets.AZURE_ENDPOINT }}
+          trusted-signing-account-name: ${{ secrets.AZURE_CODE_SIGNING_NAME }}
+          certificate-profile-name: ${{ secrets.AZURE_CERT_PROFILE_NAME }}
+          
+          # Sign all exes inside the folder
+          files-folder: ./dist 
+          files-folder-filter: exe
 
       - name: Create Release
         id: create_release