Skip to content

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

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

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

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

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

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

Package From To
pg 8.20.0 8.21.0
@clack/prompts 1.4.0 1.5.0
posthog-node 5.34.2 5.35.7
@prisma-next/contract 0.8.0 0.11.0
@prisma-next/family-sql 0.8.0 0.11.0
@prisma-next/framework-components 0.8.0 0.11.0
@prisma-next/migration-tools 0.8.0 0.11.0
@prisma-next/sql-contract 0.8.0 0.11.0
@prisma-next/sql-operations 0.8.0 0.11.0
@prisma-next/sql-relational-core 0.8.0 0.11.0
@prisma-next/sql-runtime 0.8.0 0.11.0
@prisma-next/ts-render 0.8.0 0.11.0
@prisma-next/utils 0.8.0 0.11.0
@prisma-next/adapter-postgres 0.8.0 0.11.0
@prisma-next/driver-postgres 0.8.0 0.11.0
@prisma-next/sql-contract-psl 0.8.0 0.11.0
@prisma-next/target-postgres 0.8.0 0.11.0
@cipherstash/protect-ffi 0.23.0 0.25.0
@anthropic-ai/claude-agent-sdk 0.3.143 0.3.159
@prisma-next/postgres 0.8.0 0.11.0
@prisma-next/sql-orm-client 0.8.0 0.11.0
@clerk/nextjs 7.3.5 7.4.2
next 15.5.10 15.5.18
tsx 4.22.1 4.22.4
vite 8.0.13 8.0.14

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

Release notes

Sourced from @​clack/prompts's releases.

@​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.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.35.7

Changelog

Sourced from posthog-node's changelog.

5.35.7

Patch Changes

  • Updated dependencies [d9ad199]:
    • @​posthog/core@​1.29.14

5.35.6

Patch Changes

5.35.5

Patch Changes

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

5.35.4

Patch Changes

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

5.35.3

Patch Changes

  • Updated dependencies [5568f12]:
    • @​posthog/core@​1.29.10

5.35.2

Patch Changes

  • #3658 5d7a2d3 Thanks @​gustavohstrassburger! - Include group context in the $feature_flag_called deduplication key in _captureFlagCalledEventIfNeeded, so events fire independently per group combination. (2026-05-25)

5.35.1

Patch Changes

  • Updated dependencies [c806cca]:
    • @​posthog/core@​1.29.9

... (truncated)

