Skip to content

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

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

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

Package From To
pg 8.20.0 8.22.0
@clack/prompts 1.4.0 1.6.0
posthog-node 5.34.2 5.38.2
@rollup/rollup-linux-x64-gnu 4.60.4 4.62.2
@prisma-next/contract 0.8.0 0.14.0
@prisma-next/family-sql 0.8.0 0.14.0
@prisma-next/framework-components 0.8.0 0.14.0
@prisma-next/migration-tools 0.8.0 0.14.0
@prisma-next/sql-contract 0.8.0 0.14.0
@prisma-next/sql-operations 0.8.0 0.14.0
@prisma-next/sql-relational-core 0.8.0 0.14.0
@prisma-next/sql-runtime 0.8.0 0.14.0
@prisma-next/ts-render 0.8.0 0.14.0
@prisma-next/utils 0.8.0 0.14.0
arktype 2.2.0 2.2.1
@prisma-next/adapter-postgres 0.8.0 0.14.0
@prisma-next/driver-postgres 0.8.0 0.14.0
@prisma-next/sql-contract-psl 0.8.0 0.14.0
@prisma-next/target-postgres 0.8.0 0.14.0
@cipherstash/protect-ffi 0.23.0 0.26.0
@stricli/core 1.2.7 1.2.8
uuid 14.0.0 14.0.1
@anthropic-ai/claude-agent-sdk 0.3.143 0.3.186
@prisma-next/postgres 0.8.0 0.14.0
@prisma-next/sql-orm-client 0.8.0 0.14.0
@clerk/nextjs 7.3.5 7.5.7
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.22.0

Changelog

Sourced from pg's changelog.

pg@8.22.0

pg@8.21.0

Commits

Updates @clack/prompts from 1.4.0 to 1.6.0

Release notes

Sourced from @​clack/prompts's releases.

@​clack/prompts@​1.6.0

Minor Changes

  • #568 f87933f Thanks @​florian-lefebvre! - Updates default formatter of note() to note dim lines anymore

    If you want the old behavior, provide a format() function:

    import { note } from '@clack/prompts';
+import { styleText } from 'node:util';
note(
'You can edit the file src/index.jsx',
'Next steps.'

{ format: (text) => styleText('dim', text) }
);

  • #567 cc6aab5 Thanks @​dreyfus92! - Add keyboard instruction footers to select, multiselect, and groupMultiselect in the active state, matching autocomplete. No option — always shown.

    • Patch Changes

    @​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',

    ... (truncated)

    Changelog

    Sourced from @​clack/prompts's changelog.

    1.6.0

    Minor Changes

    • #568 f87933f Thanks @​florian-lefebvre! - Updates default formatter of note() to note dim lines anymore

      If you want the old behavior, provide a format() function:

      import { note } from '@clack/prompts';
