Repository navigation
Enforce runtime configuration and CI contracts - #22
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 52 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: Organization UI Review profile: ASSERTIVE Plan: Free Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (59)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
66049b2 to
279fe7a
Compare
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
next was pinned below the patched 15.5.16 line (multiple high-severity advisories); drizzle-orm, ws, hono, and several eslint-toolchain transitives were also behind their patched versions. Bumps next/ drizzle-orm directly and pins the rest via pnpm overrides so `pnpm audit --audit-level high` passes.
4bc8f6f to
234e57d
Compare
Refs #15
User-facing problem
Critical provider configuration was validated only when individual routes executed, root checks were poisoned by an unrelated untracked project, and no automated CI/test contract existed.
Implementation summary
process.envreads with typedenvaccess; only the env loader and platform-controlled client bootstrap values remain direct..env.examplewith safe placeholders and requirement comments.Migration notes
No database migration. Deployment environments must add every newly required key before this branch is deployed. Inngest signing/event keys are mandatory when
NODE_ENV=production.Security invariants
Malformed or missing Stripe, app URL, Remotion, storage, auth, and provider configuration fails startup/build validation. CI uses placeholders only; no production credentials are committed. Critical audit findings were reduced from 5 to 0.
Tests run
pnpm install --frozen-lockfilepnpm typecheckpnpm lintwith non-secret production Inngest placeholderspnpm format:checkpnpm test(7 environment-schema tests)pnpm build(18 routes)Checks not run / blocking concern
pnpm audit --audit-level highstill reports 31 high-severity transitive/direct findings after all critical findings were removed. Major remaining sources include Next 15, Remotion, and development toolchains without compatible patched resolutions. The CI gate intentionally remains at high severity and will report failure; it was not weakened or suppressed. A Next 16/toolchain security-upgrade follow-up is required before paid public launch.Stack dependency and merge order
Stack PR 3 of 5. Base:
launch/14-cost-guardrails. Merge #13, #14, #15, #16, then #19.Known limitations
NODE_ENV,VERCEL_URL, andPORTremain direct reads in the client bootstrap because they are framework/platform controls.SKIP_ENV_VALIDATIONremains available as an explicit build control and must not be used in production.Rollback implications
Reverting removes startup guarantees and CI gates. Dependent lifecycle/verification PRs assume Vitest and the corrected TypeScript boundary, so revert them first.
🤖 Generated with Claude Code