hotfix: parche deepmerge-ts y habilita cuentas admins de la USCO - #190
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NdbkqktLvD9XHtLHf3nThV
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NdbkqktLvD9XHtLHf3nThV
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NdbkqktLvD9XHtLHf3nThV
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NdbkqktLvD9XHtLHf3nThV
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 41 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughLa validación de correo institucional acepta cualquier parte local válida de ChangesValidación de correo institucional
Configuración de resolución
Estimated code review effort: 2 (Simple) | ~10 minutos Merge Risk: 🟡 Moderate · up to The authentication change still permits malformed institutional email addresses with leading, trailing, or consecutive dots. The validation rule and regression tests should be corrected before merging to avoid accepting addresses outside the intended format. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
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 |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NdbkqktLvD9XHtLHf3nThV
Resumen
deepmerge-tspara actualizarlo a la versión8.0.0mediante el override de pnpm.@usco.edu.co.Verificación
pnpm test— 146 pasaronpnpm lint— 0 erroresnpx tsc --noEmit— sin errorespnpm build— pendiente (requiere variables de entorno)Análisis automático de CodeRabbit
Cambios principales
deepmerge-tsa la versión8.0.0mediante un override enpnpm-workspace.yaml.@usco.edu.co.AGENTS.md.Verificación
pnpm test: 146 pruebas exitosas.pnpm lint: 0 errores.npx tsc --noEmit: sin errores.pnpm build: pendiente por variables de entorno requeridas.