chore: fix a bug whereby gh release was using a wrong tag

Author: collins-w

.github/workflows/publish.yml

@@ -284,11 +284,12 @@ jobs:
       - name: Create Github Release
         uses: softprops/action-gh-release@c95fe1489396fe8a9eb87c0abf8aa5b2ef267fda # v2.2.1
         with:
-          tag_name: v${{ steps.tag.outputs.tag }}
+          tag_name: v${{ steps.tag.outputs.version }}
           body: ${{ steps.extract_release_notes.outputs.release_notes }}
           prerelease: ${{ needs.state.outputs.is_prerelease }}
         env:
           GITHUB_TOKEN: ${{ steps.gh-app-token.outputs.token }}
+          TAG_NAME: 
 
       - name: Publish Job Slack Notification
         uses: act10ns/slack@44541246747a30eb3102d87f7a4cc5471b0ffb7d # v2.1.0

scripts/tag.sh

@@ -12,10 +12,13 @@ dist_tag() {
   elif npx semver -r ">$LATEST_NPM_VERSION" "$PACKAGE_JSON_VERSION" > /dev/null; then
     echo "latest"
   else
-    # This is a patch for an older version
-    # npm can't publish without a tag
     echo "tmp"
   fi
 }
 
+gh_tag() {
+  jq -r .version package.json
+}
+
 echo "tag=$(dist_tag)" >> $GITHUB_OUTPUT
+echo "version=$(gh_tag)" >> $GITHUB_OUTPUT