fix(release): avoid protected branch writes during publish#626
Merged
Conversation
AtulWanve
pushed a commit
to AtulWanve/zeroshot
that referenced
this pull request
Jul 12, 2026
…the-open-engine#627) Release promotion of `dev` -> `main` after the-open-engine#626. ## Why The prior release run for the-open-engine#625 correctly computed `6.5.0`, but failed when `@semantic-release/git` tried to push generated package/changelog changes directly to protected `main`. the-open-engine#626 removes release-time branch writes while keeping semantic-release npm and GitHub release publishing. ## Diff - `.releaserc.json`: remove changelog/git prepare plugins that push commits to `main` ## Verification - the-open-engine#626 PR CI passed - the-open-engine#626 merge-queue CI passed - previous failed release log showed analyzer computed `6.5.0`; failure was only protected branch rejection from `@semantic-release/git` --------- Co-authored-by: tomdps <60640908+tomdps@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: tomdps <tom.dupuis24@gmail.com> Co-authored-by: Eivind Meyer <eivind.meyer@ksat.no> Co-authored-by: Michael Eichelbeck <141341133+mkceichelbeck@users.noreply.github.com> Co-authored-by: Michael Eichelbeck <michael.eichelbeck.ext@wtsde.onmicrosoft.de> Co-authored-by: Ubuntu <ubuntu@ip-172-31-38-53.eu-north-1.compute.internal> Co-authored-by: Eivind <eivind@covibes.ai> Co-authored-by: CI Test <ci-test@covibes.ai> Co-authored-by: Codex <codex@example.com> Co-authored-by: Atharv Singh <132380045+atharvwasthere@users.noreply.github.com> Co-authored-by: Sense_wang <167664334+haosenwang1018@users.noreply.github.com> Co-authored-by: haosenwang1018 <haosenwang1018@users.noreply.github.com> Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local> Co-authored-by: Zeroshot Agent <agent@covibes.ai>
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
1 participant
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
mainWhy
The #625 release run computed
6.5.0, then failed because@semantic-release/gitrangit push --tags ... HEAD:main; branch protection rejected the generated commit becausemainrequires PR + merge queue.Verification
node -e "JSON.parse(require('fs').readFileSync('.releaserc.json','utf8')); console.log('releaserc json ok')"