fix(release): remove direct-to-main push that violates branch protection#186
Merged
Conversation
…ion rules Co-authored-by: bestdan <2766380+bestdan@users.noreply.github.com> Agent-Logs-Url: https://github.com/bestdan/tsu/sessions/2e64161c-1235-4814-af9b-2b76ab5c7c63
Copilot created this pull request from a session on behalf of
bestdan
March 23, 2026 15:12
View session
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
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
release.ymlworkflow was committing a version bump directly tomainand pushing it, which is blocked by branch protection rules (PRs + status checks required). The workflow failed every run withGH013: Repository rule violations found for refs/heads/main.Changes
Remove "Configure Git" and "Update version in package.json" steps — these committed
package.jsonand pushed tomain. Version bumps are already handled viaauto-version-bump.yml(creates a PR post-merge) andtag-version.yml(tags after the bump PR merges). The release workflow doesn't need to duplicate this.Move "Generate changelog" before "Create and push tag" — if changelog generation ran after tagging HEAD,
git describe --tags --abbrev=0would resolve to the newly-created tag, makinggit log v$VERSION..HEADreturn nothing. Generating the changelog before tagging ensuresgit describefinds the previous tag.Resulting step order