ci: gate autorelease on fix and feat commits

[jdx]

What changed

• Adds a preflight check to the release-plz workflow that looks for pending fix or feat conventional commits since the latest v[0-9]* release tag.
• Skips the automatic release-plz job when no release-worthy commits are pending.
• Adds the same guard before the scheduled release PR auto-merge.

Why

This keeps automatic releases from running for maintenance-only commit ranges, while still allowing real fix/feature changes to publish automatically.

Validation

• actionlint .github/workflows/release-plz.yml .github/workflows/auto-merge-release.yml
• git diff --check

---

Note

Low Risk
Changes only CI release automation (schedule, guards, checkout); no application runtime or security-sensitive code paths.

Overview
Updates auto-merge-release so scheduled runs happen daily (10:00 UTC) instead of Mondays only, and adds a checkout step with full history and tags so the merge script can inspect releases and commits.

Before merging release → main, scheduled runs now skip when the latest v[0-9]* tag is younger than 7 days, when there are no fix/feat conventional commits since that tag, or when the same guards would block (manual workflow_dispatch bypasses these checks). Empty-body PR handling is unchanged; the log line now refers to a daily release window.

^{Reviewed by Cursor Bugbot for commit 6b33db1. 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: 37 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: 5e1efc01-f160-4ae4-8279-046797fee10a

📥 Commits

Reviewing files that changed from the base of the PR and between 2e30a7c and 6b33db1.

📒 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.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d637dfa. Configure here.}

[greptile-apps]

Greptile Summary

This PR changes the auto-merge-release workflow from a weekly Monday trigger to a daily one, then adds two gating checks for scheduled runs: the latest v[0-9]* release tag must be at least 7 days old, and there must be at least one fix or feat conventional commit on the default branch since that tag. Manual workflow_dispatch bypasses all guards.

• Changed cron from 0 10 * * 1 (Mondays) to 0 10 * * * (daily), which pairs with the new guards so the check can succeed on any day once conditions are met.
• Added a full-history checkout with fetch-depth: 0 and fetch-tags: true so tag resolution and git log ranges work correctly.
• Guards use git for-each-ref --format='%(creatordate:unix)' (tagger date for annotated tags) for the age check and git log --format=%s "$range" | grep -Eq '^(fix|feat)(\([^)]+\))?!?: ' for the commit-type filter.

Confidence Score: 5/5

Safe to merge — the new guards are logically correct and manual dispatch is always available as an escape hatch.

The guards use well-understood git primitives: for-each-ref returns the tagger date for annotated tags (correctly addressing the previous reviewer concern), and the conventional-commit regex matches both plain and breaking-change variants of fix/feat. The bootstrap path (no tags) skips the commit-type filter, which is the intended behavior. Daily schedule combined with the 7-day minimum-age gate means the workflow runs more often but merges no sooner than before in practice.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/auto-merge-release.yml	Adds git-history checkout, a 7-day tag-age guard, and a fix/feat commit check before auto-merging release PRs; also changes schedule from weekly (Monday) to daily. Logic is sound and previous thread concerns (annotated-tag timestamp, bootstrap case) are handled correctly.

_{Reviews (4): Last reviewed commit: "ci: retry setup-dependent checks" | Re-trigger Greptile}