Repository navigation
ci: publish releases on tag push without a changelog - #15
Conversation
Drop --draft so tagged releases go live automatically instead of piling up as unpublished drafts, and drop --generate-notes so the release body stays empty. Also remove the maintainer-only 'How releases are cut' section from the README.
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
What
--draftfrom the release job so a pushedv*tag publishes its release automatically.--generate-notesso the release body stays empty.Why
The release job created every release as a
--draftand nothing ever published them, so every franken release since the repo launched sat unpublished — invisible to anyone following the README's "download from the Releases page" instructions, with asset URLs that 404 for anonymous download. Publishing on tag push fixes that at the source.The README's "How releases are cut" section documented internal release mechanics (draft assets, tag/version conventions, FrankenPHP pinning) that are irrelevant to users downloading a binary.