fix: remove @semantic-release/git plugin to prevent protected branch push errors #46
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.
The frontend build workflow was failing with the error:
Root Cause
The issue occurred because:
frontend.yamlworkflow triggers on push to main branchfrontend-build-and-push.yamlas a workflow_call@semantic-release/gitplugin that commits and pushes changes back to the repositorySolution
Removed the
@semantic-release/gitplugin from/frontend/.releaserc.jsonwhile preserving all other semantic-release functionality:This minimal change (removing 7 lines) solves the protected branch push error while maintaining the essential semantic-release features. The workflow will now complete successfully without attempting to push commits back to the protected main branch.
Testing
Fixes #45.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.