github: use a different release/publish pipeline

Having a draft means that the final asset won't be visible outside the project which is what we want. This entails tagging a release each time we run the steps. Signed-off-by: Alex Bennée <[email protected]>
Linaro · Dec 19, 2024 · dd3c081 · dd3c081
1 parent 6b9e930
commit dd3c081
Showing 1 changed file with 17 additions and 7 deletions.
diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml
@@ -18,11 +18,21 @@ jobs:
           make local-all
           echo ${{ github.sha }} > Release.txt
 
-      - name: Create a Draft Release
-        uses: softprops/action-gh-release@v2
+      - name: Create Draft Release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-          draft: true
-          name: working-draft
-          files: |
-            Release.txt
-            virtio-v1.4-wd01.pdf
+          tag_name: virio-msg-draft-v${{ github.run_number }} # Or a more meaningful tag
+          release_name: Draft ${{ github.run_number }}
+          draft: false
+          prerelease: false
+      - name: Upload Release Asset
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          upload_url: ${{ steps.create_release.outputs.upload_url }}
+          asset_path: .
+          asset_name: virtio-v1.4-wd01.pdf
+          asset_content_type: application/pdf