fix: explain zig version requirement on build failure - #3931
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe Suggested reviewers: Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to This documentation-only build guidance change has no remaining merge-blocking risk. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
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 |
|
@coderabbitai review |
|
✅ Action performedReview finished.
|
|
When
just buildfails with an incompatible Zig installation, the final error now states that Herdr requires Zig 0.16.0 and suggests checkingzig versionor settingZIGto the correct binary. This only extends the existing failure message (one file, +3/-1); it also appears for other Zig build failures.Validation:
just buildpasses on Windows with Zig 0.16.0;cargo fmt --checkandgit diff --checkpass. A directly compiled build script with a deliberately failing compiler invocation confirms the hint is printed. Fulljust checkis unnecessary for this message-only change; no build logic changes.