Add release-on-merge workflow for protected branches#91
Merged
Conversation
sadjow
marked this pull request as ready for review
January 29, 2026 14:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a new release workflow that works with protected branches.
Instead of pushing tags directly to main, developers can now open PRs with version bumps. After merging, the CI automatically detects unreleased versions and creates the GitHub Release, which triggers the npm publish.
Changes:
release-on-merge.ymlworkflow that detects version bumps and creates releasesrelease:preparesince it no longer pushes