Skip to content

chore(deps): bump the production-minor-patch group across 1 directory with 27 updates#512

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-minor-patch-b55634b402
Open

chore(deps): bump the production-minor-patch group across 1 directory with 27 updates#512
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-minor-patch-b55634b402

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 14, 2026

Copy link
Copy Markdown
Contributor

Bumps the production-minor-patch group with 27 updates in the / directory:

Package From To
pg 8.20.0 8.21.0
@clack/prompts 1.4.0 1.5.1
posthog-node 5.34.2 5.36.4
@rollup/rollup-linux-x64-gnu 4.60.4 4.61.1
@prisma-next/contract 0.8.0 0.12.0
@prisma-next/family-sql 0.8.0 0.12.0
@prisma-next/framework-components 0.8.0 0.12.0
@prisma-next/migration-tools 0.8.0 0.12.0
@prisma-next/sql-contract 0.8.0 0.12.0
@prisma-next/sql-operations 0.8.0 0.12.0
@prisma-next/sql-relational-core 0.8.0 0.12.0
@prisma-next/sql-runtime 0.8.0 0.12.0
@prisma-next/ts-render 0.8.0 0.12.0
@prisma-next/utils 0.8.0 0.12.0
@prisma-next/adapter-postgres 0.8.0 0.12.0
@prisma-next/driver-postgres 0.8.0 0.12.0
@prisma-next/sql-contract-psl 0.8.0 0.12.0
@prisma-next/target-postgres 0.8.0 0.12.0
@cipherstash/protect-ffi 0.23.0 0.25.0
@anthropic-ai/claude-agent-sdk 0.3.143 0.3.168
@prisma-next/postgres 0.8.0 0.12.0
@prisma-next/sql-orm-client 0.8.0 0.12.0
@clerk/nextjs 7.3.5 7.4.3
next 15.5.10 15.5.19
tsx 4.22.1 4.22.4
vitest 3.2.4 3.2.6
vite 8.0.13 8.0.16

Updates pg from 8.20.0 to 8.21.0

Changelog

Sourced from pg's changelog.

pg@8.21.0

