fix(ci): make publish-next non-fatal when version already exists#36
fix(ci): make publish-next non-fatal when version already exists#36namastex888 merged 1 commit intodevfrom
Conversation
The version workflow bumps and publishes separately. If publish-next in CI fails (E403 version exists), it shouldn't block the version workflow from triggering on the next cycle.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
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: defaults Review profile: CHILL 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 |
Prevents publish-next failure from blocking the version workflow chain.