fix: compare manifest digests correctly in update check#50
Conversation
- Use RepoDigests (manifest digest) instead of .Image (config blob digest) so local and remote digests are comparable - Filter tag list to date-prefixed tags only (YYYY-MM-DD-sha) so raw git SHA tags don't sort ahead of the real version
|
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 2 minutes and 55 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 (1)
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 |
1 participant
Follow-up to #48. The update check still reported 'update available' even when on latest because:
Wrong digest source:
docker inspect --format {{.Image}}returns the image config blob digest, but GHCR returns the manifest digest - different SHA256s that will never match. Switched toRepoDigestswhich contains the manifest digest.Tag sorting picked wrong tag: raw git SHA tags (e.g.
ffb7ee42...) sorted alphabetically after date-prefixed tags, soremoteVersionshowed a git SHA instead of the date tag. Filtered to onlyYYYY-MM-DD-shaformat tags.