Skip to content

docs(drive): Prisma 8 RC1 release project — spec, plan, design notes#986

Open
wmadden-electric wants to merge 8 commits into
mainfrom
project/prisma-8-rc1
Open

docs(drive): Prisma 8 RC1 release project — spec, plan, design notes#986
wmadden-electric wants to merge 8 commits into
mainfrom
project/prisma-8-rc1

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

What this is

The Prisma 8 RC1 release program, recorded as a Drive project under projects/prisma-8-rc1/. The strategy was settled in operator discussion on July 15; these docs are the durable record the team executes against.

The decision: Prisma Next ships as prisma@8.0.0-rc.1, published from the merged prisma/prisma repository, by July 31 2026 — same repo, same package, announcement live the same day. The RC bar is "everything we ship works", not v7 parity; the API surface freezes at RC.

What's in it

  • spec.md — purpose, the parallel-install at-a-glance example, non-goals, the freeze-set cross-cutting requirements, transitional-shape constraints, and the project DoD.
  • plan.md — owner lanes (Will / agent-executed / Serhii / Alexey), twelve slices, the four checkpoint milestones (Jul 18 error scheme → Jul 22 Postgres floor → Jul 24 go/no-go → Jul 31 ship), and the few real sequencing constraints.
  • design-notes.md — every settled decision with rationale: version 8, merge-on-branch, the two-bin coexistence answer, v7-owns-migrations-until-cutover (ADR 122), visible-set-only package rename, error-scheme consolidation, snapshot centralization, mine-don't-convert testing, public measurements-only Bencher — with rejected alternatives collected at the end.

Tracking

Org-visible tracking is the Linear project Prisma 8 RC1 (milestones + status updates; tickets minted just-in-time as slices start). Per projects/README.md, this directory is transient: close-out migrates the durable docs into docs/ and deletes it.

🤖 Generated with Claude Code

…gn notes)

