Skip to content

Conversation

@TabishB
Copy link
Contributor

@TabishB TabishB commented Jan 11, 2026

Summary

Removes the auto-merge step from the release workflow.

Why

GitHub's auto-merge feature uses an internal token that cannot trigger workflows. Even with manual approval, when auto-merge performs the actual merge, no workflows run.

This is why v0.19.0 didn't publish - the version PR merged but the release workflow never triggered.

New Flow

Feature PR merged
    ↓
Release workflow creates Version PR
    ↓
CI runs on Version PR ✓
    ↓
User manually clicks "Merge" ← Human action triggers workflows
    ↓
Release workflow runs → publishes to npm

Industry Standard

This is the common practice for changesets - manual merge of the version PR provides a checkpoint before publishing.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions release workflow configuration by removing internal automation steps.

✏️ Tip: You can customize this high-level summary in your review settings.

GitHub's auto-merge feature uses an internal token that cannot trigger
workflows. Even with manual approval, the merge performed by auto-merge
doesn't trigger the release workflow.

Removing auto-merge means:
1. Version PR is created with CI running
2. User manually merges the PR (clicking "Merge")
3. The merge triggers the release workflow
4. Package is published

This aligns with industry standard practice for changesets.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 11, 2026

📝 Walkthrough

Walkthrough

This PR removes the changesets step identifier and eliminates automatic merge functionality for version PRs from the release preparation workflow, reducing workflow automation steps.

Changes

Cohort / File(s) Summary
Workflow Configuration
.github/workflows/release-prepare.yml
Removed id: changesets identifier from "Create/Update Version PR" step and deleted the entire "Enable auto-merge for Version PR" step (including conditional execution, gh pr merge command, and GH_TOKEN environment variable)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 No more IDs to chase, no auto-merge in sight,
The workflow grows simpler, oh what a delight!
We hop past the complexity, let humans decide,
When Version PRs merge, with care as our guide.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: removing auto-merge from the CI workflow to fix release triggering issues.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5633556 and ad18233.

📒 Files selected for processing (1)
  • .github/workflows/release-prepare.yml
💤 Files with no reviewable changes (1)
  • .github/workflows/release-prepare.yml

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@vibe-kanban-cloud
Copy link

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.

@TabishB TabishB merged commit 2fbda52 into main Jan 11, 2026
7 checks passed
@TabishB TabishB deleted the remove-auto-merge branch January 11, 2026 02:18
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.

2 participants