Skip to content

fix: allow release PR recovery - #107

Merged
jan-kubica merged 1 commit into
mainfrom
fix/release-pr-manual-trigger
Aug 13, 2026
Merged

fix: allow release PR recovery#107
jan-kubica merged 1 commit into
mainfrom
fix/release-pr-manual-trigger

Conversation

@jan-kubica

@jan-kubica jan-kubica commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a manual trigger to the Release PR workflow
  • allow recovery when a main-branch push is intentionally or transitively CI-skipped

Verification

  • actionlint .github/workflows/release-pr.yml
  • bun run lint

Summary by CodeRabbit

  • Chores
    • Release pull requests can now be created manually, in addition to being triggered automatically when changes are pushed to the main branch.

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0ddcc2bd-3620-4a71-90de-c7da785e4401

📥 Commits

Reviewing files that changed from the base of the PR and between cc3c8ae and a7dbaa8.

📒 Files selected for processing (1)
  • .github/workflows/release-pr.yml
📜 Recent review details
⏰ Context from checks skipped due to timeout. (9)
  • GitHub Check: Runtime - node / macos-15
  • GitHub Check: Pack
  • GitHub Check: Runtime - bun / ubuntu-latest
  • GitHub Check: Runtime - bun / macos-15
  • GitHub Check: Lint
  • GitHub Check: Runtime - node / ubuntu-latest
  • GitHub Check: Test
  • GitHub Check: Rust
  • GitHub Check: Provenance
🔇 Additional comments (1)
.github/workflows/release-pr.yml (1)

6-6: LGTM!


📝 Walkthrough

Walkthrough

The Release PR workflow now runs after pushes to main or manual execution.

Changes

Release workflow

Layer / File(s) Summary
Add manual workflow trigger
.github/workflows/release-pr.yml
The workflow adds the workflow_dispatch trigger alongside the existing main push trigger.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Mergeability Score: ⚪ Minimal · up to a7dba

This localized workflow change is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarises the workflow change that enables release PR recovery.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-pr-manual-trigger

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.

@jan-kubica
jan-kubica merged commit 361f21e into main Aug 13, 2026
18 checks passed
@jan-kubica
jan-kubica deleted the fix/release-pr-manual-trigger branch August 13, 2026 13:09
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant