fix: accept any warn-capable logger in env validation - #883
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthrough
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This is a localized change to accept warn-capable loggers during environment validation; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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. Comment |
commit: |
📦 Package Size✅ No notable size changes 📚 22 runtime dependencies (no change) All tracked output (27)
Runtime dependencies (22)
Baseline: main_@_5052a9fd___2026-08-22 · gzip is the comparison metric · changes below 16 B gzip are ignored |
🔗 Linked issue
📚 Description
I have a better fix coming in (self-contained nuxt/kit types for the logger) but for now this should unbreak ecosystem-ci