schedule releases for Monday morning

[jdx]

Summary

• Add an auto-merge workflow for release PRs.
• Run it Monday morning only at 0 10 * * 1 UTC.
• Target the existing release branch PR created by the release-plz task.

Validation

• actionlint -stdin-filename .github/workflows/auto-merge-release.yml -

---

Note

Low Risk
Adds release-timing automation only; merge is gated on a non-empty PR body and uses an existing release token.

Overview
Adds auto-merge-release GitHub Actions workflow to land the existing release → main PR on a fixed schedule instead of merging it manually.

The job runs Mondays at 10:00 UTC (and via workflow_dispatch), only on jdx/usage. It looks up the open PR whose head is release, exits quietly if none exists, and skips merge when the PR body is empty so release-plz can finish filling changelog text before the next run. When ready, it runs gh pr merge --squash --auto using MY_RELEASE_PLEASE_TOKEN. Concurrency is serialized with cancel-in-progress: false so overlapping runs do not fight each other.

^{Reviewed by Cursor Bugbot for commit 03acc4c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 43 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: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 32e5aaa5-86c1-496a-99b2-10ef983f46a9

📥 Commits

Reviewing files that changed from the base of the PR and between 02a06e8 and 03acc4c.

📒 Files selected for processing (1)

• .github/workflows/auto-merge-release.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

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Greptile Summary

Adds a scheduled GitHub Actions workflow that runs at 10:00 UTC every Monday (plus workflow_dispatch) to auto-merge the open release → main PR created by release-plz. No application or runtime code is changed.

• The workflow finds the PR via gh pr list with owner/branch filters, skips gracefully if no PR exists or the body is still empty, then calls gh pr merge --squash --auto using the MY_RELEASE_PLEASE_TOKEN PAT.
• Safety knobs are all present: set -euo pipefail, concurrency group with cancel-in-progress: false, empty permissions: {} at workflow level (PAT supplies the needed access), and a github.repository guard to prevent forks from triggering the merge.

Confidence Score: 5/5

The workflow is CI-only automation with no effect on application code; it is safe to merge.

The script is tightly scoped: it fails loudly on any gh error (set -euo pipefail), skips when no qualifying PR exists, skips when the PR body is empty, and defers the actual merge to GitHub's auto-merge gate so required status checks still run. The PAT is used only as GH_TOKEN, repo permissions are locked down, and the concurrency group prevents concurrent runs.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/auto-merge-release.yml	New scheduled workflow that auto-merges the release → main PR on Monday mornings; well-structured with set -euo pipefail, empty-body guard, PAT auth, concurrency lock, and repo guard.

_{Reviews (1): Last reviewed commit: "harden release PR lookup" | Re-trigger Greptile}