ci: drop @semantic-release/git to work with protected main - #12
Merged
Conversation
The @semantic-release/git plugin pushes a release commit directly to
main, which the branch protection ruleset rejects ("changes must be
made through a pull request"), aborting the release before npm publish.
Remove it (and @semantic-release/changelog, whose output was only ever
persisted by the git plugin). semantic-release still publishes to npm,
pushes the version tag, and creates the GitHub Release with notes. The
committed CHANGELOG.md and in-repo version bump are dropped; the GitHub
Releases page is the source of truth for release notes.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
🎉 This PR is included in version 1.0.0 🎉 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.
What
Remove
@semantic-release/git(and@semantic-release/changelog) from the release config.Why
@semantic-release/gitpushes achore(release)commit directly tomain, which the branch protection ruleset rejects:This runs in the
preparephase, beforepublish, so it aborted the release beforenpm publishever ran (nothing was published, no tag created).Effect
semantic-release still:
vX.Y.Ztag,Dropped: the committed
CHANGELOG.mdand the in-repopackage.jsonversion bump. The GitHub Releases page is the source of truth for release notes.After merge
Pushing this to
maintriggers a release that should publish 1.0.0 (aBREAKING CHANGEis pending since v0.1.0).🤖 Generated with Claude Code