ci: Add release approval pending notify workflow to default branch

[hatayama]

Summary

• The scheduled release-approval-pending check (added on v3-beta in ci: Notify pending release approvals via auto-managed issue #1950) will now actually run — GitHub only fires schedule and workflow_run triggers from workflow files that live on the default branch.

User Impact

• schedule/workflow_run events only ever trigger from a workflow definition on the repository's default branch (main), no matter which branch owns the implementation the workflow calls into. Without this file present here too, the notify workflow added in ci: Notify pending release approvals via auto-managed issue #1950 would sit dormant except when manually run via workflow_dispatch.
• This file is byte-identical to the one on v3-beta. Its checkout step pins ref: v3-beta, since that's where the reconcile command (cli/release-automation/cmd/notify-pending-release-approvals) actually lives — main has no cli/ directory.

Changes

• Add .github/workflows/release-approval-pending-notify.yml (identical to the v3-beta copy in ci: Notify pending release approvals via auto-managed issue #1950).

Verification

• Diffed against the v3-beta copy in ci: Notify pending release approvals via auto-managed issue #1950: byte-identical.
• No Go source changed in this PR, so scripts/check-go-cli.sh is not applicable here; it was run and green for the underlying implementation in ci: Notify pending release approvals via auto-managed issue #1950.

Companion to #1950.

[coderabbitai]

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b2be7848-2d8e-45b2-89dd-124b3951eb0a

📥 Commits

Reviewing files that changed from the base of the PR and between 98b4ab0 and fdb8094.

📒 Files selected for processing (1)

• .github/workflows/release-approval-pending-notify.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/release-approval-pending-notify-main

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}