Commits
  • af69e9c chore: update versions and lockfile [version bump]
  • 4eb5416 test(node): drain promise queue in captureException context tests (#3696)
  • a122070 chore: update versions and lockfile [version bump]
  • 7b84b75 fix: unify capture exception (#3681)
  • 727ddcf chore: update versions and lockfile [version bump]
  • e5a89ac chore: update versions and lockfile [version bump]
  • 55b3c42 chore: update versions and lockfile [version bump]
  • 1d0daf0 chore: update versions and lockfile [version bump]
  • 5d7a2d3 fix(node): fire separate $feature_flag_called events per group context (#3658)
  • 3d41c1d chore: update versions and lockfile [version bump]
  • Additional commits viewable in compare view

Updates @prisma-next/contract from 0.8.0 to 0.11.0

Release notes

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

v0.11.0

What's Changed

New Contributors

Full Changelog: prisma/prisma-next@v0.10.0...v0.11.0

v0.10.0

What's Changed

Full Changelog: prisma/prisma-next@v0.9.0...v0.10.0

v0.9.0

What's Changed

... (truncated)

Changelog

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

Changelog

The rolling, newest-first index of Prisma Next releases. Each entry mirrors the release's committed notes file under https://github.com/prisma/prisma-next/blob/main/docs/releases (the body of its GitHub Release) under a ## v<version> header — see https://github.com/prisma/prisma-next/blob/main/docs/releases/README.md for the convention and authoring template.

Changelog tracking starts at v0.12.0, the first release cut after this convention landed. For v0.11.0 and earlier, see the GitHub Releases page — historical notes are not backfilled here.

v0.13.0 (unreleased)

Breaking changes

  • MTI variant tables materialize a base-PK link column (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant that carries its own @@map (and is therefore stored in its own table) now emits a base-PK link column in storage: the variant table gains an id column, a single-column primary key on it, and a cascading foreign key (ON DELETE CASCADE) referencing the base table's primary key. Previously the variant table held only the variant-specific columns with no primary key and no link to its base. This changes the emitted contract.json / contract.d.ts and the contract's storageHash. Re-emit your contract, then plan and apply the matching migration to add the column, PK, and FK to your database. Variants that share the base table (no own @@map) are unaffected. See the migration recipe. (#669)

    Before (emitted contract.json, variant table bug):

    "bug": {
      "columns": {
        "severity": { "codecId": "pg/text@1", "nullable": false }
      }
    }

    After:

    "bug": {
      "columns": {
        "id": { "codecId": "sql/char@1", "nullable": false },
        "severity": { "codecId": "pg/text@1", "nullable": false }
      },
      "primaryKey": { "columns": ["id"] },
      "foreignKeys": [
        {
          "name": "bug_id_fkey",
          "columns": ["id"],
          "references": { "table": "task", "columns": ["id"] },
          "onDelete": "cascade"
        }
      ]
    }

Features

  • STI variants can declare their own fields (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant with no own @@map (single-table inheritance) may now declare its own scalar fields. Each such field is materialized as a column on the shared base table (always nullable in storage, since the base table also holds sibling-variant rows), and the variant no longer emits a stray shadow table. Previously the variant's column was never added to the base table, so the contract failed to emit with references non-existent column. This is purely enabling: existing contracts re-emit identically. (#669)

v0.12.0

... (truncated)

Commits

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

Release notes

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

v0.11.0

What's Changed

New Contributors

Full Changelog: prisma/prisma-next@v0.10.0...v0.11.0

v0.10.0

What's Changed

Full Changelog: prisma/prisma-next@v0.9.0...v0.10.0

v0.9.0

What's Changed

... (truncated)

Changelog

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

Changelog

The rolling, newest-first index of Prisma Next releases. Each entry mirrors the release's committed notes file under https://github.com/prisma/prisma-next/blob/main/docs/releases (the body of its GitHub Release) under a ## v<version> header — see https://github.com/prisma/prisma-next/blob/main/docs/releases/README.md for the convention and authoring template.

Changelog tracking starts at v0.12.0, the first release cut after this convention landed. For v0.11.0 and earlier, see the GitHub Releases page — historical notes are not backfilled here.

v0.13.0 (unreleased)

Breaking changes

  • MTI variant tables materialize a base-PK link column (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant that carries its own @@map (and is therefore stored in its own table) now emits a base-PK link column in storage: the variant table gains an id column, a single-column primary key on it, and a cascading foreign key (ON DELETE CASCADE) referencing the base table's primary key. Previously the variant table held only the variant-specific columns with no primary key and no link to its base. This changes the emitted contract.json / contract.d.ts and the contract's storageHash. Re-emit your contract, then plan and apply the matching migration to add the column, PK, and FK to your database. Variants that share the base table (no own @@map) are unaffected. See the migration recipe. (#669)

    Before (emitted contract.json, variant table bug):

    "bug": {
      "columns": {
        "severity": { "codecId": "pg/text@1", "nullable": false }
      }
    }

    After:

    "bug": {
      "columns": {
        "id": { "codecId": "sql/char@1", "nullable": false },
        "severity": { "codecId": "pg/text@1", "nullable": false }
      },
      "primaryKey": { "columns": ["id"] },
      "foreignKeys": [
        {
          "name": "bug_id_fkey",
          "columns": ["id"],
          "references": { "table": "task", "columns": ["id"] },
          "onDelete": "cascade"
        }
      ]
    }

Features

  • STI variants can declare their own fields (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant with no own @@map (single-table inheritance) may now declare its own scalar fields. Each such field is materialized as a column on the shared base table (always nullable in storage, since the base table also holds sibling-variant rows), and the variant no longer emits a stray shadow table. Previously the variant's column was never added to the base table, so the contract failed to emit with references non-existent column. This is purely enabling: existing contracts re-emit identically. (#669)

v0.12.0

... (truncated)

Commits

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

Release notes

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

v0.11.0

What's Changed

New Contributors

Full Changelog: prisma/prisma-next@v0.10.0...v0.11.0

v0.10.0

What's Changed

Full Changelog: prisma/prisma-next@v0.9.0...v0.10.0

v0.9.0

What's Changed

... (truncated)

Changelog

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

Changelog

The rolling, newest-first index of Prisma Next releases. Each entry mirrors the release's committed notes file under https://github.com/prisma/prisma-next/blob/main/docs/releases (the body of its GitHub Release) under a ## v<version> header — see https://github.com/prisma/prisma-next/blob/main/docs/releases/README.md for the convention and authoring template.

Changelog tracking starts at v0.12.0, the first release cut after this convention landed. For v0.11.0 and earlier, see the GitHub Releases page — historical notes are not backfilled here.

v0.13.0 (unreleased)

Breaking changes

  • MTI variant tables materialize a base-PK link column (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant that carries its own @@map (and is therefore stored in its own table) now emits a base-PK link column in storage: the variant table gains an id column, a single-column primary key on it, and a cascading foreign key (ON DELETE CASCADE) referencing the base table's primary key. Previously the variant table held only the variant-specific columns with no primary key and no link to its base. This changes the emitted contract.json / contract.d.ts and the contract's storageHash. Re-emit your contract, then plan and apply the matching migration to add the column, PK, and FK to your database. Variants that share the base table (no own @@map) are unaffected. See the migration recipe. (#669)

    Before (emitted contract.json, variant table bug):

    "bug": {
      "columns": {
        "severity": { "codecId": "pg/text@1", "nullable": false }
      }
    }

    After:

    "bug": {
      "columns": {
        "id": { "codecId": "sql/char@1", "nullable": false },
        "severity": { "codecId": "pg/text@1", "nullable": false }
      },
      "primaryKey": { "columns": ["id"] },
      "foreignKeys": [
        {
          "name": "bug_id_fkey",
          "columns": ["id"],
          "references": { "table": "task", "columns": ["id"] },
          "onDelete": "cascade"
        }
      ]
    }

Features

  • STI variants can declare their own fields (@prisma-next/sql-contract-psl) — a PSL @@base(Parent, "tag") variant with no own @@map (single-table inheritance) may now declare its own scalar fields. Each such field is materialized as a column on the shared base table (always nullable in storage, since the base table also holds sibling-variant rows), and the variant no longer emits a stray shadow table. Previously the variant's column was never added to the base table, so the contract failed to emit with references non-existent column. This is purely enabling: existing contracts re-emit identically. (#669)

v0.12.0

... (truncated)

Commits

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

Release notes

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

v0.11.0

What's Changed

… with 25 updates

Bumps the production-minor-patch group with 25 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.0` |
| [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.34.2` | `5.35.7` |
| [@prisma-next/contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/contract) | `0.8.0` | `0.11.0` |
| [@prisma-next/family-sql](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/9-family) | `0.8.0` | `0.11.0` |
| [@prisma-next/framework-components](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/framework-components) | `0.8.0` | `0.11.0` |
| [@prisma-next/migration-tools](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/3-tooling/migration) | `0.8.0` | `0.11.0` |
| [@prisma-next/sql-contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/contract) | `0.8.0` | `0.11.0` |
| [@prisma-next/sql-operations](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/operations) | `0.8.0` | `0.11.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.11.0` |
| [@prisma-next/sql-runtime](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/5-runtime) | `0.8.0` | `0.11.0` |
| [@prisma-next/ts-render](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/ts-render) | `0.8.0` | `0.11.0` |
| [@prisma-next/utils](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/utils) | `0.8.0` | `0.11.0` |
| [@prisma-next/adapter-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/6-adapters/postgres) | `0.8.0` | `0.11.0` |
| [@prisma-next/driver-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/7-drivers/postgres) | `0.8.0` | `0.11.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.11.0` |
| [@prisma-next/target-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/3-targets/postgres) | `0.8.0` | `0.11.0` |
| @cipherstash/protect-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.159` |
| [@prisma-next/postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/postgres) | `0.8.0` | `0.11.0` |
| [@prisma-next/sql-orm-client](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/sql-orm-client) | `0.8.0` | `0.11.0` |
| [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs) | `7.3.5` | `7.4.2` |
| [next](https://github.com/vercel/next.js) | `15.5.10` | `15.5.18` |
| [tsx](https://github.com/privatenumber/tsx) | `4.22.1` | `4.22.4` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.0.13` | `8.0.14` |



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.0
- [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.0/packages/prompts)

Updates `posthog-node` from 5.34.2 to 5.35.7
- [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.35.7/packages/node)

Updates `@prisma-next/contract` from 0.8.0 to 0.11.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.11.0/packages/1-framework/0-foundation/contract)

Updates `@prisma-next/family-sql` from 0.8.0 to 0.11.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.11.0/packages/2-sql/9-family)

Updates `@prisma-next/framework-components` from 0.8.0 to 0.11.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.11.0/packages/1-framework/1-core/framework-components)

Updates `@prisma-next/migration-tools` from 0.8.0 to 0.11.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.11.0/packages/1-framework/3-tooling/migration)

Updates `@prisma-next/sql-contract` from 0.8.0 to 0.11.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.11.0/packages/2-sql/1-core/contract)

Updates `@prisma-next/sql-operations` from 0.8.0 to 0.11.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.11.0/packages/2-sql/1-core/operations)

Updates `@prisma-next/sql-relational-core` from 0.8.0 to 0.11.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.11.0/packages/2-sql/4-lanes/relational-core)

Updates `@prisma-next/sql-runtime` from 0.8.0 to 0.11.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.11.0/packages/2-sql/5-runtime)

Updates `@prisma-next/ts-render` from 0.8.0 to 0.11.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.11.0/packages/1-framework/1-core/ts-render)

Updates `@prisma-next/utils` from 0.8.0 to 0.11.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.11.0/packages/1-framework/0-foundation/utils)

Updates `@prisma-next/adapter-postgres` from 0.8.0 to 0.11.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.11.0/packages/3-targets/6-adapters/postgres)

