chore: configure semantic-release to create PR instead of direct push - #14
Merged
Conversation
- Configure semantic-release to use 'release' branch - Update workflow to push release branch and create PR - Disable success/fail comments on PR - This avoids protected branch violations on main Co-Authored-By: Claude <noreply@anthropic.com>
baleen37
enabled auto-merge
January 22, 2026 05:53
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughThe release workflow has been enhanced to explicitly configure semantic-release with a designated release branch, suppress GitHub plugin comments, and implement a multi-step process that sets git credentials, executes semantic-release, and automatically creates pull requests when new releases are generated. Changes
Sequence Diagram(s)sequenceDiagram
participant GHA as GitHub Actions<br/>Workflow
participant SR as semantic-release
participant Git as Git Repository
participant GH as GitHub API
GHA->>GHA: Set git user.name & user.email
GHA->>SR: Execute semantic-release<br/>(--branches release)
alt Release Created
SR->>Git: Create release branch
Git-->>GHA: Branch created signal
GHA->>Git: Push release branch to origin
GHA->>GH: Create PR against main<br/>(with RELEASE_VERSION)
else No Release Needed
SR-->>GHA: Echo "No release needed"
end
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Suggested labels
Poem
✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Jan 22, 2026
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
Configure semantic-release to create a PR for releases instead of pushing directly to main, avoiding protected branch violations.
Changes
branches: ['release']in.releaserc.jsrelease.ymlworkflow to:releasebranchreleasebranch and create PRContext
Previously semantic-release tried to push directly to main, which failed due to branch protection rules requiring PRs.
🤖 Generated with Claude Code
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.