Set a latest/next tag when publishing, depending on the release type

This may have been a requirement in npm 11, where in previous versions of npm, publishing a prerelease would set it on latest (which is not desirable)

Author: dhritzkiv

.github/workflows/release.yml

@@ -60,6 +60,15 @@ jobs:
           node-version: '24.x'
           registry-url: 'https://registry.npmjs.org'
           cache: 'npm'
-      - run: npm publish --provenance --access public
+      - id: release_tag
+        run: |
+          VERSION=$(node -p "require('./package.json').version")
+          if [[ "$VERSION" == *"-"* ]]; then
+            echo "TAG=next" >> $GITHUB_ENV
+          else
+            echo "TAG=latest" >> $GITHUB_ENV
+          fi
+      - name: Publish to NPM
+        run: npm publish --tag "$TAG" --provenance --access public
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}