fix(ci): publish to npm directly instead of the interactive Makefile targets

release.yml called `make publish-rc`/`make publish`, which prompt for
confirmation and re-run commit/tag/push — fine for a human running the
whole release locally, but they cancel in CI (no TTY), so tag-triggered
releases never published. Publish directly, routing -rc./-beta. tags to
the matching npm dist-tag (never latest). NOTE: also requires the
NPM_TOKEN repo secret to be set (currently unset — see PR description).

Author: lakhansamani

.github/workflows/release.yml

@@ -26,11 +26,17 @@ jobs:
               run: make build
 
             - name: Publish to npm
+              # Publish directly here. The Makefile publish-rc/publish targets
+              # are interactive (confirm prompt) and re-do the commit/tag/push —
+              # correct for a human running the whole release locally, but they
+              # hang/cancel in CI, which fires AFTER the tag already exists.
               run: |
-                  if [[ "${{ github.ref }}" =~ -rc\.[0-9]+$ ]]; then
-                    make publish-rc
+                  if [[ "${GITHUB_REF_NAME}" == *-rc.* ]]; then
+                    npm publish --tag rc --access public
+                  elif [[ "${GITHUB_REF_NAME}" == *-beta.* ]]; then
+                    npm publish --tag beta --access public
                   else
-                    make publish
+                    npm publish --access public
                   fi
               env:
                   NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}