Repository navigation
ci(release): cut releases daily instead of on every merge - #776
Conversation
Quest-Claim: a804ef2fb6f38f8d
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 42 minutes. View limit details
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. |
|
No configured credential can serve this run. Your Claude subscription has hit its usage limit, which resets at 2026-11-18 06:00 UTC. Re-trigger after it resets, or add an API key for this provider, which Pullfrog falls back to automatically. The providers' responses
|
1 similar comment
|
No configured credential can serve this run. Your Claude subscription has hit its usage limit, which resets at 2026-11-18 06:00 UTC. Re-trigger after it resets, or add an API key for this provider, which Pullfrog falls back to automatically. The providers' responses
|
|
@pullfrog review this PR's head. (Written by Claude Opus 5.5 with high effort) |
|
No configured credential can serve this run. Your Claude subscription has hit its usage limit, which resets at 2026-11-18 06:00 UTC. Re-trigger after it resets, or add an API key for this provider, which Pullfrog falls back to automatically. The providers' responses
|
There was a problem hiding this comment.
✅ No new issues found.
Approach: sound. Dropping the push trigger is the minimal change, because the existing schedule and workflow_dispatch runs on main already take the release branch in scripts/release-plan.sh.
Reviewed changes
Reviewed the whole diff and checked release.yml for other push dependencies.
release.ymltrigger: removespush: branches: [main]. The remaininggithub.event_nameconditions (concurrency, plan, and publish jobs) only test forpull_request, so they are unaffected.- Docs: the
release.ymlheader comment, CONTRIBUTING.md's Releases section, and SETUP.md's pin guidance now describe the daily cut andgh workflow run release.yml --ref mainfor urgent fixes. I found no other stale "every merge" wording in the repo docs. - Quest file: deletes the finished
quest/m0/daily-release.md.
claude-sonnet-5-5 | 𝕏

Finishes quest/m0/daily-release.md, deleted here.
Summary
.github/workflows/release.yml: drop thepushtomaintrigger. The daily 06:17 UTC schedule and a manual dispatch onmainstill cut a release when the range since the latest release changes what ships; a day with none cuts nothing. Pull request runs still build and check.scripts/release-plan.shis unchanged, since a scheduled or dispatched run onmainalready takes itsrelease=$shipsbranch.release.yml, CONTRIBUTING.md's Releases section (the maintainer's request to edit it), and SETUP.md's pin guidance to the daily cut andgh workflow run release.yml --ref mainfor an urgent fix.Public API
No CLI or wire change. Release cadence changes: at most about one release a day, so consumers get about one bump PR a day. Pre-1.0 versioning is unchanged.
Validation
just checkandjust testpass. Release'son:triggers can only be exercised onmain: the first scheduled run after merge should cut one release for the day's merges (or skip), andgh workflow run release.yml --ref mainshould cut one on demand; neither can run from this branch, where Release only builds and checks. No behavior to run locally.Follow-ups
None.
Models
Size: S
Implementer: Claude Code, claude-sonnet-5-5, unknown effort (arm B)
Review
Rewritten by
quest reviewafter each round.Head: e185735
Base: origin/main at 80cd2c8
Risk: high,
it changes .github/workflows/release.yml, which is always high: workflows run with the repository's secrets and decide what merges and shipsClassified: high by the always-high paths
Reviewer: Codex, gpt-6.1-sol, medium effort
Session:
01a1ebc4-7558-7d51-aa36-dd6035741d91, round 1Score: 10/10,
Removing the push trigger preserves scheduled and manual releases and pull-request validation, and the documentation matches; no actionable defects were found by code inspection, with tests not run as instructed.Rounds: 1; first round 0; findings 0: fixed 0, refuted 0, open 0
Findings: none
Reviewer: Codex, gpt-6.1-sol, low effort, shadow
Session:
01a1ebc4-7558-7861-89bd-c6cdd6f40f57, round 1Score: 10/10,
Removing the push trigger implements the intended release cadence while preserving daily and manual releases and pull-request checks; code inspection found no actionable defects, and builds and tests were not run as instructed.Rounds: 1; first round 0; findings 0: fixed 0, refuted 0, open 0
Findings: none