fix: remove git plugin from semantic-release to resolve branch protection conflicts #22

johnlindquist · 2025-07-07T17:44:06Z

Summary

Removed @semantic-release/git plugin from semantic-release configuration
This resolves conflicts with branch protection rules that were preventing releases

Context

The semantic-release git plugin was trying to push version bumps directly to main, which was blocked by branch protection rules. This has been preventing releases from completing successfully.

By removing this plugin:

GitHub releases will still be created
npm packages will still be published
Version tags will still be created
But no commits will be pushed back to main

This allows all the pending fixes from recent commits to finally be released.

Test plan

Verified semantic-release configuration is valid
PR will trigger release workflow after merge
Release should complete successfully without git push errors

🤖 Generated with Claude Code

Summary by CodeRabbit

Chores
- Updated release configuration to simplify plugin usage during the release process.

…tion conflicts The @semantic-release/git plugin was trying to push version bumps directly to main, which conflicts with branch protection rules. Removing it allows releases to proceed while still creating GitHub releases and publishing to npm.

coderabbitai · 2025-07-07T17:44:12Z

Walkthrough

The .releaserc.json configuration was updated to remove the @semantic-release/git plugin and its related options, leaving only the @semantic-release/github plugin for release automation. No application code or exported entities were changed.

Changes

File(s)	Change Summary
.releaserc.json	Removed `@semantic-release/git` plugin and its options from config.

Possibly related PRs

feat: add GitHub Actions workflow for npm publishing #8: Both PRs involve changes to the semantic-release configuration, specifically the addition or removal of the @semantic-release/git plugin.

Poem

Hopping through the config grass,
The Git plugin’s gone—alas!
Now only GitHub gets the call,
For releases big and small.
With lighter steps, the bunny grins,
As simpler scripts the future wins!
🐇✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bacf2cc and 1728921.

📒 Files selected for processing (1)

.releaserc.json (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.705Z
Learning: Create pull requests to merge into main.

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.705Z
Learning: Semantic Release handles versioning and npm publishing automatically.

.releaserc.json (1)

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.705Z
Learning: Semantic Release handles versioning and npm publishing automatically.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

GitHub Check: test (windows-latest, 20)
GitHub Check: test (macos-latest, 18)
GitHub Check: test (windows-latest, 18)

🔇 Additional comments (1)

.releaserc.json (1)

24-26: Confirm you’re OK with losing the in-repo version bump & changelog commits.

Removing @semantic-release/git stops any commit/push made during the “prepare” phase, so:
• package.json/package-lock.json version numbers
• CHANGELOG.md (if you ever add @semantic-release/changelog)
will no longer be committed back to main.

If that’s intentional (e.g. you rely solely on GitHub releases & npm for version info), all good.
If you still want those artefacts in the repo while keeping branch protection intact, consider:
[
  "@semantic-release/git",
  { "message": "chore(release): ${nextRelease.version} [skip ci]" }
]
and allow that exact commit message pattern through branch protection, or push to a temporary branch and open a PR via @semantic-release/github “success comment” automation.

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.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

github-actions · 2025-07-07T17:47:28Z

🎉 This PR is included in version 1.1.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

johnlindquist enabled auto-merge (squash) July 7, 2025 17:44

johnlindquist merged commit d60ea23 into main Jul 7, 2025
10 checks passed

github-actions bot added the released label Jul 7, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix: remove git plugin from semantic-release to resolve branch protection conflicts #22

fix: remove git plugin from semantic-release to resolve branch protection conflicts #22

Uh oh!

johnlindquist commented Jul 7, 2025 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Jul 7, 2025 •

edited

Loading

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Uh oh!

Uh oh!

github-actions bot commented Jul 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

fix: remove git plugin from semantic-release to resolve branch protection conflicts #22

fix: remove git plugin from semantic-release to resolve branch protection conflicts #22

Uh oh!

Conversation

johnlindquist commented Jul 7, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Context

Test plan

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Jul 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Possibly related PRs

Poem

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

Uh oh!

github-actions bot commented Jul 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

johnlindquist commented Jul 7, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Jul 7, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)