Records the settled Prisma 8 RC1 strategy as a Drive project: ship
prisma@8.0.0-rc.1 from the merged prisma/prisma repo by July 31 2026.
Spec carries the freeze-set requirements and DoD, plan carries the
owner lanes and checkpoint milestones, design notes carry every settled
decision with rationale and rejected alternatives.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@wmadden-electric
wmadden-electric requested a review from a team as a code owner July 15, 2026 17:46
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (9)
  • projects/prisma-8-rc1/README.md is excluded by !projects/**
  • projects/prisma-8-rc1/design-notes.md is excluded by !projects/**
  • projects/prisma-8-rc1/feature-surface.md is excluded by !projects/**
  • projects/prisma-8-rc1/parallel-install.md is excluded by !projects/**
  • projects/prisma-8-rc1/plan.md is excluded by !projects/**
  • projects/prisma-8-rc1/release-definition.md is excluded by !projects/**
  • projects/prisma-8-rc1/repo-migration.md is excluded by !projects/**
  • projects/prisma-8-rc1/scoreboard.md is excluded by !projects/**
  • projects/prisma-8-rc1/spec.md is excluded by !projects/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: fa950bb9-ab63-4a54-985f-2851c62dbdd8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch project/prisma-8-rc1

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…rces; start it now

Rows come from (1) the v8 surface enumerated from the codebase and
(2) Prisma 7 capability taxonomy as the completeness checklist, so
missing capabilities are named rather than silently absent. Phase 1
(enumeration + no-proving-suite list) has no dependencies and starts
immediately; only the Jul 24 status freeze waits on the floor and
polymorphism decisions.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
…board

No separate progress board: cells flipping from cross to tick as
proving suites go green is the distance-to-done reading.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown

size-limit report 📦

Path Size
postgres / no-emit 158.95 KB (0%)
postgres / emit 132.46 KB (0%)
mongo / no-emit 98.71 KB (0%)
mongo / emit 89.43 KB (0%)
cf-worker / no-emit 185.12 KB (0%)
cf-worker / emit 155.88 KB (0%)

@pkg-pr-new

pkg-pr-new Bot commented Jul 15, 2026

Copy link
Copy Markdown

Open in StackBlitz

@prisma-next/extension-author-tools

npm i https://pkg.pr.new/@prisma-next/extension-author-tools@986

@prisma-next/mongo-runtime

npm i https://pkg.pr.new/@prisma-next/mongo-runtime@986

@prisma-next/family-mongo

npm i https://pkg.pr.new/@prisma-next/family-mongo@986

@prisma-next/sql-runtime

npm i https://pkg.pr.new/@prisma-next/sql-runtime@986

@prisma-next/family-sql

npm i https://pkg.pr.new/@prisma-next/family-sql@986

@prisma-next/extension-arktype-json

npm i https://pkg.pr.new/@prisma-next/extension-arktype-json@986

@prisma-next/middleware-cache

npm i https://pkg.pr.new/@prisma-next/middleware-cache@986

@prisma-next/mongo

npm i https://pkg.pr.new/@prisma-next/mongo@986

@prisma-next/extension-paradedb

npm i https://pkg.pr.new/@prisma-next/extension-paradedb@986

@prisma-next/extension-pgvector

npm i https://pkg.pr.new/@prisma-next/extension-pgvector@986

@prisma-next/extension-postgis

npm i https://pkg.pr.new/@prisma-next/extension-postgis@986

@prisma-next/postgres

npm i https://pkg.pr.new/@prisma-next/postgres@986

@prisma-next/sql-orm-client

npm i https://pkg.pr.new/@prisma-next/sql-orm-client@986

@prisma-next/sqlite

npm i https://pkg.pr.new/@prisma-next/sqlite@986

@prisma-next/extension-supabase

npm i https://pkg.pr.new/@prisma-next/extension-supabase@986

@prisma-next/target-mongo

npm i https://pkg.pr.new/@prisma-next/target-mongo@986

@prisma-next/adapter-mongo

npm i https://pkg.pr.new/@prisma-next/adapter-mongo@986

@prisma-next/driver-mongo

npm i https://pkg.pr.new/@prisma-next/driver-mongo@986

@prisma-next/contract

npm i https://pkg.pr.new/@prisma-next/contract@986

@prisma-next/utils

npm i https://pkg.pr.new/@prisma-next/utils@986

@prisma-next/config

npm i https://pkg.pr.new/@prisma-next/config@986

@prisma-next/errors

npm i https://pkg.pr.new/@prisma-next/errors@986

@prisma-next/framework-components

npm i https://pkg.pr.new/@prisma-next/framework-components@986

@prisma-next/operations

npm i https://pkg.pr.new/@prisma-next/operations@986

@prisma-next/ts-render

npm i https://pkg.pr.new/@prisma-next/ts-render@986

@prisma-next/contract-authoring

npm i https://pkg.pr.new/@prisma-next/contract-authoring@986

@prisma-next/ids

npm i https://pkg.pr.new/@prisma-next/ids@986

@prisma-next/psl-parser

npm i https://pkg.pr.new/@prisma-next/psl-parser@986

@prisma-next/psl-printer

npm i https://pkg.pr.new/@prisma-next/psl-printer@986

@prisma-next/cli

npm i https://pkg.pr.new/@prisma-next/cli@986

@prisma-next/cli-telemetry

npm i https://pkg.pr.new/@prisma-next/cli-telemetry@986

@prisma-next/config-loader

npm i https://pkg.pr.new/@prisma-next/config-loader@986

@prisma-next/emitter

npm i https://pkg.pr.new/@prisma-next/emitter@986

@prisma-next/language-server

npm i https://pkg.pr.new/@prisma-next/language-server@986

@prisma-next/migration-tools

npm i https://pkg.pr.new/@prisma-next/migration-tools@986

prisma-next

npm i https://pkg.pr.new/prisma-next@986

@prisma-next/vite-plugin-contract-emit

npm i https://pkg.pr.new/@prisma-next/vite-plugin-contract-emit@986

@prisma-next/mongo-codec

npm i https://pkg.pr.new/@prisma-next/mongo-codec@986

@prisma-next/mongo-contract

npm i https://pkg.pr.new/@prisma-next/mongo-contract@986

@prisma-next/mongo-value

npm i https://pkg.pr.new/@prisma-next/mongo-value@986

@prisma-next/mongo-contract-psl

npm i https://pkg.pr.new/@prisma-next/mongo-contract-psl@986

@prisma-next/mongo-contract-ts

npm i https://pkg.pr.new/@prisma-next/mongo-contract-ts@986

@prisma-next/mongo-emitter

npm i https://pkg.pr.new/@prisma-next/mongo-emitter@986

@prisma-next/mongo-schema-ir

npm i https://pkg.pr.new/@prisma-next/mongo-schema-ir@986

@prisma-next/mongo-query-ast

npm i https://pkg.pr.new/@prisma-next/mongo-query-ast@986

@prisma-next/mongo-orm

npm i https://pkg.pr.new/@prisma-next/mongo-orm@986

@prisma-next/mongo-query-builder

npm i https://pkg.pr.new/@prisma-next/mongo-query-builder@986

@prisma-next/mongo-lowering

npm i https://pkg.pr.new/@prisma-next/mongo-lowering@986

@prisma-next/mongo-wire

npm i https://pkg.pr.new/@prisma-next/mongo-wire@986

@prisma-next/sql-contract

npm i https://pkg.pr.new/@prisma-next/sql-contract@986

@prisma-next/sql-errors

npm i https://pkg.pr.new/@prisma-next/sql-errors@986

@prisma-next/sql-operations

npm i https://pkg.pr.new/@prisma-next/sql-operations@986

@prisma-next/sql-schema-ir

npm i https://pkg.pr.new/@prisma-next/sql-schema-ir@986

@prisma-next/sql-contract-psl

npm i https://pkg.pr.new/@prisma-next/sql-contract-psl@986

@prisma-next/sql-contract-ts

npm i https://pkg.pr.new/@prisma-next/sql-contract-ts@986

@prisma-next/sql-contract-emitter

npm i https://pkg.pr.new/@prisma-next/sql-contract-emitter@986

@prisma-next/sql-lane-query-builder

npm i https://pkg.pr.new/@prisma-next/sql-lane-query-builder@986

@prisma-next/sql-relational-core

npm i https://pkg.pr.new/@prisma-next/sql-relational-core@986

@prisma-next/sql-builder

npm i https://pkg.pr.new/@prisma-next/sql-builder@986

@prisma-next/target-postgres

npm i https://pkg.pr.new/@prisma-next/target-postgres@986

@prisma-next/target-sqlite

npm i https://pkg.pr.new/@prisma-next/target-sqlite@986

@prisma-next/adapter-postgres

npm i https://pkg.pr.new/@prisma-next/adapter-postgres@986

@prisma-next/adapter-sqlite

npm i https://pkg.pr.new/@prisma-next/adapter-sqlite@986

@prisma-next/driver-postgres

npm i https://pkg.pr.new/@prisma-next/driver-postgres@986

@prisma-next/driver-sqlite

npm i https://pkg.pr.new/@prisma-next/driver-sqlite@986

commit: 242917c

Replaces the owner-lane plan with a set of plain-English documents
that go from high-level goals to concrete steps, independent of who
does what: release definition, correctness scoreboard, feature
surface, repo migration, parallel install, and a dated step plan.
Ownership lives in Linear, not in these docs.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
… defers

Publish access to the prisma package exists, so the registry step is
release-week configuration, not an external dependency. The critical
path reduces to the merge branch and the side-by-side fixture. Also
spell out that the small four-package public API ships at RC (facade
parity landed in May); only the bundling of internals is deferred.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Bin-name collisions between two installed packages resolve
differently per package manager, so coexistence must not depend on
v7 winning one. With only prisma-next declared there is no collision:
prisma means v7 everywhere until v7 is removed. Whether v8 ever adds
a bare prisma binary is deferred to the road to final; adding a bin
later is additive.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
…age manager

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Native column types currently ride on v7-style @db. attributes in
named-type aliases; PSL syntax freezes at RC, so the removal and its
replacement spelling must land before July 31.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant