Repository navigation
fix: release workflow changelog sed mismatch (v prefix) - #65
Conversation
|
Warning Review limit reached
More reviews will be available in 41 minutes and 50 seconds. 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: defaults 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 |
2b68689 to
8e03c0f
Compare
🔍 Cora AI Code Review❌ Blocked — critical issues found. 🔴 Error (1)
Review powered by cora-cli · BYOK · MIT |
…double-escape fix
8e03c0f to
742a53c
Compare
Problem
Release notes for v0.1.3 were empty because the workflow sed pattern looked for
## [v0.1.3]but CHANGELOG uses## [0.1.3](no v prefix).Fix
TAG(v0.1.3) for display/asset names,VERSION(0.1.3) for changelog sed matchTAG, only the sed pattern usesVERSIONImpact
Next release (v0.1.4+) will have correct changelog in release notes.