Skip to content

Conversation

@ryanande
Copy link
Owner

Simplifies the release workflow to work with branch protection on GitHub Free plan:

Key Changes:

  • ✅ No PAT token needed
  • ✅ No PR-based approach needed
  • ✅ No branch protection bypass needed
  • ✅ Works on GitHub Free plan

How it works:

  1. Merge PR to main → workflow triggers
  2. Bumps version in memory
  3. Creates tag from merge commit (no push to main needed)
  4. Creates GitHub Release
  5. Publishes to npm

Trade-off:

  • package.json on main keeps old version
  • Tag and npm package have new version
  • This is standard practice for many projects

Ready to test! This should work perfectly with branch protection.

- One simple job: version, tag, release, publish
- No complex PR creation/merging logic
- Uses marketplace actions for releases
- Much more reliable and maintainable

NOTE: Requires branch protection to allow GitHub Actions bot to push,
or use a PAT with bypass permissions in secrets as GITHUB_TOKEN
- Uses GH_PAT secret if available, falls back to GITHUB_TOKEN
- Allows workflow to push version commits even with branch protection
- No UI changes needed - just add PAT secret
- No PAT needed
- No PR approach needed
- No branch protection bypass needed
- Simply bumps version, creates tag from merge commit, releases, and publishes
- Version in package.json stays at old version, but tag has new version
- This works perfectly with branch protection on free plan
@ryanande ryanande merged commit 7885d7c into main Dec 23, 2025
1 check passed
@ryanande ryanande deleted the feature/pubfix branch January 7, 2026 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants