Upload release upon tagging with created assets.

.github/workflows/release.yml

@@ -2,8 +2,9 @@
 name: Release
 
 on:
-  release:
-    types: [created]
+  push:
+    tags:
+      - '[0-9]+\.[0-9]+\.[0-9]+'
 
 jobs:
 
@@ -43,9 +44,12 @@ jobs:
             rrp \
             bash -c "/ros_release_python/scripts/ros_release_python pip"
 
-      - name: Upload assets to release
+      - name: Create Release with Assets
         run: |
-          gh release upload ${{ github.event.release.tag_name }} dist/*
+          gh release create "${{ github.ref_name }}" \
+            --title "${{ github.ref_name }}" \
+            --generate-notes \
+            dist/*
         env:
           GH_TOKEN: ${{ github.token }}
 

release_playbook.md

@@ -28,18 +28,15 @@ This playbook outlines the steps to release a new version of the `vcs2l` project
    git push origin main
    ```
 
-## 2. Tagging the release
-After merging the PR, create a new tag for the release using the following commands:
-
-```bash
-git checkout main
-git tag x.y.z
-git push origin x.y.z
-```
-
-## 3. Publishing the release on GitHub
-* Navigate to the [Releases](https://github.com/ros-infrastructure/vcs2l/releases/new) page, and select the tag you just pushed.
-* Fill in the release title as `x.y.z`.
-* Create the release notes by using the `Generate release notes` button.
-* Publish the release by setting it as the latest release.
-* This will automatically trigger the GitHub Actions workflow to publish the package to PyPI.
+## 2. Tagging the release and automated publishing
+* After merging the PR, create a new tag for the repository using the following commands:
+
+   ```bash
+   git checkout main
+   git tag x.y.z
+   git push origin x.y.z
+   ```
+* Pushing the tag will automatically create a GitHub release with assets - `*.whl` and `*.tar.gz`.
+  The release notes will be generated automatically based on the merged PRs since the last release.
+
+* This would also publish the package onto PyPI with the newly created version.