fix: correct update check and use GitHub-hosted runners#48
Conversation
- Fix update check to compare Docker image digests instead of comparing git version tags to SHA256 hashes - Switch docker build from self-hosted to ubuntu-latest runner to fix DNS/network timeout issues with Docker Hub
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 19 minutes and 8 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
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 |
|
❌ Preview deployment failed. |
Changes
Fix update check: Now compares Docker image digests (SHA256) instead of comparing git version tags to manifest digests. This correctly detects when the running container matches the latest remote image.
Switch to GitHub-hosted runners: Changed from to to fix DNS/network timeout issues when pulling from Docker Hub ().
UX
The version badge in the top-left now accurately shows:
Testing