Write release notes from the changelog instead of commit subjects - #23
Conversation
Every release here is a single squashed commit named after the release, so --generate-notes produced a note whose entire body restated the title and linked the PR that produced it. A reader landing on the releases page learned nothing about what changed. The note is now the changelog entry for the version being tagged, followed by install commands and the archive digest with the attestation command to check it against. If no changelog entry matches the tag, the release fails rather than publishing an empty note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 26 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 Plus Run ID: 📒 Files selected for processing (1)
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 |
1 participant
Releases here are one squashed commit each, so
--generate-notesproduced notes whose entire body restated the title and linked the PR that made it — "Release CodeTruss CLI v0.2.39 by @DeliriumPulse in #22". Someone deciding whether to upgrade learned nothing.Notes are now assembled from the CHANGELOG entry for the tagged version, followed by install commands and the archive digest with the
gh attestation verifycommand to check it. Dry-run verified against v0.2.39's entry. If no changelog entry matches the tag, publishing fails loudly rather than shipping an empty note.The four existing releases (v0.2.36–v0.2.39) already had their notes rewritten by hand to this shape. Assets and tags were untouched — those are immutable and attested.
🤖 Generated with Claude Code