- continue-on-error on the dist-tag advance: failure leaves @next stale until the next push-driven prerelease, which is recoverable; failing the job after a successful publish + git tag + GH release is not. - Status echo so release-log triage can confirm the advance ran. - Add removals.txt to the push-trigger path filter. Installer-affecting changes outside src/** (like the post-6.5.0 removals.txt fix) should still trigger a fresh -next.0 publish. |
||
|---|---|---|
| .. | ||
| coderabbit-review.yaml | ||
| discord.yaml | ||
| docs.yaml | ||
| publish.yaml | ||
| quality.yaml | ||