ci: drop broken REPO_TOKEN + grant contents:write#117
Conversation
The release asset upload was hitting 'Bad credentials' because secrets.REPO_TOKEN is expired / not set. Remove the explicit token override and add job-level contents:write so the default GITHUB_TOKEN has enough scope to create the GitHub release. NuGet push is unaffected and already worked via NUGET_API_KEY. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 8 minutes and 44 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
1 participant
The release asset upload failed on tag 4.1.0 with 'Bad credentials' because REPO_TOKEN is stale. Drop the explicit token and rely on the default GITHUB_TOKEN with contents:write scope. Same pattern as NosCore.Packets and NosCore.Shared PRs.