This workflow allows unpublishing and republishing npm versions using only
GitHub Actions, without needing direct npm CLI access.
Features:
- Unpublishes existing version from npm
- Deletes existing git tags
- Rebuilds and publishes from current branch
- Creates GitHub release
- Updates @latest tag automatically
Usage: Actions → 'Republish Version' → Run workflow
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Add new manual workflow to update npm dist-tags (latest, beta, next, canary)
- Convert beta release workflow to manual-only (removed auto push trigger)
- Convert main release workflow to manual-only (removed auto push trigger)
This gives full manual control over when releases are published and which versions
get which npm tags. Prevents accidental releases from automatic triggers.
To use:
- Release: Go to Actions → "Release" or "Release Beta" → Run workflow
- Update tags: Go to Actions → "Update NPM Dist Tag" → Run workflow
- Fix version from 1.2.5-beta.7 back to official 1.2.5
- Add prerelease version check in release workflow to prevent publishing beta versions as official
- Add branch verification in beta workflow to prevent accidental runs on main branch
This prevents the issue where dev branch with beta versions was merged into main,
causing the main branch to have a prerelease version number.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Workflow now auto-detects highest existing beta (from tags + npm)
- Increments to next beta: X.Y.Z-beta.N -> X.Y.Z-beta.(N+1)
- Updates package.json automatically with [skip ci]
- No manual version bumping needed for dev releases
- Bump base version to 1.2.6 for next release cycle
