ci: correct invalid pinned action SHAs#11
Conversation
Earlier SHA-pinning commit referenced SHAs that don't exist in the upstream action repos (typos in the lookup map). This re-resolves each `uses: X@<sha>` against the GitHub commits API and replaces with the verified SHA. Tag comments retained for dependabot tracking.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Followup to the earlier SHA-pinning PR — the SHA lookup map had typos that pinned to non-existent commits, breaking workflow runs. This re-resolves each action ref against
gh api repos/X/commits/Yand replaces with the verified SHA.No semantic change vs the intended pinning; only fixes broken references.