fix(ci): use checkout persisted credentials for release tag push - #92
Conversation
…ipeline Remove persist-credentials: false so actions/checkout configures git auth automatically via GITHUB_TOKEN. Replace manual http.extraHeader Basic auth push with simple git push, fixing "Failed sending HTTP request" errors that blocked all RC releases since rc.38.
|
Warning Review limit reached
Next review available in: 104 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughO workflow de release deixou de configurar autenticação manual para publicar tags. As etapas de publicação usam ChangesPublicação de releases
Estimated code review effort: 1 (Trivial) | ~5 minutos Mergeability Score: ⚪ Minimal · up to The change simplifies release-tag authentication in the CI workflow and removes the failing manual credential path; no actionable merge-blocking risk remains beyond normal checks. Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
📊 Code Coverage Summary Report
Note Total Filtered Application Coverage: 79.1% (2336 / 2954 lines) 🟡 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #92 +/- ##
========================================
Coverage 86.92% 86.92%
========================================
Files 146 146
Lines 5363 5363
Branches 227 227
========================================
Hits 4662 4662
Misses 505 505
Partials 196 196
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
govulncheck reports CVEs in net/url, crypto/tls, encoding/xml, encoding/asn1, net/http fixed in go1.25.13.
1 participant
Summary
persist-credentials: falsefrom checkout step soactions/checkoutconfigures git auth via GITHUB_TOKEN automaticallyhttp.extraHeaderBasic auth push with simplegit push origin "$TAG"GH_TOKENandGH_REPOSITORYenv vars from the tag stepRoot cause:
persist-credentials: falsestripped git credentials, and the manualhttp.extraHeaderworkaround was failing withFailed sending HTTP requeston GitHub Actions runners — blocking all RC releases since rc.38.Test plan
v1.0.0-rc.40automaticallySummary by CodeRabbit