ci(cli): create release tags with GitHub API#47
Conversation
|
Warning Review limit reached
More reviews will be available in 46 minutes and 46 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
Summary
Why
The first official beta published successfully to npm, but the release workflow failed while pushing
cli-v3.0.0-beta.0because checkout usespersist-credentials: falseand the inline git extraheader did not authenticate the push. The missingcli-v3.0.0-beta.0tag has been repaired manually at the release commit.Validation
ruby -e 'require "yaml"; YAML.load_file(".github/workflows/publish-cli.yml")'extraheader/git push originpath remainsgit diff --check