docs(drive): Prisma 8 RC1 release project — spec, plan, design notes by wmadden-electric · Pull Request #986 · prisma/prisma-next

wmadden-electric · 2026-07-15T17:46:37Z

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

coderabbitai · 2026-07-15T17:46:47Z

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (11)

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/roadmap.html is excluded by !projects/**
projects/prisma-8-rc1/roadmap.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: 3fbffc47-5284-4505-ba76-afc8a4111b4d

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.}

github-actions · 2026-07-15T17:51:13Z

size-limit report 📦

Path	Size
postgres / no-emit	160.64 KB (0%)
postgres / emit	144.07 KB (0%)
mongo / no-emit	99.3 KB (0%)
mongo / emit	89.52 KB (0%)
cf-worker / no-emit	186.82 KB (0%)
cf-worker / emit	168.17 KB (0%)

pkg-pr-new · 2026-07-15T17:53:16Z

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: 3b47819

Per-feature availability of Prisma Next across Postgres, SQLite, and MongoDB, feeding the Prisma 8 RC1 release project (PR #986). Each cell states whether the feature is available in Prisma Next; the evidence column points only to Prisma Next test suites. Lists all exposed features (mined from the public surface) plus every notable Prisma 7 feature Prisma Next lacks, so absences are named. A cell is marked Works only when a genuine integration test (executing against PGlite / SQLite / mongodb-memory-server and asserting results) proves it for that database; unit tests (SQL/AST/plan/type/snapshot assertions) do not qualify and leave the cell Untested. Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

Per-feature availability of Prisma Next across Postgres, SQLite, and MongoDB, feeding the Prisma 8 RC1 release project (PR #986). Each row is a single atomic feature; each cell states availability for that database and cites only Prisma Next tests. Lists all exposed features (mined from the public surface) plus every notable Prisma 7 feature Prisma Next lacks, so absences are named. A cell is marked Works only when a genuine integration test (executing against PGlite / SQLite / mongodb-memory-server and asserting results) proves it for that database; unit tests (SQL/AST/plan/type/snapshot assertions) do not qualify. Distinct capabilities are never bundled into one cell: each operator, command, stage, and attribute is its own row. Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

Per-feature availability of Prisma Next across Postgres, SQLite, and MongoDB, feeding the Prisma 8 RC1 release project (PR #986). scorecard.md is the index (intro, legend, coverage summary, links); the matrix itself lives under scorecard/, one file per category. Each row is a single atomic feature; each cell states availability for that database and cites only Prisma Next tests. A cell is marked Works only when a genuine integration test (executing against PGlite / SQLite / mongodb-memory-server and asserting results) proves it for that database; unit tests do not qualify. Distinct capabilities are never bundled into one cell. Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

wmadden-electric · 2026-07-21T13:59:42Z

Gzip scope deviation — #1018 (TML-3059)

This RC1 plan item — "Deduplicate migration contract snapshots into migrations/snapshots/ … .json.gz accepted from day one" — shipped without gzip support, deliberately.

Gzip reader-tolerance was dropped entirely because it preserves no real option: TypeScript cannot resolve a gzipped .d.ts, and the emitted migration.ts's ESM JSON import (import contract from '…/contract.json' with { type: "json" }) cannot decompress at import time. Reader-side tolerance would only ever help tooling that reads store files directly, while every committed migration.ts still requires plain JSON — so there is no size-reduction outcome gzip support would unlock without breaking the emitted import.

Everything else in the plan item shipped as specified: a content-addressed store at migrations/snapshots/<hex>/contract.{json,d.ts}, the migrations/ folder layout frozen for RC. Rationale recorded in ADR 239.

Per-feature availability of Prisma Next across Postgres, SQLite, and MongoDB, feeding the Prisma 8 RC1 release project (PR #986). scorecard.md is the index (intro, legend, coverage summary, links); the matrix itself lives under scorecard/, one file per category. Each row is a single atomic feature; each cell states availability for that database and cites only Prisma Next tests. A cell is marked Works only when a genuine integration test (executing against PGlite / SQLite / mongodb-memory-server and asserting results) proves it for that database; unit tests do not qualify. Distinct capabilities are never bundled into one cell. Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

wmadden-electric · 2026-07-21T16:13:32Z

Rendered preview of projects/prisma-8-rc1/roadmap.html:
https://html-preview.github.io/?url=https://github.com/prisma/prisma-next/blob/project/prisma-8-rc1/projects/prisma-8-rc1/roadmap.html

(Client-side wrapper over the raw file — no build, nothing hosted. Once this merges, the same link works with main in place of the branch. If we want a clean permanent URL for sharing outside the org, GitHub Pages on this repo is the durable answer.)

Per-feature availability of Prisma Next across Postgres, SQLite, and MongoDB, feeding the Prisma 8 RC1 release project (PR #986). scorecard.md is the index (intro, legend, coverage summary, links); the matrix itself lives under scorecard/, one file per category. Each row is a single atomic feature; each cell states availability for that database and cites only Prisma Next tests. A cell is marked Works only when a genuine integration test (executing against PGlite / SQLite / mongodb-memory-server and asserting results) proves it for that database; unit tests do not qualify. Distinct capabilities are never bundled into one cell. Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

Draft. Opens the Prisma Next feature-support matrix as a standalone document (`scorecard.md`), feeding the Prisma 8 RC1 release project (#986). ## What this is A per-feature matrix: one row per feature, one column per database (Postgres / SQLite / MongoDB). Each cell states whether the feature is **available in Prisma Next** — not whether Prisma 7 had it: - `✅` Works — proven by a named Prisma Next test suite (cited in the evidence column). - `🟡` Untested — reachable through the Prisma Next public surface, but no proving Prisma Next test exists yet. - `🧪` Experimental — shipped but outside the stability promise (polymorphism / MTI). - `❌` Not in 8.0 — deliberately absent. - `—` n/a for that database. The **Prisma Next evidence** column points only to Prisma Next (TypeScript) test suites; Rust/engine and Prisma 7 tests are never cited. ## How the rows were derived - All features Prisma Next exposes, mined from the public surface (the four public packages, PSL, query builder, ORM, migrations, introspection, CLI, extensions). - Plus every notable Prisma 7 feature Prisma Next lacks, so absences are named rather than silently missing. ## Scope / caveats - ~326 feature rows; ~675 non-n/a verdict cells. - `🟡` cells are the RC test-porting work queue (reachable-but-unproven). - A handful of `✅`/`🟡` boundary calls are conservative (marked `🟡`) where no Prisma Next test could be confirmed; these are worth a second pass against package-level codec suites. Draft for review of orientation and completeness before wiring into the #986 dashboard.  ## Summary by CodeRabbit * **Documentation** * Added a new documentation landing page for the “Prisma Next — Feature-Support Matrix,” including coverage totals, legends, and a guided structure for migrations topics. * Introduced detailed Prisma Next scorecard pages spanning targets & connections, schema language, query builder, ORM client, relations, filtering, ordering & pagination, aggregation, nested writes & atomic ops, raw & typed SQL, transactions, migrations, introspection, CLI commands, extensions, and observability/lifecycle. * Standardized status legends and added evidence references per database to clarify tested, untested, experimental, unavailable, and non-applicable features.  --------- Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

…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>

…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>

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>

@db

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>

@db

…eze list TML-3055 subsumes the @db.-removal entry: mixins replace presets and type aliases, type constructors replace @db.* attributes. Hash text form (sha256: prefix) freezes at RC alongside the artifacts that carry it, so the prefix drops now. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

…rals The tagged backtick fence is the accepted design for extension-owned text in PSL but the parser has no tagged-literal node yet; without it the plain quoted-string spelling freezes as the API at RC. Grammar work coordinates with the mixins project (TML-3055). Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

Raw SQL default expressions move to ADR 129 tagged literals instead of quoted strings inside @dbgenerated(); touches the target default normalizers, mutation defaults, and contract infer default mapping. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

…RC task A date column read through .include() fails at runtime until the type-constructor work pins the postgres Date type to the pg/date@1 codec TML-3037 shipped unbound. That breaks the RC bar (everything we ship works), so the pin is now an explicit line item riding the mixins slice rather than an implicit consequence of it. Refs: TML-3037 Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

TML-3054 is in flight; its fix gates the July 24 matrix-verdict freeze — DateTime through include() throwing and numeric/BigInt precision loss are the hardest "everything we ship works" breakers on the list. Refs: TML-3054 Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

… TML-3060 project TML-3054 was a duplicate of the Codec JSON projections plan and is cancelled in its favor; the RC gate is the lossless-projection hard cut (TML-3063) landing before the July 24 matrix-verdict freeze. Refs: TML-3060 Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

…, kanban lanes No timeline beyond the ship date: five work lanes flow as fast as they clear. Launch communications planned separately and excluded. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

Six release requirements up front, each expanding into self-contained collapsible tasks written for a reader with no project context. No internal timeline; work flows through the sections and ships when the critical path clears. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

Section 1 lists the concrete correctness defects (bytes-as-hex, type/runtime mismatches, the six open polymorphism bugs by ticket). Section 2 gains the directional-relation-syntax project and marks the type-constructor work in flight. Error-code format is decided (dotted namespace codes, consolidation in review). Scoreboard section names the capabilities still landing before the July 24 verdict freeze; editor-support work added to section 6. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

Was a trailing sentence in the tagged-fences block; now scannable on its own, with the dependency (fences land first) and the reach beyond the parser (default handling, introspection emitting fences) stated. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

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

Self-contained HTML rendering of the release roadmap: the six release requirements with owners, task and scoreboard progress bars, and collapsible plain-English task detail. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>

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

wmadden-electric requested a review from a team as a code owner July 15, 2026 17:46

SevInf mentioned this pull request Jul 16, 2026

docs: Prisma Next feature-support matrix (scorecard) #1000

Merged

wmadden-electric mentioned this pull request Jul 21, 2026

tml-3059: deduplicate migration contracts into a content-addressed migrations/snapshots/ store #1018

Merged

wmadden-electric mentioned this pull request Jul 21, 2026

docs(prisma-8-rc1): public "Roadmap to Prisma 8 RC1" page #1020

Closed

wmadden approved these changes Jul 22, 2026

View reviewed changes

wmadden added this pull request to the merge queue Jul 22, 2026

wmadden-electric removed this pull request from the merge queue due to a manual request Jul 22, 2026

wmadden-electric added this pull request to the merge queue Jul 22, 2026

github-merge-queue Bot removed this pull request from the merge queue due to invalid changes in the merge commit Jul 22, 2026

wmadden-electric added 10 commits July 22, 2026 11:18

docs(drive): fixture invokes CLIs by unambiguous names, runs per pack…

3ee25b3

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

wmadden-electric added 11 commits July 22, 2026 11:18

docs(drive): roadmap gains owners, task counts, scoreboard summary, t…

2ea004d

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

docs(prisma-8-rc1): per-requirement progress bars on the roadmap page

d55bc4e

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

wmadden force-pushed the project/prisma-8-rc1 branch from ea8195d to d55bc4e Compare July 22, 2026 09:18

wmadden enabled auto-merge July 22, 2026 09:18

wmadden added this pull request to the merge queue Jul 22, 2026

Merged via the queue into main with commit 8875a6d Jul 22, 2026
21 checks passed

wmadden deleted the project/prisma-8-rc1 branch July 22, 2026 09:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

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

wmadden-electric commented Jul 15, 2026

Uh oh!

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading

Review skipped

Uh oh!

github-actions Bot commented Jul 15, 2026 •

edited

Loading

Uh oh!

pkg-pr-new Bot commented Jul 15, 2026 •

edited

Loading

Uh oh!

wmadden-electric commented Jul 21, 2026

Uh oh!

wmadden-electric commented Jul 21, 2026

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

wmadden-electric commented Jul 15, 2026

What this is

What's in it

Tracking

Uh oh!

coderabbitai Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

github-actions Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

size-limit report 📦

Uh oh!

pkg-pr-new Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

wmadden-electric commented Jul 21, 2026

Uh oh!

wmadden-electric commented Jul 21, 2026

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading

github-actions Bot commented Jul 15, 2026 •

edited

Loading

pkg-pr-new Bot commented Jul 15, 2026 •

edited

Loading