ci(release): include manifest path in the ReleaseNotes-write failure warning#57
Conversation
…warning Brings PlexAutomationToolkit in line with the template and the other modules: the catch warning now names the built manifest (like the missing-path warning) so logs identify which file failed to update. No behavior change. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ 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 build-time warning text in the UpdateReleaseNotes psake task to include the full path of the built module manifest when Update-ModuleManifest fails, improving log diagnosability without changing behavior.
Changes:
- Include
$builtManifestpath in the non-fatalUpdateReleaseNotescatch warning message.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Cosmetic logging parity: the
UpdateReleaseNotescatch warning now names the built manifest path (matching the missing-path warning above and the rest of the fleet), so logs identify which file failed to update. No behavior change.Plex adopted the non-fatal guard in #56, just before this one-line warning-text improvement was added to the template + other modules — this brings it level.
🤖 Generated with Claude Code