Repository navigation
Pin StringZilla by commit - #150
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe StringZilla dependency URL now references commit ChangesStringZilla Pin
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The dependency still targets v4.5.1’s source and keeps its existing content hash; this pin change shows no concrete merge-blocking regression. 🚥 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. A rabbit checks the pinned code, Comment |
StringZilla was the only dependency pinned by tag. It now points at the commit tag v4.5.1 resolves to (
7ca39645), so a moved or deleted tag cannot break fetching. The archive contents and the zig hash are unchanged: a fresh fetch into empty package caches resolves to the sameN-V-__8AAAZ8QgBo...hash,scripts/check-zon-pins.pyreports both dependencies pinned by commit, and the suite passes 681/681 on Zig 0.16 and 0.17.Summary by CodeRabbit