Fix release workflow for branch protection#2
Merged
svperfecta merged 1 commit intomainfrom Feb 8, 2026
Merged
Conversation
Stop bumping version and pushing commits to main (blocked by org-level branch protection). Instead, read version from package.json and only push a lightweight tag. Version bumps now happen in PRs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
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.
Summary
npm version patch) and direct commit push tomainfrom the release workflow, which was blocked by org-level branch protection rules.package.jsoninstead of bumping it, and only pushes a lightweight git tag.Test plan
Releaseworkflow manually viaworkflow_dispatchon themainbranch with sample release notes.package.jsoncorrectly.v1.0.1) is created and pushed.mainby the workflow.🤖 Generated with Claude Code