+import { styleText } from 'node:util';
note(
'You can edit the file src/index.jsx',
'Next steps.'

{ format: (text) => styleText('dim', text) }
);

  • #567 cc6aab5 Thanks @​dreyfus92! - Add keyboard instruction footers to select, multiselect, and groupMultiselect in the active state, matching autocomplete. No option — always shown.

    • Patch Changes

    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';

    ... (truncated)

    Commits
    • 0e70056 [ci] release (#562)
    • f87933f fix(prompts): do not dim note contents (#568)
    • cc6aab5 feat(prompts): add instructions footer for select, multi-select & `group-...
    • 02ae191 [ci] release (#549)
    • 56e9d67 docs: add jsdoc for date, limit-options, and messages (#546)
    • 030ba4d [ci] release (#539)
    • 83428ac feat: standard schema for validation (#543)
    • adb6af9 docs: add jsdoc for box, group, and group-multi-select (#542)
    • 3170ed9 docs: add jsdoc for autocomplete, confirm, and path prompts (#540)
    • 3dcb31a fix: spaces and uppercase characters in multiline input (#534)
    • See full diff in compare view

    Updates posthog-node from 5.34.2 to 5.38.2

    Release notes

    Sourced from posthog-node's releases.

    posthog-node@5.38.2

    5.38.2

    Patch Changes

    posthog-node@5.38.1

    5.38.1

    Patch Changes

    • #3886 e6d7fe2 Thanks @​marandaneto! - Stop sending deprecated no-op top-level type, library, and library_version fields in event batch payloads. Use properties.$lib and properties.$lib_version for SDK metadata; legacy queued library and library_version values are used as fallbacks when the official $ properties are missing. (2026-06-18)
    • Updated dependencies [e6d7fe2]:
      • @​posthog/core@​1.35.2

    posthog-node@5.38.0

    5.38.0

    Minor Changes

    • #3845 a0553b3 Thanks @​marandaneto! - Add setPersonProperties() and unsetPersonProperties() helpers to manage person properties from the Node.js SDK. (2026-06-16)

    Patch Changes

    Changelog

    Sourced from posthog-node's changelog.

    5.38.2

    Patch Changes

    5.38.1

    Patch Changes

    • #3886 e6d7fe2 Thanks @​marandaneto! - Stop sending deprecated no-op top-level type, library, and library_version fields in event batch payloads. Use properties.$lib and properties.$lib_version for SDK metadata; legacy queued library and library_version values are used as fallbacks when the official $ properties are missing. (2026-06-18)
    • Updated dependencies [e6d7fe2]:
      • @​posthog/core@​1.35.2

    5.38.0

    Minor Changes

    • #3845 a0553b3 Thanks @​marandaneto! - Add setPersonProperties() and unsetPersonProperties() helpers to manage person properties from the Node.js SDK. (2026-06-16)

    Patch Changes

    5.37.1

    Patch Changes

    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

    ... (truncated)

    Commits
    • b0bd00f chore: update versions and lockfile [version bump]
    • 6b21f77 fix: validate custom event UUIDs (#3903)
    • 229efff chore: update versions and lockfile [version bump]
    • e6d7fe2 fix: remove ignored batch metadata fields (#3886)
    • f495510 chore: update versions and lockfile [version bump]
    • bd07ec4 feat(flags): add disableRemoteFeatureFlags option and runtime updateFlags (#3...
    • 4ff3bb3 chore: update versions and lockfile [version bump]
    • a0553b3 feat(node): add person property helpers (#3845)
    • 70d3dde chore: Generate versioned references only on release (#3858)
    • 47aea13 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.2

    Release notes

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

    v4.62.2

    4.62.2

    2026-06-19

    Bug Fixes

    • Do not add spurious side-effect-free external imports to chunks when using minChunkSize (#6411)

    Pull Requests

    v4.62.1

    4.62.1

    2026-06-19

    Bug Fixes

    • Preserve multipart file extensions when deconflicting output chunks (#6408)
    • Fix an issue where getLogFilter would match additional logs (#6415)

    Pull Requests

    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

    ... (truncated)

    Changelog

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

    4.62.2

    2026-06-19

    Bug Fixes

    • Do not add spurious side-effect-free external imports to chunks when using minChunkSize (#6411)

    Pull Requests

    4.62.1

    2026-06-19

    Bug Fixes

    • Preserve multipart file extensions when deconflicting output chunks (#6408)
    • Fix an issue where getLogFilter would match additional logs (#6415)

    Pull Requests

    4.62.0

    2026-06-13

    Features

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

    Pull Requests

    ... (truncated)

    Commits
    • 8faa187 4.62.2
    • a38a795 refactor(rust/parser_ast): extract property AstConverter write buffer kind lo...
    • 6cc5c31 Skip side-effect-free external imports when hoisting is disabled (#6411)
    • caacf70 4.62.1
    • d1e8297 Add missing ignore
    • 1ba1fc2 fix: insert conflict numbers before first extension in multi-extension filena...
    • 532bd0a Use import attributes for importing JSON (#6393)
    • 2cd8194 fix: advance value past wildcard prefix before suffix check in getLogFilter (...
    • dfac590 fix(deps): update minor/patch updates (#6418)
    • 1d6db3d chore(deps): update dependency eslint-plugin-unicorn to v66 (#6419)
    • Additional commits viewable in compare view

    Updates @prisma-next/contract from 0.8.0 to 0.14.0

    Release notes

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

    v0.14.0

    This release reshapes the enum surface (PSL enum is now a domain concept backed by a value-set CHECK constraint, not a native Postgres type), makes the SQL builder always-qualified by namespace, adds native UUID storage on Postgres, ships a new fault-tolerant PSL parser, completes the read side of many-to-many (correlated includes plus some / every / none filters through the junction), and adds a Supabase façade alongside several runtime-class renamings. Most breaking changes have a matching codemod or upgrade recipe.

    Breaking changes

    • PSL enum becomes the domain enum — an enum block now authors a text-class column whose value set is enforced by a CHECK constraint, not a native CREATE TYPE … AS ENUM. Each block must declare @@type("<codec-id>") (typically pg/text@1) and map members to database values with Name = "value". The transitional enum2 keyword is retired (rename to enum — emitted contract is identical). Native enum machinery is deleted: enumType(name, values[]) / enumColumn from @prisma-next/adapter-postgres/column-types, the pg/enum@1 codec, and adoption of native enum types in contract infer are all gone. Databases carrying a native enum type need a one-time converting migration (ALTER column to text USING ::text, add the value-set CHECK, DROP TYPE) — contract infer refuses native enum types and names them. See the 0.13→0.14 upgrade recipe and the extension-author recipe. (#817)

      Before:

      enum user_type {
  admin
  user
}

      After:

      enum user_type {
  @@type("pg/text@1")
  admin = "admin"
  user  = "user"
}

    • Query builder and ORM are always qualified by namespace — the flat by-bare-name accessors are removed at the builder layer; the Postgres facade exposes the namespaced surface. On Postgres, db.sql.<table> becomes db.sql.<namespace>.<table> and db.orm.<Model> becomes db.orm.<namespace>.<Model> (public for a standard single-schema project). Direct builder calls (sql.<table>, orm.<Model>) migrate the same way. SQLite and Mongo are unaffected — their single-namespace facade keeps the flat surface working. No codemod: the correct namespace is the one each table/model is declared in. The generated contract.d.ts also drops the flat top-level export type Models — read models per-namespace as Contract['domain']['namespaces']['<namespace>']['models'] and re-emit. See the 0.13→0.14 upgrade recipe. (#778)

      Before:

      const users = await db.sql.user.select('id', 'email').build().execute();
const alice = await db.orm.User.find({ where: { id } });

      After:

      const users = await db.sql.public.user.select('id', 'email').build().execute();
const alice = await db.orm.public.User.find({ where: { id } });

    • UUID field presets renamed by storage encoding — field.uuid() → field.uuidString(), field.id.uuidv4() → field.id.uuidv4String(), field.id.uuidv7() → field.id.uuidv7String(). The new names describe the char(36) storage encoding (the emitted codec, sql/char@1, is unchanged). Postgres-native uuid columns use the new field.uuidNative() / field.id.uuidv4Native() / field.id.uuidv7Native() presets from @prisma-next/postgres/contract-builder. The rename is mechanical — a colocated codemod ships in the 0.13→0.14 upgrade recipe. (#810)

      Before:

      id: field.id.uuidv7(),
externalId: field.uuid(),

    ... (truncated)

    Changelog

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

    v0.14.0

    This release reshapes the enum surface (PSL enum is now a domain concept backed by a value-set CHECK constraint, not a native Postgres type), makes the SQL builder always-qualified by namespace, adds native UUID storage on Postgres, ships a new fault-tolerant PSL parser, completes the read side of many-to-many (correlated includes plus some / every / none filters through the junction), and adds a Supabase façade alongside several runtime-class renamings. Most breaking changes have a matching codemod or upgrade recipe.

    Breaking changes

    • PSL enum becomes the domain enum — an enum block now authors a text-class column whose value set is enforced by a CHECK constraint, not a native CREATE TYPE … AS ENUM. Each block must declare @@type("<codec-id>") (typically pg/text@1) and map members to database values with Name = "value". The transitional enum2 keyword is retired (rename to enum — emitted contract is identical). Native enum machinery is deleted: enumType(name, values[]) / enumColumn from @prisma-next/adapter-postgres/column-types, the pg/enum@1 codec, and adoption of native enum types in contract infer are all gone. Databases carrying a native enum type need a one-time converting migration (ALTER column to text USING ::text, add the value-set CHECK, DROP TYPE) — contract infer refuses native enum types and names them. See the 0.13→0.14 upgrade recipe and the extension-author recipe. (#817)

      Before:

      enum user_type {
  admin
  user
}

      After:

      enum user_type {
  @@type("pg/text@1")
  admin = "admin"
  user  = "user"
}

    • Query builder and ORM are always qualified by namespace — the flat by-bare-name accessors are removed at the builder layer; the Postgres facade exposes the namespaced surface. On Postgres, db.sql.<table> becomes db.sql.<namespace>.<table> and db.orm.<Model> becomes db.orm.<namespace>.<Model> (public for a standard single-schema project). Direct builder calls (sql.<table>, orm.<Model>) migrate the same way. SQLite and Mongo are unaffected — their single-namespace facade keeps the flat surface working. No codemod: the correct namespace is the one each table/model is declared in. The generated contract.d.ts also drops the flat top-level export type Models — read models per-namespace as Contract['domain']['namespaces']['<namespace>']['models'] and re-emit. See the 0.13→0.14 upgrade recipe. (#778)

      Before:

      const users = await db.sql.user.select('id', 'email').build().execute();
const alice = await db.orm.User.find({ where: { id } });

      After:

      const users = await db.sql.public.user.select('id', 'email').build().execute();
const alice = await db.orm.public.User.find({ where: { id } });

    • UUID field presets renamed by storage encoding — field.uuid() → field.uuidString(), field.id.uuidv4() → field.id.uuidv4String(), field.id.uuidv7() → field.id.uuidv7String(). The new names describe the char(36) storage encoding (the emitted codec, sql/char@1, is unchanged). Postgres-native uuid columns use the new field.uuidNative() / field.id.uuidv4Native() / field.id.uuidv7Native() presets from @prisma-next/postgres/contract-builder. The rename is mechanical — a colocated codemod ships in the 0.13→0.14 upgrade recipe. (#810)

      Before:

      id: field.id.uuidv7(),
externalId: field.uuid(),

    ... (truncated)

    Commits

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

    Release notes

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

    v0.14.0

    This release reshapes the enum surface (PSL enum is now a domain concept backed by a value-set CHECK constraint, not a native Postgres type), makes the SQL builder always-qualified by namespace, adds native UUID storage on Postgres, ships a new fault-tolerant PSL parser, completes the read side of many-to-many (correlated includes plus some / every / none filters through the junction), and adds a Supabase façade alongside several runtime-class renamings. Most breaking changes have a matching codemod or upgrade recipe.

    Breaking changes

    • PSL enum becomes the domain enum — an enum block now authors a text-class column whose value set is enforced by a CHECK constraint, not a native CREATE TYPE … AS ENUM. Each block must declare @@type("<codec-id>") (typically pg/text@1) and map members to database values with Name = "value". The transitional enum2 keyword is retired (rename to enum — emitted contract is identical). Native enum machinery is deleted: enumType(name, values[]) / enumColumn from @prisma-next/adapter-postgres/column-types, the pg/enum@1 codec, and adoption of native enum types in contract infer are all gone. Databases carrying a native enum type need a one-time converting migration (ALTER column to text USING ::text, add the value-set CHECK, DROP TYPE) — contract infer refuses native enum types and names them. See the 0.13→0.14 upgrade recipe and the extension-author recipe. (#817)

      Before:

      enum user_type {
  admin
  user
}

      After:

      enum user_type {
  @@type("pg/text@1")
  admin = "admin"
  user  = "user"
}

    • Query builder and ORM are always qualified by namespace — the flat by-bare-name accessors are removed at the builder layer; the Postgres facade exposes the namespaced surface. On Postgres, db.sql.<table> becomes db.sql.<namespace>.<table> and db.orm.<Model> becomes db.orm.<namespace>.<Model> (public for a standard single-schema project). Direct builder calls (sql.<table>, orm.<Model>) migrate the same way. SQLite and Mongo are unaffected — their single-namespace facade keeps the flat surface working. No codemod: the correct namespace is the one each table/model is declared in. The generated contract.d.ts also drops the flat top-level export type Models — read models per-namespace as Contract['domain']['namespaces']['<namespace>']['models'] and re-emit. See the 0.13→0.14 upgrade recipe. (#778)

      Before:

      const users = await db.sql.user.select('id', 'email').build().execute();
const alice = await db.orm.User.find({ where: { id } });

      After:

      const users = await db.sql.public.user.select('id', 'email').build().execute();
const alice = await db.orm.public.User.find({ where: { id } });

    • UUID field presets renamed by storage encoding — field.uuid() → field.uuidString(), field.id.uuidv4() → field.id.uuidv4String(), field.id.uuidv7() → field.id.uuidv7String(). The new names describe the char(36) storage encoding (the emitted codec, sql/char@1, is unchanged). Postgres-native uuid columns use the new field.uuidNative() / field.id.uuidv4Native() / field.id.uuidv7Native() presets from @prisma-next/postgres/contract-builder. The rename is mechanical — a colocated codemod ships in the 0.13→0.14 upgrade recipe. (#810)

      Before:

      id: field.id.uuidv7(),
externalId: field.uuid(),

    ... (truncated)

    Changelog

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

    v0.14.0

    This release reshapes the enum surface (PSL enum is now a domain concept backed by a value-set CHECK constraint, not a native Postgres type), makes the SQL builder always-qualified by namespace, adds native UUID storage on Postgres, ships a new fault-tolerant PSL parser, completes the read side of many-to-many (correlated includes plus some / every / none filters through the junction), and adds a Supabase façade alongside several runtime-class renamings. Most breaking changes have a matching codemod or upgrade recipe.

    Breaking changes

    • PSL enum becomes the domain enum — an enum block now authors a text-class column whose value set is enforced by a CHECK constraint, not a native CREATE TYPE … AS ENUM. Each block must declare @@type("<codec-id>") (typically pg/text@1) and map members to database values with Name = "value". The transitional enum2 keyword is retired (rename to enum — emitted contract is identical). Native enum machinery is deleted: enumType(name, values[]) / enumColumn from @prisma-next/adapter-postgres/column-types, the pg/enum@1 codec, and adoption of native enum types in contract infer are all gone. Databases carrying a native enum type need a one-time converting migration (ALTER column to text USING ::text, add the value-set CHECK, DROP TYPE) — contract infer refuses native enum types and names them. See the 0.13→0.14 upgrade recipe and the extension-author recipe. (#817)

      Before:

      enum user_type {
  admin
  user
}

      After:

      enum user_type {
  @@type("pg/text@1")
  admin = "admin"
  user  = "user"
}

    • Query builder and ORM are always qualified by namespace — the flat by-bare-name accessors are removed at the builder layer; the Postgres facade exposes the namespaced surface. On Postgres, db.sql.<table> becomes db.sql.<namespace>.<table> and db.orm.<Model> becomes db.orm.<namespace>.<Model> (public for a standard single-schema project). Direct builder calls (sql.<table>, orm.<Model>) migrate the same way. SQLite and Mongo are unaffected — their single-namespace facade keeps the flat surface working. No codemod: the correct namespace is the one each table/model is declared in. The generated contract.d.ts also drops the flat top-level export type Models — read models per-namespace as Contract['domain']['namespaces']['<namespace>']['models'] and re-emit. See the 0.13→0.14 upgrade recipe. (#778)

      Before:

      const users = await db.sql.user.select('id', 'email').build().execute();
const alice = await db.orm.User.find({ where: { id } });

      After:

      const users = await db.sql.public.user.select('id', 'email').build().execute();
const alice = await db.orm.public.User.find({ where: { id } });

    • UUID field presets renamed by storage encoding — field.uuid() → field.uuidString(), field.id.uuidv4() → field.id.uuidv4String(), field.id.uuidv7() → field.id.uuidv7String(). The new names describe the char(36) storage encoding (the emitted codec, sql/char@1, is unchanged). Postgres-native uuid columns use the new field.uuidNative() / field.id.uuidv4Native() / field.id.uuidv7Native() presets from @prisma-next/postgres/contract-builder. The rename is mechanical — a colocated codemod ships in the 0.13→0.14 upgrade recipe. (#810)

      Before:

      id: field.id.uuidv7(),
externalId: field.uuid(),

    ... (truncated)

    Commits

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

    Release notes

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

    v0.14.0

    This release reshapes the enum surface (PSL enum is now a domain concept backed by a value-set CHECK constraint, not a native Postgres type), makes the SQL builder always-qualified by namespace, adds native UUID storage on Postgres, ships a new fault-tolerant PSL parser, completes the read side of many-to-many (correlated includes plus some / every / none filters through the junction), and adds a Supabase façade alongside several runtime-class renamings. Most breaking changes have a matching codemod or upgrade recipe.

    Breaking changes

    • PSL enum becomes the domain enum — an enum block now authors a text-class column whose value set is enforced by a CHECK constraint, not a native CREATE TYPE … AS ENUM. Each block must declare @@type("<codec-id>") (typically pg/text@1) and map members to database values with Name = "value". The transitional enum2 keyword is retired (rename to enum — emitted contract is identical). Native enum machinery is deleted: enumType(name, values[]) / enumColumn from @prisma-next/adapter-postgres/column-types, the pg/enum@1 codec, and adoption of native enum types in contract infer are all gone. Databases carrying a native enum type need a one-time converting migration (ALTER column to text USING ::text, add the value-set CHECK, DROP TYPE) — contract infer refuses native enum types and names them. See the 0.13→0.14 upgrade recipe and the extension-author recipe. (#817)

      Before:

      enum user_type {
  admin
  user
}

      After:

      enum user_type {
  @@type("pg/text@1")
  admin = "admin"
  user  = "user"
}

    • Query builder and ORM are always qualified by namespace — the flat by-bare-name accessors are removed at the builder layer; the Postgres facade exposes the namespaced surface. On Postgres, db.sql.<table> becomes db.sql.<namespace>.<table> and d...

      Description has been truncated

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

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

| Package | From | To |
| --- | --- | --- |
| [pg](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg) | `8.20.0` | `8.22.0` |
| [@clack/prompts](https://github.com/bombshell-dev/clack/tree/HEAD/packages/prompts) | `1.4.0` | `1.6.0` |
| [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.34.2` | `5.38.2` |
| [@rollup/rollup-linux-x64-gnu](https://github.com/rollup/rollup) | `4.60.4` | `4.62.2` |
| [@prisma-next/contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/contract) | `0.8.0` | `0.14.0` |
| [@prisma-next/family-sql](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/9-family) | `0.8.0` | `0.14.0` |
| [@prisma-next/framework-components](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/framework-components) | `0.8.0` | `0.14.0` |
| [@prisma-next/migration-tools](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/3-tooling/migration) | `0.8.0` | `0.14.0` |
| [@prisma-next/sql-contract](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/contract) | `0.8.0` | `0.14.0` |
| [@prisma-next/sql-operations](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/1-core/operations) | `0.8.0` | `0.14.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.14.0` |
| [@prisma-next/sql-runtime](https://github.com/prisma/prisma-next/tree/HEAD/packages/2-sql/5-runtime) | `0.8.0` | `0.14.0` |
| [@prisma-next/ts-render](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/1-core/ts-render) | `0.8.0` | `0.14.0` |
| [@prisma-next/utils](https://github.com/prisma/prisma-next/tree/HEAD/packages/1-framework/0-foundation/utils) | `0.8.0` | `0.14.0` |
| [arktype](https://github.com/arktypeio/arktype/tree/HEAD/ark/type) | `2.2.0` | `2.2.1` |
| [@prisma-next/adapter-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/6-adapters/postgres) | `0.8.0` | `0.14.0` |
| [@prisma-next/driver-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/7-drivers/postgres) | `0.8.0` | `0.14.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.14.0` |
| [@prisma-next/target-postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-targets/3-targets/postgres) | `0.8.0` | `0.14.0` |
| [@cipherstash/protect-ffi](https://github.com/cipherstash/protectjs-ffi) | `0.23.0` | `0.26.0` |
| [@stricli/core](https://github.com/bloomberg/stricli) | `1.2.7` | `1.2.8` |
| [uuid](https://github.com/uuidjs/uuid) | `14.0.0` | `14.0.1` |
| [@anthropic-ai/claude-agent-sdk](https://github.com/anthropics/claude-agent-sdk-typescript) | `0.3.143` | `0.3.186` |
| [@prisma-next/postgres](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/postgres) | `0.8.0` | `0.14.0` |
| [@prisma-next/sql-orm-client](https://github.com/prisma/prisma-next/tree/HEAD/packages/3-extensions/sql-orm-client) | `0.8.0` | `0.14.0` |
| [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs) | `7.3.5` | `7.5.7` |
| [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.22.0
- [Changelog](https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md)
- [Commits](https://github.com/brianc/node-postgres/commits/pg@8.22.0/packages/pg)

Updates `@clack/prompts` from 1.4.0 to 1.6.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.6.0/packages/prompts)

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

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

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

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

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

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

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

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

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

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

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

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

Updates `arktype` from 2.2.0 to 2.2.1
- [Release notes](https://github.com/arktypeio/arktype/releases)
- [Changelog](https://github.com/arktypeio/arktype/blob/main/ark/type/CHANGELOG.md)
- [Commits](https://github.com/arktypeio/arktype/commits/arktype@2.2.1/ark/type)

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

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

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

Updates `@prisma-next/target-postgres` from 0.8.0 to 0.14.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.14.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 `@stricli/core` from 1.2.7 to 1.2.8
- [Release notes](https://github.com/bloomberg/stricli/releases)
- [Changelog](https://github.com/bloomberg/stricli/blob/main/CHANGELOG.md)
- [Commits](bloomberg/stricli@v1.2.7...v1.2.8)

Updates `uuid` from 14.0.0 to 14.0.1
- [Release notes](https://github.com/uuidjs/uuid/releases)
- [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md)
- [Commits](uuidjs/uuid@v14.0.0...v14.0.1)

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

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

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

Updates `@clerk/nextjs` from 7.3.5 to 7.5.7
- [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.7/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.22.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@clack/prompts"
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: posthog-node
  dependency-version: 5.38.2
  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.62.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/contract"
  dependency-version: 0.14.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.14.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.14.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.14.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.14.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.14.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.14.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.14.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.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/utils"
  dependency-version: 0.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: arktype
  dependency-version: 2.2.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/adapter-postgres"
  dependency-version: 0.14.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.14.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.14.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.14.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: "@stricli/core"
  dependency-version: 1.2.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: uuid
  dependency-version: 14.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: "@anthropic-ai/claude-agent-sdk"
  dependency-version: 0.3.186
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-patch
- dependency-name: "@prisma-next/postgres"
  dependency-version: 0.14.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.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-patch
- dependency-name: "@clerk/nextjs"
  dependency-version: 7.5.7
  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 requested a review from a team as a code owner June 30, 2026 10:11
    @dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 30, 2026
    @dependabot @github

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

    Copy link
    Copy Markdown

    ⚠️ No Changeset found

    Latest commit: e62c077

    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