build(deps): bump the prisma group across 1 directory with 3 updates

[dependabot]

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

Updates @prisma/orm-postgres from 8.0.0-rc.13 to 8.0.0-rc.14

Release notes

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

v8.0.0-rc.14

In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash no longer depends on how the default was written. The Mongo ORM passes every value it writes, reads or filters on through its field's codec. The Postgres CLI commands now work with date and time defaults on Node 24, which has no Temporal.

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

Breaking changes

• Serverless connect() returns a connection, not a Runtime. postgresServerless(...).connect({ url }) from @prisma/orm-postgres/serverless now returns a connection with the members of a postgres() client except connect. Replace runtime.query(plan) with db.runtime().query(plan), and pass db.runtime() wherever the connect() result was used as a runtime. connect() now opens the database connection before it returns, and rejects with DRIVER.CONNECTION_FAILED when the database cannot be reached. Reads no longer go through a server-side cursor by default. The cursor option is now PostgresCursorOptions, { batchSize?: number }, so delete cursor: { disabled: true }. See serverless-connect-returns-connection and serverless-cursor-default-off in the app recipe. (#30482)

  Before:

  await using runtime = await db.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await runtime.query(db.sql.public.user.select('id').build());

  After:

  await using db = await postgres.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await db.runtime().query(db.sql.public.user.select('id').build());

• A date or time default is stored in its type's canonical form. On Postgres and SQLite, prisma contract emit stores each date or time default as one text for each value: @default("2024-01-01T01:00:00+01:00") on a DateTime column is stored as "2024-01-01T00:00:00Z". TypeScript contracts store the same text. A default that was not already in that form gets a new storage hash. The database does not change: re-emit, then run prisma db sign, or record an empty migration with prisma migration new. contract emit now refuses a default that the column's type does not hold, such as an offset on a Timestamp column, with PSL_INVALID_DEFAULT_LITERAL. See date-time-default-stored-in-canonical-form, date-time-default-refused-text and date-time-ts-default-stored-in-canonical-form in the app recipe. (#30532)

  Before, accepted and stored as written:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00Z")
  }

  After, because a Timestamp column holds no offset:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00")
  }

