[dependabot]

Bumps the prisma group with 4 updates in the / directory: @prisma/orm-postgres, @prisma/orm-toolchain, prisma and @prisma/orm-extension-pgvector.

Updates @prisma/orm-postgres from 8.0.0-rc.18 to 8.0.0-rc.20

Release notes

Sourced from @​prisma/orm-postgres's releases.

v8.0.0-rc.20

ORM commands run on @prisma/cli-engine 0.9.0, so a piped command prints tab-separated data lines and JSON needs --json. A type alias in PSL can set @default, @onCreate and @onUpdate, and the contract stores each column's real type instead of the alias name. Postgres migrations can rename, move and remove namespaces, and can change a relation's actions or a primary key. A failed migration check now names the object it expected.

The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them.

Breaking changes

• A piped ORM command prints data lines, not JSON, unless you pass --json. The ORM toolchain now requires @prisma/cli-engine 0.9.0, up from 0.7.0, the engine the prisma CLI ships since 8.0.0-rc.25. This engine picks the output format from flags only. When stdout is a pipe, a file, $(…), a CI log or an agent, a command used to print JSON. It now prints the human output on stderr and plain data lines on stdout. Add --json to every script, CI step or program that reads JSON from prisma contract …, prisma db …, prisma migration … or prisma orm init. A project that depends on @prisma/cli-engine itself moves to 0.9.0. Data lines are a stable interface: fields are tab-separated in a documented order, and new fields are only added at the end. For example, migration list prints space, name, from, to and operation count, one line per migration. db init, db update, db verify, db schema and migration ref delete print nothing on stdout; read their exit code, or pass --json. See piped-output-needs-json and engine-pin-moves-to-0-9-0 in the app recipe and the extension recipe. (#30835)

  Before:

  prisma migration status | jq '.envelope.result'

  After:

  prisma migration status --json | jq '.envelope.result'
  prisma migration list | cut -f2   # or read the data lines: one migration name per line

• The contract stores a column's type, not the type alias it was written with. A column typed by a types {} alias now stores the alias's codec and parameters itself, and the contract no longer has the alias in storage.types. Every contract that uses an alias gets a new storage hash. A stored contract whose columns still name an alias in typeRef no longer loads. Run the app recipe's script, which rewrites stored contracts and migration snapshots, then run prisma contract emit, then prisma db sign against every database. The database does not change. In the TypeScript builder, the types key is removed and field.namedType(...) takes only an enum: write an alias as a constant field.column(type.VarChar(64)). The Supabase extension's contract changes hash for the same reason, so sign a Supabase database too. See stored-contracts-expand-type-aliases, ts-types-key-removed and supabase-contract-expanded in the app recipe. Extension authors run the same script from the package root and re-emit the bundled contract. A contract space that registers a database type writes it under databaseTypes instead of types. ColumnTypeDescriptor.typeRef, StorageColumn.typeRef and ExecutionContext.types are removed. See stored-contracts-expand-type-aliases, types-key-is-database-types and column-type-ref-removed in the extension recipe. (#30819)

  Before:

  const types = { Embedding1536: type.pgvector.Vector(1536) } as const;
  const Post = model('Post', {
    fields: { embedding: field.namedType(types.Embedding1536).optional() },
  });
  return { types, models: { Post } };

  After:

  const Embedding1536 = field.column(type.pgvector.Vector(1536));
  const Post = model('Post', {
    fields: { embedding: Embedding1536.optional() },
  });
  return { models: { Post } };

• A SQL builder insert must include every column the database requires. In db.sql.<namespace>.<table>.insert(rows), leaving out a column that is not nullable and has no default is now a type error that names the column. Such an insert used to compile and then fail in the database. A value typed T | undefined for such a column is an error too; check it before the insert. In ORM create and upsert, a field that is not nullable, has no default and generates a value only on update, such as one with @onUpdate(...) and no @onCreate(...), is now required. See sql-builder-insert-required-columns and orm-create-on-update-only-field in the app recipe, and sql-builder-insert-required-columns in the extension recipe. (#30830)

  Before:

... (truncated)

Changelog

Sourced from @​prisma/orm-postgres's changelog.

v8.0.0-rc.20

ORM commands run on @prisma/cli-engine 0.9.0, so a piped command prints tab-separated data lines and JSON needs --json. A type alias in PSL can set @default, @onCreate and @onUpdate, and the contract stores each column's real type instead of the alias name. Postgres migrations can rename, move and remove namespaces, and can change a relation's actions or a primary key. A failed migration check now names the object it expected.

The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them.

Breaking changes

• A piped ORM command prints data lines, not JSON, unless you pass --json. The ORM toolchain now requires @prisma/cli-engine 0.9.0, up from 0.7.0, the engine the prisma CLI ships since 8.0.0-rc.25. This engine picks the output format from flags only. When stdout is a pipe, a file, $(…), a CI log or an agent, a command used to print JSON. It now prints the human output on stderr and plain data lines on stdout. Add --json to every script, CI step or program that reads JSON from prisma contract …, prisma db …, prisma migration … or prisma orm init. A project that depends on @prisma/cli-engine itself moves to 0.9.0. Data lines are a stable interface: fields are tab-separated in a documented order, and new fields are only added at the end. For example, migration list prints space, name, from, to and operation count, one line per migration. db init, db update, db verify, db schema and migration ref delete print nothing on stdout; read their exit code, or pass --json. See piped-output-needs-json and engine-pin-moves-to-0-9-0 in the app recipe and the extension recipe. (#30835)

  Before:

  prisma migration status | jq '.envelope.result'

  After:

  prisma migration status --json | jq '.envelope.result'
  prisma migration list | cut -f2   # or read the data lines: one migration name per line

• The contract stores a column's type, not the type alias it was written with. A column typed by a types {} alias now stores the alias's codec and parameters itself, and the contract no longer has the alias in storage.types. Every contract that uses an alias gets a new storage hash. A stored contract whose columns still name an alias in typeRef no longer loads. Run the app recipe's script, which rewrites stored contracts and migration snapshots, then run prisma contract emit, then prisma db sign against every database. The database does not change. In the TypeScript builder, the types key is removed and field.namedType(...) takes only an enum: write an alias as a constant field.column(type.VarChar(64)). The Supabase extension's contract changes hash for the same reason, so sign a Supabase database too. See stored-contracts-expand-type-aliases, ts-types-key-removed and supabase-contract-expanded in the app recipe. Extension authors run the same script from the package root and re-emit the bundled contract. A contract space that registers a database type writes it under databaseTypes instead of types. ColumnTypeDescriptor.typeRef, StorageColumn.typeRef and ExecutionContext.types are removed. See stored-contracts-expand-type-aliases, types-key-is-database-types and column-type-ref-removed in the extension recipe. (#30819)

  Before:

  const types = { Embedding1536: type.pgvector.Vector(1536) } as const;
  const Post = model('Post', {
    fields: { embedding: field.namedType(types.Embedding1536).optional() },
  });
  return { types, models: { Post } };

  After:

  const Embedding1536 = field.column(type.pgvector.Vector(1536));
  const Post = model('Post', {
    fields: { embedding: Embedding1536.optional() },
  });
  return { models: { Post } };

• A SQL builder insert must include every column the database requires. In db.sql.<namespace>.<table>.insert(rows), leaving out a column that is not nullable and has no default is now a type error that names the column. Such an insert used to compile and then fail in the database. A value typed T | undefined for such a column is an error too; check it before the insert. In ORM create and upsert, a field that is not nullable, has no default and generates a value only on update, such as one with @onUpdate(...) and no @onCreate(...), is now required. See sql-builder-insert-required-columns and orm-create-on-update-only-field in the app recipe, and sql-builder-insert-required-columns in the extension recipe. (#30830)

  Before:

... (truncated)

Commits

• 10b7bed chore(release): bump to 8.0.0-rc.20 (#30838)
• a5d1d96 TML-3688, TML-3411, TML-3685, TML-3687: A Supabase client shuts down like a P...
• 1e98c69 chore(release): bump to 8.0.0-rc.19 (#30821)
• 2e2b4c1 TML-3603: A transaction offers the client's query members on every SQL client...
• 0c3b8fc TML-3602: A client takes its contract as a typed value from contractFromJson,...
• dfc44c5 TML-3549: Packages contribute collection methods computed from a model (#30717)
• See full diff in compare view

Updates @prisma/orm-toolchain from 8.0.0-rc.18 to 8.0.0-rc.20

Release notes

Sourced from @​prisma/orm-toolchain's releases.

v8.0.0-rc.20

ORM commands run on @prisma/cli-engine 0.9.0, so a piped command prints tab-separated data lines and JSON needs --json. A type alias in PSL can set @default, @onCreate and @onUpdate, and the contract stores each column's real type instead of the alias name. Postgres migrations can rename, move and remove namespaces, and can change a relation's actions or a primary key. A failed migration check now names the object it expected.

The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them.

Breaking changes

• A piped ORM command prints data lines, not JSON, unless you pass --json. The ORM toolchain now requires @prisma/cli-engine 0.9.0, up from 0.7.0, the engine the prisma CLI ships since 8.0.0-rc.25. This engine picks the output format from flags only. When stdout is a pipe, a file, $(…), a CI log or an agent, a command used to print JSON. It now prints the human output on stderr and plain data lines on stdout. Add --json to every script, CI step or program that reads JSON from prisma contract …, prisma db …, prisma migration … or prisma orm init. A project that depends on @prisma/cli-engine itself moves to 0.9.0. Data lines are a stable interface: fields are tab-separated in a documented order, and new fields are only added at the end. For example, migration list prints space, name, from, to and operation count, one line per migration. db init, db update, db verify, db schema and migration ref delete print nothing on stdout; read their exit code, or pass --json. See piped-output-needs-json and engine-pin-moves-to-0-9-0 in the app recipe and the extension recipe. (#30835)

  Before:

  prisma migration status | jq '.envelope.result'

  After:

  prisma migration status --json | jq '.envelope.result'
  prisma migration list | cut -f2   # or read the data lines: one migration name per line

• The contract stores a column's type, not the type alias it was written with. A column typed by a types {} alias now stores the alias's codec and parameters itself, and the contract no longer has the alias in storage.types. Every contract that uses an alias gets a new storage hash. A stored contract whose columns still name an alias in typeRef no longer loads. Run the app recipe's script, which rewrites stored contracts and migration snapshots, then run prisma contract emit, then prisma db sign against every database. The database does not change. In the TypeScript builder, the types key is removed and field.namedType(...) takes only an enum: write an alias as a constant field.column(type.VarChar(64)). The Supabase extension's contract changes hash for the same reason, so sign a Supabase database too. See stored-contracts-expand-type-aliases, ts-types-key-removed and supabase-contract-expanded in the app recipe. Extension authors run the same script from the package root and re-emit the bundled contract. A contract space that registers a database type writes it under databaseTypes instead of types. ColumnTypeDescriptor.typeRef, StorageColumn.typeRef and ExecutionContext.types are removed. See stored-contracts-expand-type-aliases, types-key-is-database-types and column-type-ref-removed in the extension recipe. (#30819)

  Before:

  const types = { Embedding1536: type.pgvector.Vector(1536) } as const;
  const Post = model('Post', {
    fields: { embedding: field.namedType(types.Embedding1536).optional() },
  });
  return { types, models: { Post } };

  After:

  const Embedding1536 = field.column(type.pgvector.Vector(1536));
  const Post = model('Post', {
    fields: { embedding: Embedding1536.optional() },
  });
  return { models: { Post } };

• A SQL builder insert must include every column the database requires. In db.sql.<namespace>.<table>.insert(rows), leaving out a column that is not nullable and has no default is now a type error that names the column. Such an insert used to compile and then fail in the database. A value typed T | undefined for such a column is an error too; check it before the insert. In ORM create and upsert, a field that is not nullable, has no default and generates a value only on update, such as one with @onUpdate(...) and no @onCreate(...), is now required. See sql-builder-insert-required-columns and orm-create-on-update-only-field in the app recipe, and sql-builder-insert-required-columns in the extension recipe. (#30830)

  Before:

... (truncated)

Changelog

Sourced from @​prisma/orm-toolchain's changelog.

v8.0.0-rc.20

ORM commands run on @prisma/cli-engine 0.9.0, so a piped command prints tab-separated data lines and JSON needs --json. A type alias in PSL can set @default, @onCreate and @onUpdate, and the contract stores each column's real type instead of the alias name. Postgres migrations can rename, move and remove namespaces, and can change a relation's actions or a primary key. A failed migration check now names the object it expected.

The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them.

Breaking changes

• A piped ORM command prints data lines, not JSON, unless you pass --json. The ORM toolchain now requires @prisma/cli-engine 0.9.0, up from 0.7.0, the engine the prisma CLI ships since 8.0.0-rc.25. This engine picks the output format from flags only. When stdout is a pipe, a file, $(…), a CI log or an agent, a command used to print JSON. It now prints the human output on stderr and plain data lines on stdout. Add --json to every script, CI step or program that reads JSON from prisma contract …, prisma db …, prisma migration … or prisma orm init. A project that depends on @prisma/cli-engine itself moves to 0.9.0. Data lines are a stable interface: fields are tab-separated in a documented order, and new fields are only added at the end. For example, migration list prints space, name, from, to and operation count, one line per migration. db init, db update, db verify, db schema and migration ref delete print nothing on stdout; read their exit code, or pass --json. See piped-output-needs-json and engine-pin-moves-to-0-9-0 in the app recipe and the extension recipe. (#30835)

  Before:

  prisma migration status | jq '.envelope.result'

  After:

  prisma migration status --json | jq '.envelope.result'
  prisma migration list | cut -f2   # or read the data lines: one migration name per line

• The contract stores a column's type, not the type alias it was written with. A column typed by a types {} alias now stores the alias's codec and parameters itself, and the contract no longer has the alias in storage.types. Every contract that uses an alias gets a new storage hash. A stored contract whose columns still name an alias in typeRef no longer loads. Run the app recipe's script, which rewrites stored contracts and migration snapshots, then run prisma contract emit, then prisma db sign against every database. The database does not change. In the TypeScript builder, the types key is removed and field.namedType(...) takes only an enum: write an alias as a constant field.column(type.VarChar(64)). The Supabase extension's contract changes hash for the same reason, so sign a Supabase database too. See stored-contracts-expand-type-aliases, ts-types-key-removed and supabase-contract-expanded in the app recipe. Extension authors run the same script from the package root and re-emit the bundled contract. A contract space that registers a database type writes it under databaseTypes instead of types. ColumnTypeDescriptor.typeRef, StorageColumn.typeRef and ExecutionContext.types are removed. See stored-contracts-expand-type-aliases, types-key-is-database-types and column-type-ref-removed in the extension recipe. (#30819)

  Before:

  const types = { Embedding1536: type.pgvector.Vector(1536) } as const;
  const Post = model('Post', {
    fields: { embedding: field.namedType(types.Embedding1536).optional() },
  });
  return { types, models: { Post } };

  After:

  const Embedding1536 = field.column(type.pgvector.Vector(1536));
  const Post = model('Post', {
    fields: { embedding: Embedding1536.optional() },
  });
  return { models: { Post } };

• A SQL builder insert must include every column the database requires. In db.sql.<namespace>.<table>.insert(rows), leaving out a column that is not nullable and has no default is now a type error that names the column. Such an insert used to compile and then fail in the database. A value typed T | undefined for such a column is an error too; check it before the insert. In ORM create and upsert, a field that is not nullable, has no default and generates a value only on update, such as one with @onUpdate(...) and no @onCreate(...), is now required. See sql-builder-insert-required-columns and orm-create-on-update-only-field in the app recipe, and sql-builder-insert-required-columns in the extension recipe. (#30830)

  Before:

... (truncated)

Commits

• 10b7bed chore(release): bump to 8.0.0-rc.20 (#30838)
• 9975b28 TML-3716: ORM commands run on CLI engine 0.9.0, and a piped command prints pl...
• 1e98c69 chore(release): bump to 8.0.0-rc.19 (#30821)
• See full diff in compare view

Updates prisma from 8.0.0-rc.23 to 8.0.0-rc.27

Release notes

Sourced from prisma's releases.

v8.0.0-rc.27

What's Changed

• Follow the products' released versions: @​prisma/composer-cli 0.33.0 -> 0.34.0; @​prisma/composer 0.33.0 -> 0.34.0 by @​prisma-bot in prisma/prisma-cli#366
• Bump to version 8.0.0-rc.27 by @​wmadden-electric in prisma/prisma-cli#367

Full Changelog: prisma/prisma-cli@v8.0.0-rc.26...v8.0.0-rc.27

v8.0.0-rc.26

What's Changed

• Follow the products' released versions: @​prisma/orm-toolchain 8.0.0-rc.19 -> 8.0.0-rc.20 by @​prisma-bot in prisma/prisma-cli#364
• Bump to version 8.0.0-rc.26 by @​wmadden-electric in prisma/prisma-cli#365

Full Changelog: prisma/prisma-cli@v8.0.0-rc.25...v8.0.0-rc.26

v8.0.0-rc.25

What's Changed

• Follow the products' released versions: @​prisma/orm-toolchain 8.0.0-rc.18 -> 8.0.0-rc.19 by @​prisma-bot in prisma/prisma-cli#359
• Follow the products' released versions: @​prisma/composer-cli 0.32.0 -> 0.33.0; @​prisma/composer 0.32.0 -> 0.33.0 by @​prisma-bot in prisma/prisma-cli#361
• Bump to version 8.0.0-rc.25 by @​wmadden-electric in prisma/prisma-cli#362

Full Changelog: prisma/prisma-cli@v8.0.0-rc.24...v8.0.0-rc.25

v8.0.0-rc.24

What's Changed

• feat(engine): a command can also have subcommands, so prisma dev and prisma dev url can coexist by @​wmadden-electric in prisma/prisma-cli#349
• feat!: piping a prisma command gives its plain data; JSON needs --json by @​wmadden-electric in prisma/prisma-cli#353
• docs(readme): name Prisma Postgres and Prisma Compute in the npm READMEs by @​gregory-boch-prisma in prisma/prisma-cli#348
• feat: add prisma dev url, prisma dev stop and prisma emulator list (Composer 0.31.0) by @​wmadden-electric in prisma/prisma-cli#355
• Follow the products' released versions: @​prisma/composer-cli 0.31.0 -> 0.32.0; @​prisma/composer 0.31.0 -> 0.32.0 by @​prisma-bot in prisma/prisma-cli#357
• Follow Composer 0.32.0, and list the DEV error codes so their docs links resolve by @​wmadden-electric in prisma/prisma-cli#356
• Bump to version 8.0.0-rc.24 by @​wmadden-electric in prisma/prisma-cli#358

Full Changelog: prisma/prisma-cli@v8.0.0-rc.23...v8.0.0-rc.24

Commits

• 325e33b Bump to version 8.0.0-rc.27 (#367)
• 21d970f Follow the products' released versions: @​prisma/composer-cli 0.33.0 -> 0.34.0...
• c188f3b Bump to version 8.0.0-rc.26 (#365)
• 9292b20 Follow the products' released versions: @​prisma/orm-toolchain 8.0.0-rc.19 -> ...
• 1d84b9a Bump to version 8.0.0-rc.25 (#362)
• 3debe80 Follow the products' released versions: @​prisma/composer-cli 0.32.0 -> 0.33.0...
• 9d3bc26 Follow the products' released versions: @​prisma/orm-toolchain 8.0.0-rc.18 -> ...
• 7d09abd Bump to version 8.0.0-rc.24 (#358)
• a80f6b0 Follow the products' released versions: @​prisma/composer-cli 0.31.0 -> 0.32.0...
• 52c518f feat: add prisma dev url, prisma dev stop and prisma emulator list (Composer ...
• Additional commits viewable in compare view

Updates @prisma/orm-extension-pgvector from 8.0.0-rc.18 to 8.0.0-rc.20

Release notes

Sourced from @​prisma/orm-extension-pgvector's releases.

v8.0.0-rc.20

ORM commands run on @prisma/cli-engine 0.9.0, so a piped command prints tab-separated data lines and JSON needs --json. A type alias in PSL can set @default, @onCreate and @onUpdate, and the contract stores each column's real type instead of the alias name. Postgres migrations can rename, move and remove namespaces, and can change a relation's actions or a primary key. A failed migration check now names the object it expected.

The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them.

Breaking changes

• A piped ORM command prints data lines, not JSON, unless you pass --json. The ORM toolchain now requires @prisma/cli-engine 0.9.0, up from 0.7.0, the engine the prisma CLI ships since 8.0.0-rc.25. This engine picks the output format from flags only. When stdout is a pipe, a file, $(…), a CI log or an agent, a command used to print JSON. It now prints the human output on stderr and plain data lines on stdout. Add --json to every script, CI step or program that reads JSON from prisma contract …, prisma db …, prisma migration … or prisma orm init. A project that depends on @prisma/cli-engine itself moves to 0.9.0. Data lines are a stable interface: fields are tab-separated in a documented order, and new fields are only added at the end. For example, migration list prints space, name, from, to and operation count, one line per migration. db init, db update, db verify, db schema and migration ref delete print nothing on stdout; read their exit code, or pass --json. See piped-output-needs-json and engine-pin-moves-to-0-9-0 in the app recipe and the extension recipe. (#30835)

  Before:

  prisma migration status | jq '.envelope.result'

  After:

  prisma migration status --json | jq '.envelope.result'
  prisma migration list | cut -f2   # or read the data lines: one migration name per line

• The contract stores a column's type, not the type alias it was written with. A column typed by a types {} alias now stores the alias's codec and parameters itself, and the contract no longer has the alias in storage.types. Every contract that uses an alias gets a new storage hash. A stored contract whose columns still name an alias in typeRef no longer loads. Run the app recipe's script, which rewrites stored contracts and migration snapshots, then run prisma contract emit, then prisma db sign against every database. The database does not change. In the TypeScript builder, the types key is removed and field.namedType(...) takes only an enum: write an alias as a constant field.column(type.VarChar(64)). The Supabase extension's contract changes hash for the same reason, so sign a Supabase database too. See stored-contracts-expand-type-aliases, ts-types-key-removed and supabase-contract-expanded in the app recipe. Extension authors run the same script from the package root and re-emit the bundled contract. A contract space that registers a database type writes it under databaseTypes instead of types. ColumnTypeDescriptor.typeRef, StorageColumn.typeRef and ExecutionContext.types are removed. See stored-contracts-expand-type-aliases, types-key-is-database-types and column-type-ref-removed in the extension recipe. (#30819)

  Before:

  const types = { Embedding1536: type.pgvector.Vector(1536) } as const;
  const Post = model('Post', {
    fields: { embedding: field.namedType(types.Embedding1536).optional() },
  });
  return { types, models: { Post } };

  After:

  const Embedding1536 = field.column(type.pgvector.Vector(1536));
  const Post = model('Post', {
    fields: { embedding: Embedding1536.optional() },
  });
  return { models: { Post } };

• A SQL builder insert must include every column the database requires. In db.sql.<namespace>.<table>.insert(rows), leaving out a column that is not nullable and has no default is now a type error that names the column. Such an insert used to compile and then fail in the database. A value typed T | undefined for such a column is an error too; check it before the insert. In ORM create and upsert, a field that is not nullable, has no default and generates a value only on update, such as one with @onUpdate(...) and no @onCreate(...), is now required. See sql-builder-insert-required-columns and orm-create-on-update-only-field in the app recipe, and sql-builder-insert-required-columns in the extension recipe. (#30830)

  Before:

... (truncated)

Changelog

Sourced from @​prisma/orm-extension-pgvector's changelog.

v8.0.0-rc.20

ORM commands run on @prisma/cli-engine 0.9.0, so a piped command prints tab-separated data lines and JSON needs --json. A type alias in PSL can set @default, @onCreate and @onUpdate, and the contract stores each column's real type instead of the alias name. Postgres migrations can rename, move and remove namespaces, and can change a relation's actions or a primary key. A failed migration check now names the object it expected.

The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them.

Breaking changes

• A piped ORM command prints data lines, not JSON, unless you pass --json. The ORM toolchain now requires @prisma/cli-engine 0.9.0, up from 0.7.0, the engine the prisma CLI ships since 8.0.0-rc.25. This engine picks the output format from flags only. When stdout is a pipe, a file, $(…), a CI log or an agent, a command used to print JSON. It now prints the human output on stderr and plain data lines on stdout. Add --json to every script, CI step or program that reads JSON from prisma contract …, prisma db …, prisma migration … or prisma orm init. A project that depends on @prisma/cli-engine itself moves to 0.9.0. Data lines are a stable interface: fields are tab-separated in a documented order, and new fields are only added at the end. For example, migration list prints space, name, from, to and operation count, one line per migration. db init, db update, db verify, db schema and migration ref delete print nothing on stdout; read their exit code, or pass --json. See piped-output-needs-json and engine-pin-moves-to-0-9-0 in the app recipe and the extension recipe. (#30835)

  Before:

  prisma migration status | jq '.envelope.result'

  After:

  prisma migration status --json | jq '.envelope.result'
  prisma migration list | cut -f2   # or read the data lines: one migration name per line

• The contract stores a column's type, not the type alias it was written with. A column typed by a types {} alias now stores the alias's codec and parameters itself, and the contract no longer has the alias in storage.types. Every contract that uses an alias gets a new storage hash. A stored contract whose columns still name an alias in typeRef no longer loads. Run the app recipe's script, which rewrites stored contracts and migration snapshots, then run prisma contract emit, then prisma db sign against every database. The database does not change. In the TypeScript builder, the types key is removed and field.namedType(...) takes only an enum: write an alias as a constant field.column(type.VarChar(64)). The Supabase extension's contract changes hash for the same reason, so sign a Supabase database too. See stored-contracts-expand-type-aliases, ts-types-key-removed and supabase-contract-expanded in the app recipe. Extension authors run the same script from the package root and re-emit the bundled contract. A contract space that registers a database type writes it under databaseTypes instead of types. ColumnTypeDescriptor.typeRef, StorageColumn.typeRef and ExecutionContext.types are removed. See stored-contracts-expand-type-aliases, types-key-is-database-types and column-type-ref-removed in the extension recipe. (#30819)

  Before:

  const types = { Embedding1536: type.pgvector.Vector(1536) } as const;
  const Post = model('Post', {
    fields: { embedding: field.namedType(types.Embedding1536).optional() },
  });
  return { types, models: { Post } };

  After:

  const Embedding1536 = field.column(type.pgvector.Vector(1536));
  const Post = model('Post', {
    fields: { embedding: Embedding1536.optional() },
  });
  return { models: { Post } };

• A SQL builder insert must include every column the database requires. In db.sql.<namespace>.<table>.insert(rows), leaving out a column that is not nullable and has no default is now a type error that names the column. Such an insert used to compile and then fail in the database. A value typed T | undefined for such a column is an error too; check it before the insert. In ORM create and upsert, a field that is not nullable, has no default and generates a value only on update, such as one with @onUpdate(...) and no @onCreate(...), is now required. See sql-builder-insert-required-columns and orm-create-on-update-only-field in the app recipe, and sql-builder-insert-required-columns in the extension recipe. (#30830)

  Before:

... (truncated)

Commits

• 10b7bed chore(release): bump to 8.0.0-rc.20 (#30838)
• 1e98c69 chore(release): bump to 8.0.0-rc.19 (#30821)
• See full diff in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
stack-docs	Error		Oct 29, 2026 1:22am UTC

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3c45828

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR