Skip to content

fix: remove @semantic-release/git to avoid push to protected main#13

Merged
Lefix2 merged 1 commit intomainfrom
claude/fix-semantic-release-protected-branch
May 3, 2026
Merged

fix: remove @semantic-release/git to avoid push to protected main#13
Lefix2 merged 1 commit intomainfrom
claude/fix-semantic-release-protected-branch

Conversation

@Lefix2
Copy link
Copy Markdown
Owner

@Lefix2 Lefix2 commented May 3, 2026

Summary

  • @semantic-release/git was committing the version-bumped package.json directly to main, which fails because main requires changes to go through a PR (GH006: Protected branch update failed)
  • Removing the plugin fixes the error — the version bump is redundant anyway since release.yml already syncs the version from the tag via npm version --no-git-tag-version when it runs

What's removed

["@semantic-release/git", {
  "assets": ["package.json", "package-lock.json"],
  "message": "chore(release): ${nextRelease.version} [skip ci]"
}]

https://claude.ai/code/session_01V2Cfo3mjjVxW1iuVhavsXp


Generated by Claude Code

The plugin commits the version-bumped package.json directly to main,
which fails because main requires PRs. The version is already synced
from the tag in release.yml via npm version --no-git-tag-version, so
this commit-back step is redundant.

https://claude.ai/code/session_01V2Cfo3mjjVxW1iuVhavsXp
@Lefix2 Lefix2 merged commit 77d8d43 into main May 3, 2026
1 check passed
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 3, 2026

🎉 This PR is included in version 1.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants