Skip to content

fix: Release PRs resume after branch-scoped releases are published#1127

Merged
hatayama merged 1 commit into
v3-betafrom
feature/hatayama/fix-release-pr-label-sync
May 14, 2026
Merged

fix: Release PRs resume after branch-scoped releases are published#1127
hatayama merged 1 commit into
v3-betafrom
feature/hatayama/fix-release-pr-label-sync

Conversation

@hatayama
Copy link
Copy Markdown
Owner

Summary

  • Release automation can now clear stale pending labels even when release-please uses a branch-scoped release title.
  • Future fix and feat merges to v3-beta can open the next release PR instead of being blocked by the previous published release.

User Impact

  • Before this change, a published beta release could still leave its merged release PR marked as pending.
  • After this change, the label sync can identify the published release from the release PR body and mark it as tagged when the release points at the merge commit.

Changes

  • Fall back to the release PR body when the release version is not present in the title.
  • Keep the existing release-target check before updating release PR labels.
  • Add coverage for branch-scoped release titles such as chore: release v3-beta.

Verification

  • scripts/test-sync-published-release-pr-labels.sh
  • scripts/test-mark-release-pr-tagged.sh
  • scripts/test-release-please-config.sh
  • scripts/test-sync-release-please-package-releases.sh
  • scripts/test-is-release-please-release-commit.sh

Release-please can generate branch-scoped titles such as chore: release v3-beta without embedding the version in the title. The stale pending label then blocks later release PR creation even when the release was published, so fall back to the release PR body before deciding the PR cannot be synced.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

Warning

Rate limit exceeded

@hatayama has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 3 minutes and 51 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 82348288-e4b4-4e16-a11e-cb5f60b1990a

📥 Commits

Reviewing files that changed from the base of the PR and between 8412aa4 and 0777286.

📒 Files selected for processing (2)
  • scripts/sync-published-release-pr-labels.sh
  • scripts/test-sync-published-release-pr-labels.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/hatayama/fix-release-pr-label-sync

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.

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

@hatayama hatayama merged commit 141e888 into v3-beta May 14, 2026
5 checks passed
@hatayama hatayama deleted the feature/hatayama/fix-release-pr-label-sync branch May 14, 2026 16:47
@github-actions github-actions Bot mentioned this pull request May 14, 2026
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