Commits
  • 544b1ce Publish
  • cc03fa5 Add scramMaxIterations option to limit SCRAM iteration count (#3677)
  • f776327 Remove compatibility code for unsupported versions of Node (<16) (#3678)
  • f252870 cleanup: pg utils (#3675)
  • c8da6ab Assorted test cleanup (#3673)
  • fa47e73 fix: Client#end callback being called multiple times when first is no-op (#...
  • 88a7e60 cleanup: Move declaration to more natural place
  • 2095247 cleanup: Combine duplicated code in Client#query and avoid unneeded early n...
  • 0ac3edd fix: apply SASLprep (RFC 4013) to passwords before SCRAM-SHA-256 PBKDF2 (#3669)
  • be880d4 Assorted test fixes and cleanup (#3672)
  • Additional commits viewable in compare view

Updates @clack/prompts from 1.4.0 to 1.5.1

Release notes

Sourced from @​clack/prompts's releases.

@​clack/prompts@​1.5.1

Patch Changes

@​clack/prompts@​1.5.0

Minor Changes

  • #543 83428ac Thanks @​florian-lefebvre! - Adds support for Standard Schema validation

    Prompts accept an optional validate() function to validate user input. While a function provides more flexibility and customization over your validation, it can be a bit verbose. To help solve this, there are libraries that provide schema-based validation to make shorthand and type-strict validation substantially easier.

    Libraries following the Standard Schema specification are now natively supported. For example, using Arktype:

    import { text } from '@clack/prompts';
import { type } from 'arktype';
const name = await text({
message: 'Enter your email',

validate: type('string.email').describe('Invalid email'),
});

Patch Changes

Changelog

Sourced from @​clack/prompts's changelog.

1.5.1

Patch Changes

1.5.0

Minor Changes

  • #543 83428ac Thanks @​florian-lefebvre! - Adds support for Standard Schema validation

    Prompts accept an optional validate() function to validate user input. While a function provides more flexibility and customization over your validation, it can be a bit verbose. To help solve this, there are libraries that provide schema-based validation to make shorthand and type-strict validation substantially easier.

    Libraries following the Standard Schema specification are now natively supported. For example, using Arktype:

    import { text } from '@clack/prompts';
import { type } from 'arktype';
const name = await text({
message: 'Enter your email',

validate: type('string.email').describe('Invalid email'),
});

Patch Changes

Commits

Updates posthog-node from 5.34.2 to 5.36.4

Changelog

Sourced from posthog-node's changelog.

5.36.4

Patch Changes

  • Updated dependencies []:
    • @​posthog/core@​1.30.10

5.36.3

Patch Changes

  • Updated dependencies []:
    • @​posthog/core@​1.30.9

5.36.2

Patch Changes

  • Updated dependencies []:
    • @​posthog/core@​1.30.8

5.36.1

Patch Changes

  • Updated dependencies []:
    • @​posthog/core@​1.30.7

5.36.0

Minor Changes

  • #3728 9287c87 Thanks @​turnipdabeets! - Add a configurable $is_server event property (default true) so PostHog can identify server-side events. Set isServer: false when using the SDK as a client/CLI so the device OS is attributed normally. (2026-06-04)

5.35.15

Patch Changes

  • Updated dependencies []:
    • @​posthog/core@​1.30.6

5.35.14

Patch Changes

  • Updated dependencies []:
    • @​posthog/core@​1.30.5

5.35.13

... (truncated)

Commits
  • d46f0b9 chore: update versions and lockfile [version bump]
  • e0ebad5 chore: update versions and lockfile [version bump]
  • a8fd228 chore: update versions and lockfile [version bump]
  • 287ad9f chore: update versions and lockfile [version bump]
  • dc1e193 chore: update versions and lockfile [version bump]
  • 9287c87 feat: emit $is_server property on captured events (#3728)
  • b539fcb chore: update versions and lockfile [version bump]
  • 79de441 chore: update versions and lockfile [version bump]
  • 4a8cacc chore: add Sentry attribution comments (#3738)
  • d385e2a chore: clarify error tracking comments (#3735)
  • Additional commits viewable in compare view

Updates @rollup/rollup-linux-x64-gnu from 4.60.4 to 4.61.1

Release notes

Sourced from @​rollup/rollup-linux-x64-gnu's releases.

v4.61.1

4.61.1

2026-06-04

Bug Fixes

  • Avoid extraneous newlines when adding headers via plugins (#6403)
  • Fix a rare issue where starting Rollup would hang on Windows (#6404)

Pull Requests

v4.61.0

4.61.0

2026-06-01

Features

  • Sort entry modules to make chunk hashes deterministic (#6391)

Pull Requests

Changelog

Sourced from @​rollup/rollup-linux-x64-gnu's changelog.

4.61.1

2026-06-04

Bug Fixes

  • Avoid extraneous newlines when adding headers via plugins (#6403)
  • Fix a rare issue where starting Rollup would hang on Windows (#6404)

Pull Requests

4.61.0

2026-06-01

Features

  • Sort entry modules to make chunk hashes deterministic (#6391)

Pull Requests

Commits
  • b77daf0 4.61.1
  • 91b6dc4 fix: set report.excludeNetwork=true before getReport() to avoid blocking PTR ...
  • f2a0449 Improve documentation for manualPureFunctions (#6402)
  • 7bdce6c Does not add an extra leading line feed for addons (#6403)
  • 765167f 4.61.0
  • 0f547eb Sort entry modules to make chunk hash names deterministic (#6391)
  • 5838787 docs: fix broken links (#6400)
  • cc0f51a chore(deps): update react monorepo to v19 (#6395)
  • dd30037 fix(deps): update rust crate swc_compiler_base to v57 (#6396)
  • cb86c3e chore(deps): lock file maintenance (#6397)
  • Additional commits viewable in compare view

Updates @prisma-next/contract from 0.8.0 to 0.12.0

Release notes

Sourced from @​prisma-next/contract's releases.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contract.domain.namespaces.<ns>, and emitted contract.d.ts exports Models via ContractModelsMap<Contract> instead of Contract['models']. Re-emit your contract; consumers reading the flat shape must adopt the namespaced helpers. See the 0.11→0.12 upgrade recipe (extension authors: the extension-author recipe also covers the removal of the @prisma-next/contract/testing subpath — test factories now live in @prisma-next/test-utils). (#653)

    Before (consuming emitted contract.d.ts):

    type Models = Contract['models'];

    After:

    type Models = ContractModelsMap<Contract>;

  • Cross-namespace references are explicit { namespace, model } pairs — emitted contract roots and relation.to now carry an explicit { namespace, model } object (namespace branded as NamespaceId) rather than a bare model-name string. Re-emit your contract, and update any code that read relation.to (or a root) as a string to read .model / .namespace. (#600)

    Before (consuming emitted contract.d.ts):

    // relation.to was a bare model-name string
readonly to: 'User';

... (truncated)

Changelog

Sourced from @​prisma-next/contract's changelog.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contract.domain.namespaces.<ns>, and emitted contract.d.ts exports Models via ContractModelsMap<Contract> instead of Contract['models']. Re-emit your contract; consumers reading the flat shape must adopt the namespaced helpers. See the 0.11→0.12 upgrade recipe (extension authors: the extension-author recipe also covers the removal of the @prisma-next/contract/testing subpath — test factories now live in @prisma-next/test-utils). (#653)

    Before (consuming emitted contract.d.ts):

    type Models = Contract['models'];

    After:

    type Models = ContractModelsMap<Contract>;

  • Cross-namespace references are explicit { namespace, model } pairs — emitted contract roots and relation.to now carry an explicit { namespace, model } object (namespace branded as NamespaceId) rather than a bare model-name string. Re-emit your contract, and update any code that read relation.to (or a root) as a string to read .model / .namespace. (#600)

    Before (consuming emitted contract.d.ts):

    // relation.to was a bare model-name string
readonly to: 'User';

... (truncated)

Commits

Updates @prisma-next/family-sql from 0.8.0 to 0.12.0

Release notes

Sourced from @​prisma-next/family-sql's releases.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contract.domain.namespaces.<ns>, and emitted contract.d.ts exports Models via ContractModelsMap<Contract> instead of Contract['models']. Re-emit your contract; consumers reading the flat shape must adopt the namespaced helpers. See the 0.11→0.12 upgrade recipe (extension authors: the extension-author recipe also covers the removal of the @prisma-next/contract/testing subpath — test factories now live in @prisma-next/test-utils). (#653)

    Before (consuming emitted contract.d.ts):

    type Models = Contract['models'];

    After:

    type Models = ContractModelsMap<Contract>;

  • Cross-namespace references are explicit { namespace, model } pairs — emitted contract roots and relation.to now carry an explicit { namespace, model } object (namespace branded as NamespaceId) rather than a bare model-name string. Re-emit your contract, and update any code that read relation.to (or a root) as a string to read .model / .namespace. (#600)

    Before (consuming emitted contract.d.ts):

    // relation.to was a bare model-name string
readonly to: 'User';

... (truncated)

Changelog

Sourced from @​prisma-next/family-sql's changelog.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contract.domain.namespaces.<ns>, and emitted contract.d.ts exports Models via ContractModelsMap<Contract> instead of Contract['models']. Re-emit your contract; consumers reading the flat shape must adopt the namespaced helpers. See the 0.11→0.12 upgrade recipe (extension authors: the extension-author recipe also covers the removal of the @prisma-next/contract/testing subpath — test factories now live in @prisma-next/test-utils). (#653)

    Before (consuming emitted contract.d.ts):

    type Models = Contract['models'];

    After:

    type Models = ContractModelsMap<Contract>;

  • Cross-namespace references are explicit { namespace, model } pairs — emitted contract roots and relation.to now carry an explicit { namespace, model } object (namespace branded as NamespaceId) rather than a bare model-name string. Re-emit your contract, and update any code that read relation.to (or a root) as a string to read .model / .namespace. (#600)

    Before (consuming emitted contract.d.ts):

    // relation.to was a bare model-name string
readonly to: 'User';

... (truncated)

Commits

Updates @prisma-next/framework-components from 0.8.0 to 0.12.0

Release notes

Sourced from @​prisma-next/framework-components's releases.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contract.domain.namespaces.<ns>, and emitted contract.d.ts exports Models via ContractModelsMap<Contract> instead of Contract['models']. Re-emit your contract; consumers reading the flat shape must adopt the namespaced helpers. See the 0.11→0.12 upgrade recipe (extension authors: the extension-author recipe also covers the removal of the @prisma-next/contract/testing subpath — test factories now live in @prisma-next/test-utils). (#653)

    Before (consuming emitted contract.d.ts):

    type Models = Contract['models'];

    After:

    type Models = ContractModelsMap<Contract>;

  • Cross-namespace references are explicit { namespace, model } pairs — emitted contract roots and relation.to now carry an explicit { namespace, model } object (namespace branded as NamespaceId) rather than a bare model-name string. Re-emit your contract, and update any code that read relation.to (or a root) as a string to read .model / .namespace. (#600)

    Before (consuming emitted contract.d.ts):

    // relation.to was a bare model-name string
readonly to: 'User';

... (truncated)

Changelog

Sourced from @​prisma-next/framework-components's changelog.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contract.domain.namespaces.<ns>, and emitted contract.d.ts exports Models via ContractModelsMap<Contract> instead of Contract['models']. Re-emit your contract; consumers reading the flat shape must adopt the namespaced helpers. See the 0.11→0.12 upgrade recipe (extension authors: the extension-author recipe also covers the removal of the @prisma-next/contract/testing subpath — test factories now live in @prisma-next/test-utils). (#653)

    Before (consuming emitted contract.d.ts):

    type Models = Contract['models'];

    After:

    type Models = ContractModelsMap<Contract>;

  • Cross-namespace references are explicit { namespace, model } pairs — emitted contract roots and relation.to now carry an explicit { namespace, model } object (namespace branded as NamespaceId) rather than a bare model-name string. Re-emit your contract, and update any code that read relation.to (or a root) as a string to read .model / .namespace. (#600)

    Before (consuming emitted contract.d.ts):

    // relation.to was a bare model-name string
readonly to: 'User';

... (truncated)

Commits

Updates @prisma-next/migration-tools from 0.8.0 to 0.12.0

Release notes

Sourced from @​prisma-next/migration-tools's releases.

v0.12.0

Namespaces become first-class: un-namespaced Postgres models now live in public, the application plane is symmetric with storage, and every cross-namespace reference is explicit. This release also ratifies a version-support policy (Node 24+), simplifies runtime marker verification, closes MongoDB validators by default, and adds raw SQL to the typed builder. Several contract-shape changes require a one-time re-emit — most are mechanical and covered by the linked upgrade recipes.

Breaking changes

  • Supported-version floors raised — the supported floor for each dependency is now the latest GA release we test against: Node.js >=24 (declared in every package's engines), TypeScript >=5.9, PostgreSQL 17, and MongoDB 8.0. Bump your runtime and toolchain to meet these floors before upgrading. (#659)

  • Un-namespaced Postgres models default to public — models without an explicit namespace now emit under the public namespace instead of the __unbound__ sentinel (postgres-unbound-schema → postgres-schema); explicit namespace unbound { … } still round-trips to __unbound__. Re-emit your contract so contract.json / contract.d.ts pick up the new namespace key. See the 0.11→0.12 upgrade recipe. (#662)

    Before (emitted contract.json):

    "storage": {
  "namespaces": {
    "__unbound__": { "id": "__unbound__", "kind": "postgres-unbound-schema" }
  }
}

    After:

    "storage": {
  "namespaces": {
    "public": { "id": "public", "kind": "postgres-schema" }
  }
}

  • Symmetric domain plane — models and value objects moved from flat contract.models / contract.valueObjects to contrac...

    Description has been truncated

@dependabot
chore(deps): bump the production-minor-patch group across 1 directory…
c742cd0 
… with 27 updates

Bumps the production-minor-patch group with 27 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [pg](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg) | `8.20.0` | `8.21.0` |
| [@clack/prompts](https://github.com/bombshell-dev/clack/tree/HEAD/packages/prompts) | `1.4.0` | `1.5.1` |
| [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.34.2` | `5.36.4` |
| [@rollup/rollup-linux-x64-gnu](https://github.com/rollup/rollup) | `4.60.4` | `4.61.1` |
| [@prisma-next/contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/contract) | `0.8.0` | `0.12.0` |
| [@prisma-next/family-sql](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/9-family) | `0.8.0` | `0.12.0` |
| [@prisma-next/framework-components](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/framework-components) | `0.8.0` | `0.12.0` |
| [@prisma-next/migration-tools](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/3-tooling/migration) | `0.8.0` | `0.12.0` |
| [@prisma-next/sql-contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/contract) | `0.8.0` | `0.12.0` |
| [@prisma-next/sql-operations](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/operations) | `0.8.0` | `0.12.0` |
| [@prisma-next/sql-relational-core](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/4-lanes/relational-core) | `0.8.0` | `0.12.0` |
| [@prisma-next/sql-runtime](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/5-runtime) | `0.8.0` | `0.12.0` |
| [@prisma-next/ts-render](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/ts-render) | `0.8.0` | `0.12.0` |
| [@prisma-next/utils](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/utils) | `0.8.0` | `0.12.0` |
| [@prisma-next/adapter-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/6-adapters/postgres) | `0.8.0` | `0.12.0` |
| [@prisma-next/driver-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/7-drivers/postgres) | `0.8.0` | `0.12.0` |
| [@prisma-next/sql-contract-psl](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/2-authoring/contract-psl) | `0.8.0` | `0.12.0` |
| [@prisma-next/target-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/3-targets/postgres) | `0.8.0` | `0.12.0` |
| [@cipherstash/protect-ffi](https://github.com/cipherstash/protectjs-ffi) | `0.23.0` | `0.25.0` |
| [@anthropic-ai/claude-agent-sdk](https://github.com/anthropics/claude-agent-sdk-typescript) | `0.3.143` | `0.3.168` |
| [@prisma-next/postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/postgres) | `0.8.0` | `0.12.0` |
| [@prisma-next/sql-orm-client](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/sql-orm-client) | `0.8.0` | `0.12.0` |
| [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs) | `7.3.5` | `7.4.3` |
| [next](https://github.com/vercel/next.js) | `15.5.10` | `15.5.19` |
| [tsx](https://github.com/privatenumber/tsx) | `4.22.1` | `4.22.4` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `3.2.4` | `3.2.6` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.0.13` | `8.0.16` |



Updates `pg` from 8.20.0 to 8.21.0
- [Changelog](https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md)
- [Commits](https://github.com/brianc/node-postgres/commits/pg@8.21.0/packages/pg)

Updates `@clack/prompts` from 1.4.0 to 1.5.1
- [Release notes](https://github.com/bombshell-dev/clack/releases)
- [Changelog](https://github.com/bombshell-dev/clack/blob/main/packages/prompts/CHANGELOG.md)
- [Commits](https://github.com/bombshell-dev/clack/commits/@clack/prompts@1.5.1/packages/prompts)

Updates `posthog-node` from 5.34.2 to 5.36.4
- [Release notes](https://github.com/PostHog/posthog-js/releases)
- [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md)
- [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.36.4/packages/node)

Updates `@rollup/rollup-linux-x64-gnu` from 4.60.4 to 4.61.1
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.60.4...v4.61.1)

Updates `@prisma-next/contract` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/1-framework/0-foundation/contract)

Updates `@prisma-next/family-sql` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/2-sql/9-family)

Updates `@prisma-next/framework-components` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/1-framework/1-core/framework-components)

Updates `@prisma-next/migration-tools` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/1-framework/3-tooling/migration)

Updates `@prisma-next/sql-contract` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/2-sql/1-core/contract)

Updates `@prisma-next/sql-operations` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/2-sql/1-core/operations)

Updates `@prisma-next/sql-relational-core` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/2-sql/4-lanes/relational-core)

Updates `@prisma-next/sql-runtime` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/2-sql/5-runtime)

Updates `@prisma-next/ts-render` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/1-framework/1-core/ts-render)

Updates `@prisma-next/utils` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/1-framework/0-foundation/utils)

Updates `@prisma-next/adapter-postgres` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/3-targets/6-adapters/postgres)

Updates `@prisma-next/driver-postgres` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/3-targets/7-drivers/postgres)

Updates `@prisma-next/sql-contract-psl` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/2-sql/2-authoring/contract-psl)

Updates `@prisma-next/target-postgres` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/3-targets/3-targets/postgres)

Updates `@cipherstash/protect-ffi` from 0.23.0 to 0.25.0
- [Release notes](https://github.com/cipherstash/protectjs-ffi/releases)
- [Commits](cipherstash/protectjs-ffi@v0.23.0...v0.25.0)

Updates `@anthropic-ai/claude-agent-sdk` from 0.3.143 to 0.3.168
- [Release notes](https://github.com/anthropics/claude-agent-sdk-typescript/releases)
- [Changelog](https://github.com/anthropics/claude-agent-sdk-typescript/blob/main/CHANGELOG.md)
- [Commits](anthropics/claude-agent-sdk-typescript@v0.3.143...v0.3.168)

Updates `@prisma-next/postgres` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/3-extensions/postgres)

Updates `@prisma-next/sql-orm-client` from 0.8.0 to 0.12.0
- [Release notes](https://github.com/prisma/prisma-next/releases)
- [Changelog](https://github.com/prisma/prisma-next/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prisma/prisma-next/commits/v0.12.0/packages/3-extensions/sql-orm-client)

Updates `@clerk/nextjs` from 7.3.5 to 7.4.3
- [Release notes](https://github.com/clerk/javascript/releases)
- [Changelog](https://github.com/clerk/javascript/blob/main/packages/nextjs/CHANGELOG.md)
- [Commits](https://github.com/clerk/javascript/commits/@clerk/nextjs@7.4.3/packages/nextjs)

Updates `next` from 15.5.10 to 15.5.19
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.5.10...v15.5.19)

Updates `tsx` from 4.22.1 to 4.22.4
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.22.1...v4.22.4)

Updates `vitest` from 3.2.4 to 3.2.6
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.6/packages/vitest)

Updates `vite` from 8.0.13 to 8.0.16
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.0.16/packages/vite)

---
updated-dependencies:
- dependency-name: pg
  dependency-version: 8.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@clack/prompts"
  dependency-version: 1.5.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: posthog-node
  dependency-version: 5.36.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@rollup/rollup-linux-x64-gnu"
  dependency-version: 4.61.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/contract"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/family-sql"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/framework-components"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/migration-tools"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/sql-contract"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/sql-operations"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/sql-relational-core"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/sql-runtime"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/ts-render"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/utils"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/adapter-postgres"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/driver-postgres"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/sql-contract-psl"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/target-postgres"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/protect-ffi"
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@anthropic-ai/claude-agent-sdk"
  dependency-version: 0.3.168
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/postgres"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/sql-orm-client"
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@clerk/nextjs"
  dependency-version: 7.4.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: next
  dependency-version: 15.5.19
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: tsx
  dependency-version: 4.22.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: vitest
  dependency-version: 3.2.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: vite
  dependency-version: 8.0.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 14, 2026
@dependabot dependabot Bot requested a review from a team as a code owner June 14, 2026 22:14
@dependabot @github

dependabot Bot commented on behalf of github Jun 14, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: supply-chain. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@changeset-bot

changeset-bot Bot commented Jun 14, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c742cd0

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants