chore(prisma-cloud): prisma-next 0.15.0 → 0.16.0#156
Conversation
Bump every @prisma-next/* pin (target extension, public package, and the three examples that query through the typed client) to the current 0.16.0 release. Mechanical: typecheck green across all touched packages and the target package's full test suite passes, including the live Postgres migration integration tests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Warning Review limit reached
Next review available in: 22 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: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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: |
The framework bumped its bundled @prisma-next/* to 0.16.0 (prisma/composer#156, shipped in 0.2.0-dev.7); the app follows as a matched pair so the emitted contract and the deploy-side migration tooling stay the same version: composer packages to 0.2.0-dev.7, prisma-next + @prisma-next/postgres to 0.16.0. The 0.16 emit changes the contract format, so the storage hash moved and the init migration was regenerated (same 30 operations, from: null to the new hash). contract.prisma and all app code are untouched — the 0.16 ORM surface is unchanged. Destroyed and redeployed fresh: [database-migrate] ran on the 0.16 tooling, and the abbreviated end-to-end check passed on the deploy-reported URL (shell 200, guest sign-in 200 against the new database with zero manual steps, chat create 201, SSE ready + 3 heartbeats over ~17s). Local dev loop green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
2 participants
Bumps every
@prisma-next/*pin — the target extension, the public@prisma/composer-prisma-cloudpackage, and the three examples that query through the typed client — from0.15.0to the current0.16.0release (published today).Mechanical: no source changes.
turbo typecheckgreen across all touched packages (21/21 tasks) and the target package's full suite passes on 0.16 — 253 tests including the live Postgres migration integration tests — pluscheck:publish-depsclean.Follow-up: prisma/open-chat#1 re-aligns its app toolchain (contract re-emit on 0.16) once this ships in a dev release.
🤖 Generated with Claude Code