Skip to content

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

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

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

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the production-minor-patch group with 33 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.37.0
@rollup/rollup-linux-x64-gnu 4.60.4 4.62.0
@prisma-next/contract 0.8.0 0.13.0
@prisma-next/family-sql 0.8.0 0.13.0
@prisma-next/framework-components 0.8.0 0.13.0
@prisma-next/migration-tools 0.8.0 0.13.0
@prisma-next/sql-contract 0.8.0 0.13.0
@prisma-next/sql-operations 0.8.0 0.13.0
@prisma-next/sql-relational-core 0.8.0 0.13.0
@prisma-next/sql-runtime 0.8.0 0.13.0
@prisma-next/ts-render 0.8.0 0.13.0
@prisma-next/utils 0.8.0 0.13.0
@prisma-next/adapter-postgres 0.8.0 0.13.0
@prisma-next/driver-postgres 0.8.0 0.13.0
@prisma-next/sql-contract-psl 0.8.0 0.13.0
@prisma-next/target-postgres 0.8.0 0.13.0
@cipherstash/protect-ffi 0.23.0 0.26.0
@anthropic-ai/claude-agent-sdk 0.3.143 0.3.177
@prisma-next/postgres 0.8.0 0.13.0
@prisma-next/sql-orm-client 0.8.0 0.13.0
@cipherstash/auth-darwin-arm64 0.38.0 0.39.0
@cipherstash/auth-darwin-x64 0.38.0 0.39.0
@cipherstash/auth-linux-arm64-gnu 0.38.0 0.39.0
@cipherstash/auth-linux-x64-gnu 0.38.0 0.39.0
@cipherstash/auth-linux-x64-musl 0.38.0 0.39.0
@cipherstash/auth-win32-x64-msvc 0.38.0 0.39.0
@clerk/nextjs 7.3.5 7.5.2
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.37.0

Release notes

Sourced from posthog-node's releases.

posthog-node@5.37.0

5.37.0

Minor Changes

  • #3705 d6fc0a5 Thanks @​gustavohstrassburger! - feat(feature-flags): support the early_exit condition option in local evaluation. When a flag enables early exit, evaluation now stops and returns false as soon as a condition group's property filters match but the rollout percentage excludes the user, instead of falling through to later groups — matching the server-side evaluation behavior. (2026-06-12)

posthog-node@5.36.17

5.36.17

Patch Changes

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

posthog-node@5.36.16

5.36.16

Patch Changes

  • Updated dependencies [25822ac]:
    • @​posthog/core@​1.32.2
Changelog

Sourced from posthog-node's changelog.

5.37.0

Minor Changes

  • #3705 d6fc0a5 Thanks @​gustavohstrassburger! - feat(feature-flags): support the early_exit condition option in local evaluation. When a flag enables early exit, evaluation now stops and returns false as soon as a condition group's property filters match but the rollout percentage excludes the user, instead of falling through to later groups — matching the server-side evaluation behavior. (2026-06-12)

5.36.17

Patch Changes

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

5.36.16

Patch Changes

  • Updated dependencies [25822ac]:
    • @​posthog/core@​1.32.2

5.36.15

Patch Changes

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

5.36.14

Patch Changes

  • Updated dependencies [612f97a]:
    • @​posthog/core@​1.32.0

5.36.13

Patch Changes

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

5.36.12

Patch Changes

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

5.36.11

... (truncated)

Commits
  • 5e8c4b7 chore: update versions and lockfile [version bump]
  • d6fc0a5 feat(flags): support early_exit in posthog-node local evaluation (#3705)
  • be08a64 docs: centralize SDK examples in official docs (#3825)
  • 1f2c06b chore: make workspace releases explicit (#3803)
  • c7abf85 chore: update versions and lockfile [version bump]
  • 5fe3bd4 chore: update versions and lockfile [version bump]
  • defbc62 chore: update versions and lockfile [version bump]
  • 50a666f chore: update versions and lockfile [version bump]
  • f4d4c8b chore: update versions and lockfile [version bump]
  • 8b8b196 chore: update versions and lockfile [version bump]
  • Additional commits viewable in compare view

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

Release notes

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

v4.62.0

4.62.0

2026-06-13

Features

  • Ensure that shared dependencies between manual chunks and entry points receive a serparate chunk (#6374)

Pull Requests

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

... (truncated)

Changelog

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

4.62.0

2026-06-13

Features

  • Ensure that shared dependencies between manual chunks and entry points receive a serparate chunk (#6374)

Pull Requests

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

... (truncated)

Commits
  • 5e0066d 4.62.0
  • 93e85fc chore(deps): update dependency eslint-plugin-unicorn to v65 (#6413)
  • 5c9ef2e fix(deps): update minor/patch updates (#6412)
  • 18654d8 chore(deps): lock file maintenance minor/patch updates (#6414)
  • d96ed95 Extract the static dependencies imported by manual chunks into separate chunk...
  • 126e141 chore(deps): pin dependency concurrently to v9 (#6406)
  • f2f58c4 chore(deps): lock file maintenance minor/patch updates (#6410)
  • 5a15062 chore(deps): update minor/patch updates to v6.2.0 (#6409)
  • d02f03a chore(deps): lock file maintenance minor/patch updates (#6407)
  • 844671c fix(deps): update minor/patch updates (#6405)
  • Additional commits viewable in compare view

Updates @prisma-next/contract from 0.8.0 to 0.13.0

Release notes

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

v0.13.0

This release makes namespaces a first-class part of the query surface, adds cross-contract foreign keys to the SQL ORM, makes many-to-many a validatable contract shape, introduces a per-object control policy (@@control) that decides what Prisma manages, ships domain enums backed by storage value-sets, and gives the migration CLI a unified graph-tree view across list / log / status / show. Telemetry also flips from opt-in to opt-out. A few changes require a one-time contract re-emit — all are covered by the linked upgrade recipes.

Breaking changes

  • Telemetry is now opt-out — anonymous CLI telemetry is collected by default and you opt out, where previously you opted in. Set PRISMA_NEXT_DISABLE_TELEMETRY=1 (or DO_NOT_TRACK=1) to turn it off. See docs/Telemetry.md for what is collected and every opt-out signal. (#676)

  • MTI variant tables materialize a base-PK link column — 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 a copy of the base table's primary-key column(s), a primary key over them, 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. Variants that share the base table (no own @@map) are unaffected. See the 0.12→0.13 upgrade 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"
    }
  ]
}

  • Contract storage IR moved to a namespace envelope — the SQL/Mongo storage IR is now keyed by namespace (storage.namespaces.<ns>.entries.<kind>), and cross-references are explicit { namespace, model } objects in domain. Consumer impact is mechanical: re-emit with prisma-next contract emit to pick up the new shape. No codemod or source change is required, but the contract's storageHash changes, so plan and apply a migration afterward. (#715)

  • Extension authors: codec-resolution SPI takes a leading namespaceId — CodecDescriptorRegistry.codecRefForColumn(table, column) is now codecRefForColumn(namespaceId, table, column), and the free codecRefForStorageColumn(storage, table, column) is now codecRefForStorageColumn(storage, namespaceId, table, column) (both in @prisma-next/sql-relational-core). Thread the namespace the table lives in through every call site that stamps codec onto AST nodes. There is no codemod — the right namespace is call-site-specific. See the 0.12→0.13 extension-author recipe. (#715)

    Before:

    const ref = descriptors.codecRefForColumn('document', 'embedding');

... (truncated)

Changelog

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

v0.13.0

This release makes namespaces a first-class part of the query surface, adds cross-contract foreign keys to the SQL ORM, makes many-to-many a validatable contract shape, introduces a per-object control policy (@@control) that decides what Prisma manages, ships domain enums backed by storage value-sets, and gives the migration CLI a unified graph-tree view across list / log / status / show. Telemetry also flips from opt-in to opt-out. A few changes require a one-time contract re-emit — all are covered by the linked upgrade recipes.

Breaking changes

  • Telemetry is now opt-out — anonymous CLI telemetry is collected by default and you opt out, where previously you opted in. Set PRISMA_NEXT_DISABLE_TELEMETRY=1 (or DO_NOT_TRACK=1) to turn it off. See docs/Telemetry.md for what is collected and every opt-out signal. (#676)

  • MTI variant tables materialize a base-PK link column — 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 a copy of the base table's primary-key column(s), a primary key over them, 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. Variants that share the base table (no own @@map) are unaffected. See the 0.12→0.13 upgrade 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"
    }
  ]
}

  • Contract storage IR moved to a namespace envelope — the SQL/Mongo storage IR is now keyed by namespace (storage.namespaces.<ns>.entries.<kind>), and cross-references are explicit { namespace, model } objects in domain. Consumer impact is mechanical: re-emit with prisma-next contract emit to pick up the new shape. No codemod or source change is required, but the contract's storageHash changes, so plan and apply a migration afterward. (#715)

  • Extension authors: codec-resolution SPI takes a leading namespaceId — CodecDescriptorRegistry.codecRefForColumn(table, column) is now codecRefForColumn(namespaceId, table, column), and the free codecRefForStorageColumn(storage, table, column) is now codecRefForStorageColumn(storage, namespaceId, table, column) (both in @prisma-next/sql-relational-core). Thread the namespace the table lives in through every call site that stamps codec onto AST nodes. There is no codemod — the right namespace is call-site-specific. See the 0.12→0.13 extension-author recipe. (#715)

    Before:

    const ref = descriptors.codecRefForColumn('document', 'embedding');

... (truncated)

Commits

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

Release notes

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

v0.13.0

This release makes namespaces a first-class part of the query surface, adds cross-contract foreign keys to the SQL ORM, makes many-to-many a validatable contract shape, introduces a per-object control policy (@@control) that decides what Prisma manages, ships domain enums backed by storage value-sets, and gives the migration CLI a unified graph-tree view across list / log / status / show. Telemetry also flips from opt-in to opt-out. A few changes require a one-time contract re-emit — all are covered by the linked upgrade recipes.

Breaking changes

  • Telemetry is now opt-out — anonymous CLI telemetry is collected by default and you opt out, where previously you opted in. Set PRISMA_NEXT_DISABLE_TELEMETRY=1 (or DO_NOT_TRACK=1) to turn it off. See docs/Telemetry.md for what is collected and every opt-out signal. (#676)

  • MTI variant tables materialize a base-PK link column — 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 a copy of the base table's primary-key column(s), a primary key over them, 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. Variants that share the base table (no own @@map) are unaffected. See the 0.12→0.13 upgrade 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"
    }
  ]
}

  • Contract storage IR moved to a namespace envelope — the SQL/Mongo storage IR is now keyed by namespace (storage.namespaces.<ns>.entries.<kind>), and cross-references are explicit { namespace, model } objects in domain. Consumer impact is mechanical: re-emit with prisma-next contract emit to pick up the new shape. No codemod or source change is required, but the contract's storageHash changes, so plan and apply a migration afterward. (#715)

  • Extension authors: codec-resolution SPI takes a leading namespaceId — CodecDescriptorRegistry.codecRefForColumn(table, column) is now codecRefForColumn(namespaceId, table, column), and the free codecRefForStorageColumn(storage, table, column) is now codecRefForStorageColumn(storage, namespaceId, table, column) (both in @prisma-next/sql-relational-core). Thread the namespace the table lives in through every call site that stamps codec onto AST nodes. There is no codemod — the right namespace is call-site-specific. See the 0.12→0.13 extension-author recipe. (#715)

    Before:

    const ref = descriptors.codecRefForColumn('document', 'embedding');

... (truncated)

Changelog

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

v0.13.0

This release makes namespaces a first-class part of the query surface, adds cross-contract foreign keys to the SQL ORM, makes many-to-many a validatable contract shape, introduces a per-object control policy (@@control) that decides what Prisma manages, ships domain enums backed by storage value-sets, and gives the migration CLI a unified graph-tree view across list / log / status / show. Telemetry also flips from opt-in to opt-out. A few changes require a one-time contract re-emit — all are covered by the linked upgrade recipes.

Breaking changes

  • Telemetry is now opt-out — anonymous CLI telemetry is collected by default and you opt out, where previously you opted in. Set PRISMA_NEXT_DISABLE_TELEMETRY=1 (or DO_NOT_TRACK=1) to turn it off. See docs/Telemetry.md for what is collected and every opt-out signal. (#676)

  • MTI variant tables materialize a base-PK link column — 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 a copy of the base table's primary-key column(s), a primary key over them, 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. Variants that share the base table (no own @@map) are unaffected. See the 0.12→0.13 upgrade 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"
    }
  ]
}

  • Contract storage IR moved to a namespace envelope — the SQL/Mongo storage IR is now keyed by namespace (storage.namespaces.<ns>.entries.<kind>), and cross-references are explicit { namespace, model } objects in domain. Consumer impact is mechanical: re-emit with prisma-next contract emit to pick up the new shape. No codemod or source change is required, but the contract's storageHash changes, so plan and apply a migration afterward. (#715)

  • Extension authors: codec-resolution SPI takes a leading namespaceId — CodecDescriptorRegistry.codecRefForColumn(table, column) is now codecRefForColumn(namespaceId, table, column), and the free codecRefForStorageColumn(storage, table, column) is now codecRefForStorageColumn(storage, namespaceId, table, column) (both in @prisma-next/sql-relational-core). Thread the namespace the table lives in through every call site that stamps codec onto AST nodes. There is no codemod — the right namespace is call-site-specific. See the 0.12→0.13 extension-author recipe. (#715)

    Before:

    const ref = descriptors.codecRefForColumn('document', 'embedding');

... (truncated)

Commits

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

Release notes

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

v0.13.0

This release makes namespaces a first-class part of the query surface, adds cross-contract foreign keys to the SQL ORM, makes many-to-many a validatable contract shape, introduces a per-object control policy (@@control) that decides what Prisma manages, ships domain enums backed by storage value-sets, and gives the migration CLI a unified graph-tree view across list / log / status / show. Telemetry also flips from opt-in to opt-out. A few changes require a one-time contract re-emit — all are covered by the linked upgrade recipes.

Breaking changes

  • Telemetry is now opt-out — anonymous CLI telemetry is collected by default and you opt out, where previously you opted in. Set PRISMA_NEXT_DISABLE_TELEMETRY=1 (or DO_NOT_TRACK=1) to turn it off. See docs/Telemetry.md for what is collected and every opt-out signal. (#676)

  • MTI variant tables materialize a base-PK link column — 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 a copy of the base table's primary-key column(s), a primary key over them, 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. Variants that share the base table (no own @@map) are unaffected. See the 0.12→0.13 upgrade 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"
    }
  ]
}

  • Contract storage IR moved to a namespace envelope — the SQL/Mongo storage IR is now keyed by namespace (storage.namespaces.<ns>.entries.<kind>), and cross-references are explicit { namespace, model } objects in domain. Consumer impact is mechanical: re-emit with prisma-next contract emit to pick up the new shape. No codemod or source change is required, but the contract's storageHash changes, so plan and apply a migration afterward. (#715)

  • Extension authors: codec-resolution SPI takes a leading namespaceId — CodecDescriptorRegistry.codecRefForColumn(table, column) is now codecRefForColumn(namespaceId, table, column), and the free codecRefForStorageColumn(storage, table, column) is now codecRefForStorageColumn(storage, namespaceId, table, column) (both in @prisma-next/sql-relational-core). Thread the namespace the table lives in through every call site that stamps codec onto AST nodes. There is no codemod — the right namespace is call-site-specific. See the 0.12→0.13 extension-author recipe. (#715)

    Before:

    const ref = descriptors.codecRefForColumn('document', 'embedding');

... (truncated)

Changelog

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

v0.13.0

This release makes namespaces a first-class part of the query surface, adds cross-contract foreign keys to the SQL ORM, makes many-to-many a validatable contract shape, introduces a per-object control policy (@@control) that decides what Prisma manages, ships domain enums backed by storage value-sets, and gives the migration CLI a unified graph-tree view across list / log / status / show. Telemetry also flips from opt-in to opt-out. A few changes require a one-time contract re-emit — all are covered by the linked upgrade recipes.

Breaking changes

  • Telemetry is now opt-out — anonymous CLI telemetry is collected by default and you opt out, where previously you opted in. Set PRISMA_NEXT_DISABLE_TELEMETRY=1 (or DO_NOT_TRACK=1) to turn it off. See docs/Telemetry.md for what is collected and every opt-out signal. (#676)

  • MTI variant tables materialize a base-PK link column — 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 a copy of the base table's primary-key column(s), a primary key over them, 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. Variants that share the base table (no own @@map) are unaffected. See the 0.12→0.13 upgrade 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_fk...
Description has been truncated

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 19, 2026
@dependabot dependabot Bot requested a review from a team as a code owner June 19, 2026 13:36
@dependabot @github

dependabot Bot commented on behalf of github Jun 19, 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.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 19, 2026
@changeset-bot

changeset-bot Bot commented Jun 19, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: bc6b440

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

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

Bumps the production-minor-patch group with 33 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.37.0` |
| [@rollup/rollup-linux-x64-gnu](https://github.com/rollup/rollup) | `4.60.4` | `4.62.0` |
| [@prisma-next/contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/contract) | `0.8.0` | `0.13.0` |
| [@prisma-next/family-sql](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/9-family) | `0.8.0` | `0.13.0` |
| [@prisma-next/framework-components](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/framework-components) | `0.8.0` | `0.13.0` |
| [@prisma-next/migration-tools](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/3-tooling/migration) | `0.8.0` | `0.13.0` |
| [@prisma-next/sql-contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/contract) | `0.8.0` | `0.13.0` |
| [@prisma-next/sql-operations](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/operations) | `0.8.0` | `0.13.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.13.0` |
| [@prisma-next/sql-runtime](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/5-runtime) | `0.8.0` | `0.13.0` |
| [@prisma-next/ts-render](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/ts-render) | `0.8.0` | `0.13.0` |
| [@prisma-next/utils](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/utils) | `0.8.0` | `0.13.0` |
| [@prisma-next/adapter-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/6-adapters/postgres) | `0.8.0` | `0.13.0` |
| [@prisma-next/driver-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/7-drivers/postgres) | `0.8.0` | `0.13.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.13.0` |
| [@prisma-next/target-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/3-targets/postgres) | `0.8.0` | `0.13.0` |
| [@cipherstash/protect-ffi](https://github.com/cipherstash/protectjs-ffi) | `0.23.0` | `0.26.0` |
| [@anthropic-ai/claude-agent-sdk](https://github.com/anthropics/claude-agent-sdk-typescript) | `0.3.143` | `0.3.177` |
| [@prisma-next/postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/postgres) | `0.8.0` | `0.13.0` |
| [@prisma-next/sql-orm-client](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/sql-orm-client) | `0.8.0` | `0.13.0` |
| @cipherstash/auth-darwin-arm64 | `0.38.0` | `0.39.0` |
| @cipherstash/auth-darwin-x64 | `0.38.0` | `0.39.0` |
| @cipherstash/auth-linux-arm64-gnu | `0.38.0` | `0.39.0` |
| @cipherstash/auth-linux-x64-gnu | `0.38.0` | `0.39.0` |
| @cipherstash/auth-linux-x64-musl | `0.38.0` | `0.39.0` |
| @cipherstash/auth-win32-x64-msvc | `0.38.0` | `0.39.0` |
| [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs) | `7.3.5` | `7.5.2` |
| [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.37.0
- [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.37.0/packages/node)

Updates `@rollup/rollup-linux-x64-gnu` from 4.60.4 to 4.62.0
- [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.62.0)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Updates `@cipherstash/auth-darwin-arm64` from 0.38.0 to 0.39.0

Updates `@cipherstash/auth-darwin-x64` from 0.38.0 to 0.39.0

Updates `@cipherstash/auth-linux-arm64-gnu` from 0.38.0 to 0.39.0

Updates `@cipherstash/auth-linux-x64-gnu` from 0.38.0 to 0.39.0

Updates `@cipherstash/auth-linux-x64-musl` from 0.38.0 to 0.39.0

Updates `@cipherstash/auth-win32-x64-msvc` from 0.38.0 to 0.39.0

Updates `@clerk/nextjs` from 7.3.5 to 7.5.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.5.2/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: "@anthropic-ai/claude-agent-sdk"
  dependency-version: 0.3.175
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/auth-darwin-arm64"
  dependency-version: 0.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/auth-darwin-x64"
  dependency-version: 0.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/auth-linux-arm64-gnu"
  dependency-version: 0.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/auth-linux-x64-gnu"
  dependency-version: 0.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/auth-linux-x64-musl"
  dependency-version: 0.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/auth-win32-x64-msvc"
  dependency-version: 0.39.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@cipherstash/protect-ffi"
  dependency-version: 0.26.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: "@clerk/nextjs"
  dependency-version: 7.5.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/adapter-postgres"
  dependency-version: 0.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/contract"
  dependency-version: 0.13.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.13.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.13.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.13.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.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/postgres"
  dependency-version: 0.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/utils"
  dependency-version: 0.13.0
  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: next
  dependency-version: 15.5.19
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- 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: posthog-node
  dependency-version: 5.36.17
  dependency-type: direct:production
  update-type: version-update:semver-minor
  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.16
  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
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/production-minor-patch-c0ad460c13 branch from fc7d151 to bc6b440 Compare June 21, 2026 22:16
@dependabot @github

dependabot Bot commented on behalf of github Jun 28, 2026

Copy link
Copy Markdown
Contributor Author

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

@dependabot dependabot Bot closed this Jun 28, 2026
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/production-minor-patch-c0ad460c13 branch June 28, 2026 22:15
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