fix: use github token fallback in release workflows#39
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 44 minutes and 29 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: defaults Review profile: CHILL 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 |
Summary
github.tokencontext instead of nonexistentsecrets.GITHUB_TOKENRoot cause
actions/checkoutreceived an empty token whenRELEASE_PLEASE_TOKENwas not configured becausesecrets.GITHUB_TOKENis not a real secret. The fetch then fell back to unauthenticated HTTPS and failed withcould not read Username for 'https://github.com': terminal prompts disabled.Verification
.github/workflows/auto-release.ymland.github/workflows/release.ymlwith PyYAML