ci: tolerate git-cliff output wrapper failures on default release workflow#687
Conversation
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
More reviews will be available in 6 minutes and 16 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: Path: .coderabbit.yaml Review profile: ASSERTIVE 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 |
Why
The homolog tag release workflow is executed from the default
mainworkflow file forworkflow_runevents. The homolog-side fix was not enough: release runs forv2.260531.3/v2.260531.4still failed inGenerate changelogwith:Fix
Patch the default
mainrelease workflow to tolerate theorhun/git-cliff-actionoutput-wrapper failure and ensure/tmp/release-notes.mdexists beforegh release create.Scope
Workflow-only patch:
.github/workflows/release.yml.Verification