Skip to content

fix(ci): CI-safe npm publish on release #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lakhansamani merged 1 commit into from
Jul 11, 2026
+9 −3
Merged

fix(ci): CI-safe npm publish on release #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 }}
Expand Down
Loading