docs(drive): Prisma 8 RC1 release project — spec, plan, design notes#986
docs(drive): Prisma 8 RC1 release project — spec, plan, design notes#986wmadden-electric wants to merge 8 commits into
Conversation
…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>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (9)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
…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>
size-limit report 📦
|
@prisma-next/extension-author-tools
@prisma-next/mongo-runtime
@prisma-next/family-mongo
@prisma-next/sql-runtime
@prisma-next/family-sql
@prisma-next/extension-arktype-json
@prisma-next/middleware-cache
@prisma-next/mongo
@prisma-next/extension-paradedb
@prisma-next/extension-pgvector
@prisma-next/extension-postgis
@prisma-next/postgres
@prisma-next/sql-orm-client
@prisma-next/sqlite
@prisma-next/extension-supabase
@prisma-next/target-mongo
@prisma-next/adapter-mongo
@prisma-next/driver-mongo
@prisma-next/contract
@prisma-next/utils
@prisma-next/config
@prisma-next/errors
@prisma-next/framework-components
@prisma-next/operations
@prisma-next/ts-render
@prisma-next/contract-authoring
@prisma-next/ids
@prisma-next/psl-parser
@prisma-next/psl-printer
@prisma-next/cli
@prisma-next/cli-telemetry
@prisma-next/config-loader
@prisma-next/emitter
@prisma-next/language-server
@prisma-next/migration-tools
prisma-next
@prisma-next/vite-plugin-contract-emit
@prisma-next/mongo-codec
@prisma-next/mongo-contract
@prisma-next/mongo-value
@prisma-next/mongo-contract-psl
@prisma-next/mongo-contract-ts
@prisma-next/mongo-emitter
@prisma-next/mongo-schema-ir
@prisma-next/mongo-query-ast
@prisma-next/mongo-orm
@prisma-next/mongo-query-builder
@prisma-next/mongo-lowering
@prisma-next/mongo-wire
@prisma-next/sql-contract
@prisma-next/sql-errors
@prisma-next/sql-operations
@prisma-next/sql-schema-ir
@prisma-next/sql-contract-psl
@prisma-next/sql-contract-ts
@prisma-next/sql-contract-emitter
@prisma-next/sql-lane-query-builder
@prisma-next/sql-relational-core
@prisma-next/sql-builder
@prisma-next/target-postgres
@prisma-next/target-sqlite
@prisma-next/adapter-postgres
@prisma-next/adapter-sqlite
@prisma-next/driver-postgres
@prisma-next/driver-sqlite
commit: |
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>
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 mergedprisma/prismarepository, 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
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 intodocs/and deletes it.🤖 Generated with Claude Code