• The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type, of a fraction or an out-of-range number to an Int32 field, of a value outside the field's enum, or of null to a required field now fails with RUNTIME.ENCODE_FAILED naming the field. Before, some of these were stored as given. A filter expression passed to where() is encoded the same way, so a filter on an Int64 field needs a bigint. create() and createAll() return the document as stored, decoded like a read, and a nullable field missing from a stored document reads as null, not undefined. The query builder's match() still sends values as given. See the mongo-* entries in the app recipe. (#30519)

  Before:

  db.orm.posts.where(MongoFieldFilter.gt('views', Long.fromNumber(5)))

... (truncated)

Changelog

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

v8.0.0-rc.14

In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash no longer depends on how the default was written. The Mongo ORM passes every value it writes, reads or filters on through its field's codec. The Postgres CLI commands now work with date and time defaults on Node 24, which has no Temporal.

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

Breaking changes

• Serverless connect() returns a connection, not a Runtime. postgresServerless(...).connect({ url }) from @prisma/orm-postgres/serverless now returns a connection with the members of a postgres() client except connect. Replace runtime.query(plan) with db.runtime().query(plan), and pass db.runtime() wherever the connect() result was used as a runtime. connect() now opens the database connection before it returns, and rejects with DRIVER.CONNECTION_FAILED when the database cannot be reached. Reads no longer go through a server-side cursor by default. The cursor option is now PostgresCursorOptions, { batchSize?: number }, so delete cursor: { disabled: true }. See serverless-connect-returns-connection and serverless-cursor-default-off in the app recipe. (#30482)

  Before:

  await using runtime = await db.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await runtime.query(db.sql.public.user.select('id').build());

  After:

  await using db = await postgres.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await db.runtime().query(db.sql.public.user.select('id').build());

• A date or time default is stored in its type's canonical form. On Postgres and SQLite, prisma contract emit stores each date or time default as one text for each value: @default("2024-01-01T01:00:00+01:00") on a DateTime column is stored as "2024-01-01T00:00:00Z". TypeScript contracts store the same text. A default that was not already in that form gets a new storage hash. The database does not change: re-emit, then run prisma db sign, or record an empty migration with prisma migration new. contract emit now refuses a default that the column's type does not hold, such as an offset on a Timestamp column, with PSL_INVALID_DEFAULT_LITERAL. See date-time-default-stored-in-canonical-form, date-time-default-refused-text and date-time-ts-default-stored-in-canonical-form in the app recipe. (#30532)

  Before, accepted and stored as written:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00Z")
  }

  After, because a Timestamp column holds no offset:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00")
  }

• The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type, of a fraction or an out-of-range number to an Int32 field, of a value outside the field's enum, or of null to a required field now fails with RUNTIME.ENCODE_FAILED naming the field. Before, some of these were stored as given. A filter expression passed to where() is encoded the same way, so a filter on an Int64 field needs a bigint. create() and createAll() return the document as stored, decoded like a read, and a nullable field missing from a stored document reads as null, not undefined. The query builder's match() still sends values as given. See the mongo-* entries in the app recipe. (#30519)

  Before:

  db.orm.posts.where(MongoFieldFilter.gt('views', Long.fromNumber(5)))

... (truncated)

Commits

• 266c45e chore(release): bump to 8.0.0-rc.14 (#30541)
• 759fa14 TML-3250: The CLI handles Postgres date and time defaults on Node 24, which h...
• 35f68b2 TML-2398: serverless connect() returns a connection with db.orm, db.transacti...
• See full diff in compare view

Updates @prisma/orm-toolchain from 8.0.0-rc.13 to 8.0.0-rc.14

Release notes

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

v8.0.0-rc.14

In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash no longer depends on how the default was written. The Mongo ORM passes every value it writes, reads or filters on through its field's codec. The Postgres CLI commands now work with date and time defaults on Node 24, which has no Temporal.

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

Breaking changes

• Serverless connect() returns a connection, not a Runtime. postgresServerless(...).connect({ url }) from @prisma/orm-postgres/serverless now returns a connection with the members of a postgres() client except connect. Replace runtime.query(plan) with db.runtime().query(plan), and pass db.runtime() wherever the connect() result was used as a runtime. connect() now opens the database connection before it returns, and rejects with DRIVER.CONNECTION_FAILED when the database cannot be reached. Reads no longer go through a server-side cursor by default. The cursor option is now PostgresCursorOptions, { batchSize?: number }, so delete cursor: { disabled: true }. See serverless-connect-returns-connection and serverless-cursor-default-off in the app recipe. (#30482)

  Before:

  await using runtime = await db.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await runtime.query(db.sql.public.user.select('id').build());

  After:

  await using db = await postgres.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await db.runtime().query(db.sql.public.user.select('id').build());

• A date or time default is stored in its type's canonical form. On Postgres and SQLite, prisma contract emit stores each date or time default as one text for each value: @default("2024-01-01T01:00:00+01:00") on a DateTime column is stored as "2024-01-01T00:00:00Z". TypeScript contracts store the same text. A default that was not already in that form gets a new storage hash. The database does not change: re-emit, then run prisma db sign, or record an empty migration with prisma migration new. contract emit now refuses a default that the column's type does not hold, such as an offset on a Timestamp column, with PSL_INVALID_DEFAULT_LITERAL. See date-time-default-stored-in-canonical-form, date-time-default-refused-text and date-time-ts-default-stored-in-canonical-form in the app recipe. (#30532)

  Before, accepted and stored as written:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00Z")
  }

  After, because a Timestamp column holds no offset:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00")
  }

• The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type, of a fraction or an out-of-range number to an Int32 field, of a value outside the field's enum, or of null to a required field now fails with RUNTIME.ENCODE_FAILED naming the field. Before, some of these were stored as given. A filter expression passed to where() is encoded the same way, so a filter on an Int64 field needs a bigint. create() and createAll() return the document as stored, decoded like a read, and a nullable field missing from a stored document reads as null, not undefined. The query builder's match() still sends values as given. See the mongo-* entries in the app recipe. (#30519)

  Before:

  db.orm.posts.where(MongoFieldFilter.gt('views', Long.fromNumber(5)))

... (truncated)

Changelog

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

v8.0.0-rc.14

In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash no longer depends on how the default was written. The Mongo ORM passes every value it writes, reads or filters on through its field's codec. The Postgres CLI commands now work with date and time defaults on Node 24, which has no Temporal.

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

Breaking changes

• Serverless connect() returns a connection, not a Runtime. postgresServerless(...).connect({ url }) from @prisma/orm-postgres/serverless now returns a connection with the members of a postgres() client except connect. Replace runtime.query(plan) with db.runtime().query(plan), and pass db.runtime() wherever the connect() result was used as a runtime. connect() now opens the database connection before it returns, and rejects with DRIVER.CONNECTION_FAILED when the database cannot be reached. Reads no longer go through a server-side cursor by default. The cursor option is now PostgresCursorOptions, { batchSize?: number }, so delete cursor: { disabled: true }. See serverless-connect-returns-connection and serverless-cursor-default-off in the app recipe. (#30482)

  Before:

  await using runtime = await db.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await runtime.query(db.sql.public.user.select('id').build());

  After:

  await using db = await postgres.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await db.runtime().query(db.sql.public.user.select('id').build());

• A date or time default is stored in its type's canonical form. On Postgres and SQLite, prisma contract emit stores each date or time default as one text for each value: @default("2024-01-01T01:00:00+01:00") on a DateTime column is stored as "2024-01-01T00:00:00Z". TypeScript contracts store the same text. A default that was not already in that form gets a new storage hash. The database does not change: re-emit, then run prisma db sign, or record an empty migration with prisma migration new. contract emit now refuses a default that the column's type does not hold, such as an offset on a Timestamp column, with PSL_INVALID_DEFAULT_LITERAL. See date-time-default-stored-in-canonical-form, date-time-default-refused-text and date-time-ts-default-stored-in-canonical-form in the app recipe. (#30532)

  Before, accepted and stored as written:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00Z")
  }

  After, because a Timestamp column holds no offset:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00")
  }

• The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type, of a fraction or an out-of-range number to an Int32 field, of a value outside the field's enum, or of null to a required field now fails with RUNTIME.ENCODE_FAILED naming the field. Before, some of these were stored as given. A filter expression passed to where() is encoded the same way, so a filter on an Int64 field needs a bigint. create() and createAll() return the document as stored, decoded like a read, and a nullable field missing from a stored document reads as null, not undefined. The query builder's match() still sends values as given. See the mongo-* entries in the app recipe. (#30519)

  Before:

  db.orm.posts.where(MongoFieldFilter.gt('views', Long.fromNumber(5)))

... (truncated)

Commits

• 266c45e chore(release): bump to 8.0.0-rc.14 (#30541)
• 64f6c3e fix(deps): build orm-toolchain against @​prisma/cli-engine 0.6.2, which prints...
• See full diff in compare view

Updates @prisma/orm-extension-pgvector from 8.0.0-rc.13 to 8.0.0-rc.14

Release notes

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

v8.0.0-rc.14

In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash no longer depends on how the default was written. The Mongo ORM passes every value it writes, reads or filters on through its field's codec. The Postgres CLI commands now work with date and time defaults on Node 24, which has no Temporal.

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

Breaking changes

• Serverless connect() returns a connection, not a Runtime. postgresServerless(...).connect({ url }) from @prisma/orm-postgres/serverless now returns a connection with the members of a postgres() client except connect. Replace runtime.query(plan) with db.runtime().query(plan), and pass db.runtime() wherever the connect() result was used as a runtime. connect() now opens the database connection before it returns, and rejects with DRIVER.CONNECTION_FAILED when the database cannot be reached. Reads no longer go through a server-side cursor by default. The cursor option is now PostgresCursorOptions, { batchSize?: number }, so delete cursor: { disabled: true }. See serverless-connect-returns-connection and serverless-cursor-default-off in the app recipe. (#30482)

  Before:

  await using runtime = await db.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await runtime.query(db.sql.public.user.select('id').build());

  After:

  await using db = await postgres.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await db.runtime().query(db.sql.public.user.select('id').build());

• A date or time default is stored in its type's canonical form. On Postgres and SQLite, prisma contract emit stores each date or time default as one text for each value: @default("2024-01-01T01:00:00+01:00") on a DateTime column is stored as "2024-01-01T00:00:00Z". TypeScript contracts store the same text. A default that was not already in that form gets a new storage hash. The database does not change: re-emit, then run prisma db sign, or record an empty migration with prisma migration new. contract emit now refuses a default that the column's type does not hold, such as an offset on a Timestamp column, with PSL_INVALID_DEFAULT_LITERAL. See date-time-default-stored-in-canonical-form, date-time-default-refused-text and date-time-ts-default-stored-in-canonical-form in the app recipe. (#30532)

  Before, accepted and stored as written:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00Z")
  }

  After, because a Timestamp column holds no offset:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00")
  }

• The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type, of a fraction or an out-of-range number to an Int32 field, of a value outside the field's enum, or of null to a required field now fails with RUNTIME.ENCODE_FAILED naming the field. Before, some of these were stored as given. A filter expression passed to where() is encoded the same way, so a filter on an Int64 field needs a bigint. create() and createAll() return the document as stored, decoded like a read, and a nullable field missing from a stored document reads as null, not undefined. The query builder's match() still sends values as given. See the mongo-* entries in the app recipe. (#30519)

  Before:

  db.orm.posts.where(MongoFieldFilter.gt('views', Long.fromNumber(5)))

... (truncated)

Changelog

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

v8.0.0-rc.14

In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash no longer depends on how the default was written. The Mongo ORM passes every value it writes, reads or filters on through its field's codec. The Postgres CLI commands now work with date and time defaults on Node 24, which has no Temporal.

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

Breaking changes

• Serverless connect() returns a connection, not a Runtime. postgresServerless(...).connect({ url }) from @prisma/orm-postgres/serverless now returns a connection with the members of a postgres() client except connect. Replace runtime.query(plan) with db.runtime().query(plan), and pass db.runtime() wherever the connect() result was used as a runtime. connect() now opens the database connection before it returns, and rejects with DRIVER.CONNECTION_FAILED when the database cannot be reached. Reads no longer go through a server-side cursor by default. The cursor option is now PostgresCursorOptions, { batchSize?: number }, so delete cursor: { disabled: true }. See serverless-connect-returns-connection and serverless-cursor-default-off in the app recipe. (#30482)

  Before:

  await using runtime = await db.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await runtime.query(db.sql.public.user.select('id').build());

  After:

  await using db = await postgres.connect({ url: env.HYPERDRIVE.connectionString });
  const rows = await db.runtime().query(db.sql.public.user.select('id').build());

• A date or time default is stored in its type's canonical form. On Postgres and SQLite, prisma contract emit stores each date or time default as one text for each value: @default("2024-01-01T01:00:00+01:00") on a DateTime column is stored as "2024-01-01T00:00:00Z". TypeScript contracts store the same text. A default that was not already in that form gets a new storage hash. The database does not change: re-emit, then run prisma db sign, or record an empty migration with prisma migration new. contract emit now refuses a default that the column's type does not hold, such as an offset on a Timestamp column, with PSL_INVALID_DEFAULT_LITERAL. See date-time-default-stored-in-canonical-form, date-time-default-refused-text and date-time-ts-default-stored-in-canonical-form in the app recipe. (#30532)

  Before, accepted and stored as written:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00Z")
  }

  After, because a Timestamp column holds no offset:

  model Event {
    id      Int       @id
    localAt Timestamp @default("2024-01-01T00:00:00")
  }

• The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type, of a fraction or an out-of-range number to an Int32 field, of a value outside the field's enum, or of null to a required field now fails with RUNTIME.ENCODE_FAILED naming the field. Before, some of these were stored as given. A filter expression passed to where() is encoded the same way, so a filter on an Int64 field needs a bigint. create() and createAll() return the document as stored, decoded like a read, and a nullable field missing from a stored document reads as null, not undefined. The query builder's match() still sends values as given. See the mongo-* entries in the app recipe. (#30519)

  Before:

  db.orm.posts.where(MongoFieldFilter.gt('views', Long.fromNumber(5)))

... (truncated)

Commits

• 266c45e chore(release): bump to 8.0.0-rc.14 (#30541)
• 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	Ready	Preview	Oct 8, 2026 10:44am UTC

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3bfa424

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

[borisno2]

@dependabot recreate

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.