Improve release notes handling in publish workflow#1786
Conversation
|
Warning Review limit reached
More reviews will be available in 11 minutes. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions publish workflow to generate RELEASE_NOTES.md from the raw event payload, improving handling of multiline/escaped release bodies when publishing packages.
Changes:
- Write release notes via a single grouped redirection (
{ ... } > RELEASE_NOTES.md) instead of multipleecho >>appends. - Read the release body from
$GITHUB_EVENT_PATHusingjq -r '.release.body // ""'to preserve formatting and avoid expression/quoting pitfalls.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|



Not sure how to test this without just trying it out