Repository navigation
Conversation
…Error codes The catalog-registration gate has been failing at baseline on three long-committed codes: SUBSCRIPTION_CANCELLED and REQUEST_ENTITY_TOO_LARGE are plain object-literal error payloads that never construct a LunoraError, so they get a documented allowlist entry instead of a catalog registration. CRON_SCHEDULE_INVALID is minted onto a CodegenDiagnosticError (a LunoraError subclass) via diagnosticAt's Object.assign, so it genuinely needs a catalog entry — added alongside its sibling CRON_*_NOT_STATIC/_INVALID codes, which are already documented as build-time-only and deliberately not internal.
Walk from REPO_ROOT instead of packages/*/src so registry/, shared/, templates/, sdks/, protocol/, tools/, apps/, and examples/ are covered — an unregistered code is treated as client-safe, and registry/templates/ examples are exactly the code users copy into their own apps. The new LunoraError(...) capture group now tolerates any case, since a mint's first argument is unambiguously a code regardless of casing; the code: object-literal group stays SCREAMING_SNAKE_CASE-only to avoid flagging unrelated literals (key names, locale tags, driver error codes) repo-wide. Adds the three SQL_* SqlRejectionCode values to the non-LunoraError allowlist alongside the existing REQUEST_ENTITY_TOO_LARGE/ SUBSCRIPTION_CANCELLED entries, with an integrity assertion that keeps each allowlist entry honest.
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 ignored due to path filters (1)
📒 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 |
❌ Deploy Preview for lunorash failed.
|
|
Thank you for following the naming conventions! 🙏 |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
|
Closing: this PR was opened in error by an automated run, outside the scope of its task. No work is lost — the branch is retained on origin and this PR can be reopened at any time. Context: this branch predates the merges of #288 and #289, so much of its content is already on |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Branched before #288/#289 landed, so it needs a rebase onto current alpha before merge.
Commits
Files this branch still changes relative to alpha