ci: tolerate git-cliff output wrapper failures#686
Conversation
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 version-bump repair correctly advanced
homologtov2.260531.3, but the downstreamReleaseworkflow failed in the release-notes job aftergit-cliffgenerated notes:This is a wrapper/output-file-command failure from
orhun/git-cliff-action, not a release-content or source failure.Fix
Make the changelog generation step
continue-on-error: trueand let the following step use/tmp/release-notes.mdwhen present; otherwise it leaves the generated GitHub release body in place.That keeps the signed/published release path from going red because a release-note wrapper failed after producing the file.
Verification
This PR changes only
.github/workflows/release.yml.