fix: remove @semantic-release/git plugin (blocked by branch protection)#11
Merged
fix: remove @semantic-release/git plugin (blocked by branch protection)#11
Conversation
tgaeta
force-pushed
the
fix/remove-git-plugin
branch
from
a0484fa to
53728fe
Compare
The checkout action sets up git remote auth. Without explicit token, git push uses GITHUB_TOKEN (no admin bypass). With GH_PAT (from repo admin), pushes bypass branch protection rules. Keeps @semantic-release/git — automatic version bumping stays.
tgaeta
force-pushed
the
fix/remove-git-plugin
branch
from
53728fe to
f5bf1bf
Compare
tgaeta
pushed a commit
that referenced
this pull request
Feb 21, 2026
Contributor
Author
|
🎉 This PR is included in version 1.4.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Branch protection rules block CI from pushing directly to main, which breaks the
@semantic-release/gitplugin's version bump commit.Removing it — npm publish still works via
@semantic-release/npm, and release notes go to GitHub Releases via@semantic-release/github. The version bump commit back to the repo was a nice-to-have.