Updates `@prisma-next/driver-postgres` from 0.8.0 to 0.11.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.11.0/packages/3-targets/7-drivers/postgres)

Updates `@prisma-next/sql-contract-psl` from 0.8.0 to 0.11.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.11.0/packages/2-sql/2-authoring/contract-psl)

Updates `@prisma-next/target-postgres` from 0.8.0 to 0.11.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.11.0/packages/3-targets/3-targets/postgres)

Updates `@cipherstash/protect-ffi` from 0.23.0 to 0.25.0

Updates `@anthropic-ai/claude-agent-sdk` from 0.3.143 to 0.3.159
- [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.159)

Updates `@prisma-next/postgres` from 0.8.0 to 0.11.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.11.0/packages/3-extensions/postgres)

Updates `@prisma-next/sql-orm-client` from 0.8.0 to 0.11.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.11.0/packages/3-extensions/sql-orm-client)

Updates `@clerk/nextjs` from 7.3.5 to 7.4.2
- [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.2/packages/nextjs)

Updates `next` from 15.5.10 to 15.5.18
- [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.18)

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 `vite` from 8.0.13 to 8.0.14
- [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.14/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.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: posthog-node
  dependency-version: 5.35.7
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/contract"
  dependency-version: 0.11.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.11.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.11.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.11.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.11.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.11.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.11.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.11.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.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/utils"
  dependency-version: 0.11.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.11.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.11.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.11.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.11.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.159
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/postgres"
  dependency-version: 0.11.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.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@clerk/nextjs"
  dependency-version: 7.4.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: next
  dependency-version: 15.5.18
  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: vite
  dependency-version: 8.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jun 7, 2026

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.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 7, 2026
@dependabot dependabot Bot requested a review from a team as a code owner June 7, 2026 22:13
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 7, 2026
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jun 7, 2026

⚠️ No Changeset found

Latest commit: b9f725e

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants