Skip to content

ci: switch cut-release to PR-based flow#19

Merged
sinzin91 merged 1 commit intomainfrom
fix/cut-release-pr-flow
Feb 27, 2026
Merged

ci: switch cut-release to PR-based flow#19
sinzin91 merged 1 commit intomainfrom
fix/cut-release-pr-flow

Conversation

@sinzin91
Copy link
Copy Markdown
Owner

Why

The cut-release workflow was pushing directly to main, which fails on protected branches (protected branch hook declined). This is what caused the orphaned v0.2.0 tag with no release.

Changes

  • cut-release.yml — instead of committing directly to main and tagging, it now creates a release/vX.Y.Z branch and opens a PR
  • tag-on-release-merge.yml (new) — when a release/v* PR merges to main, it creates the git tag and pushes it, which triggers the existing release.yml build + publish pipeline

Flow

workflow_dispatch (cut-release)
  → creates release/vX.Y.Z branch + PR
  → human merges PR
  → tag-on-release-merge creates vX.Y.Z tag
  → release.yml builds binaries + creates GitHub Release + publishes crate

No more direct pushes to protected branches.

Instead of pushing directly to protected main, cut-release now:
1. Creates a release/vX.Y.Z branch with version bump + changelog
2. Opens a PR against main
3. On PR merge, tag-on-release-merge.yml creates the tag
4. Tag push triggers the existing release.yml (build + publish)
@sinzin91 sinzin91 merged commit 7e41c8b into main Feb 27, 2026
5 checks passed
@sinzin91 sinzin91 deleted the fix/cut-release-pr-flow branch February 27, 2026 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant