chore(deps): bump the npm-dependencies group across 1 directory with 29 updates

[dependabot]

Bumps the npm-dependencies group with 29 updates in the / directory:

Package	From	To
@fastify/helmet	13.1.0	13.1.1
@fastify/static	10.1.2	10.1.3
@nestjs/cache-manager	3.1.3	12.0.0
@nestjs/common	11.1.28	12.0.1
@nestjs/config	4.0.4	12.0.0
@nestjs/core	11.1.28	12.0.1
@nestjs/platform-fastify	11.1.28	12.0.1
@nestjs/swagger	11.4.6	12.0.0
@prisma/adapter-pg	7.9.0	7.10.0
@prisma/client	7.9.0	7.10.0
@scalar/nestjs-api-reference	1.2.11	1.2.16
fastify	5.10.0	5.12.1
ioredis	5.11.1	6.0.0
nestjs-i18n	10.8.4	10.8.5
nestjs-zod	5.4.0	5.5.0
pg	8.22.0	8.23.0
@types/pg	8.20.0	8.23.1
prisma	7.9.0	7.9.1
@biomejs/biome	2.5.2	2.5.11
@commitlint/cli	21.2.0	21.2.2
@commitlint/config-conventional	21.2.0	21.2.2
@nestjs/cli	11.0.23	12.0.0
@nestjs/schematics	11.1.0	12.0.0
@nestjs/testing	11.1.28	12.0.1
@types/node	26.1.0	26.4.0
@types/supertest	7.2.0	7.2.1
lint-staged	17.0.8	17.4.1
ts-jest	29.4.11	29.4.12
typescript	6.0.3	7.0.2

Updates @fastify/helmet from 13.1.0 to 13.1.1

Release notes

Sourced from @​fastify/helmet's releases.

v13.1.1

What's Changed

• test: fix CSP header order assertions for helmet@8.3.x by @​Tony133 in fastify/fastify-helmet#318
• ci: pin actions to commit-hash by @​Fdawgs in fastify/fastify-helmet#316
• chore: bump c8 from 11.0.0 to 12.0.0 by @​dependabot[bot] in fastify/fastify-helmet#317
• chore: bump fastify/workflows/.github/workflows/lock-threads.yml from 6.0.0 to 7.0.0 by @​dependabot[bot] in fastify/fastify-helmet#320
• chore: bump fastify/workflows/.github/workflows/plugins-ci.yml from 6.0.0 to 7.0.0 by @​dependabot[bot] in fastify/fastify-helmet#321
• chore(.npmrc): add min-release-age by @​Fdawgs in fastify/fastify-helmet#319

Full Changelog: fastify/fastify-helmet@v13.1.0...v13.1.1

Commits

• 8854d49 Bumped v13.1.1
• c4bbcb2 chore(.npmrc): add min-release-age (#319)
• 8406fa8 chore: bump fastify/workflows/.github/workflows/plugins-ci.yml (#321)
• d8da457 chore: bump fastify/workflows/.github/workflows/lock-threads.yml (#320)
• 655cd3a chore: bump c8 from 11.0.0 to 12.0.0 (#317)
• 928d9b5 ci: pin actions to commit-hash
• 7c9cda3 test: fix CSP header order assertions for helmet@8.3.x
• See full diff in compare view

Maintainer changes

This version was pushed to npm by tony133, a new releaser for @​fastify/helmet since your current version.

Updates @fastify/static from 10.1.2 to 10.1.3

Release notes

Sourced from @​fastify/static's releases.

v10.1.3

What's Changed

• chore: bump c8 from 11.0.0 to 12.0.0 by @​dependabot[bot] in fastify/fastify-static#602
• chore(.npmrc): add min-release-age by @​Fdawgs in fastify/fastify-static#603
• chore: bump fastify/workflows/.github/workflows/lock-threads.yml from 6.0.0 to 7.0.0 by @​dependabot[bot] in fastify/fastify-static#605

Full Changelog: fastify/fastify-static@v10.1.2...v10.1.3

Commits

• fd3fe0d Bumped v10.1.3
• fabaf1b fix: preserve absolute Windows sendFile paths (#606)
• a2f192b Merge commit from fork
• b9a6405 chore: bump fastify/workflows/.github/workflows/lock-threads.yml (#605)
• aad18dc chore(.npmrc): add min-release-age
• 94d75c0 chore: bump c8 from 11.0.0 to 12.0.0 (#602)
• See full diff in compare view

Updates @nestjs/cache-manager from 3.1.3 to 12.0.0

Release notes

Sourced from @​nestjs/cache-manager's releases.

Release 12.0.0

What's Changed

@nestjs/cache-manager is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 4.x — 3.1.3 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root:

import { CacheModule, CacheInterceptor, CacheKey, CacheTTL } from '@nestjs/cache-manager';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, CommonJS consumers can keep using require('@nestjs/cache-manager') unchanged — the exports map points both import and require at the same ESM build, and Node loads it natively.

This is why the supported Node range is now enforced via engines:

"engines": {
  "node": "^20.19.0 || ^22.12.0 || >=24.0.0"
}

Those are the Node versions where require(esm) is available unflagged. On older Node versions, requiring this package from CommonJS will fail with ERR_REQUIRE_ESM.

Upgrading

npm i @nestjs/cache-manager@12

Checklist:

• Ensure you're on Node ^20.19.0, ^22.12.0, or >=24.0.0.
• Replace any deep imports (e.g. @nestjs/cache-manager/dist/...) with root imports.
• No changes needed to CacheModule.register() / registerAsync(), interceptors, or decorators.

Commits

• 661bc00 chore(): release v12.0.0
• 085ae1a chore: upgrade to v12
• 3a07e0b chore(deps): update dependency oxlint to v1.80.0 (#1152)
• 5f1ad64 chore(deps): update nest monorepo to v11.2.3 (#1151)
• f34fe5a chore(deps): update dependency vite to v8.2.2 (#1150)
• 288ea83 Merge pull request #1149 from miso-kyoungminkim/cachettl-ms-comment
• 9c08ea6 chore(deps): update dependency oxlint to v1.79.0 (#1148)
• f2b60ee docs(cache-ttl): clarify that ttl is in milliseconds
• f12d697 chore(deps): update dependency vitest to v4.1.11 (#1147)
• d0030ab Merge pull request #1067 from nestjs/chore/esm-migration
• Additional commits viewable in compare view

Updates @nestjs/common from 11.1.28 to 12.0.1

Release notes

Sourced from @​nestjs/common's releases.

v12.0.0

NestJS v12.0.0

NestJS 12 is centered around ESM-ready packages, first-class Standard Schema support for validation and serialization, a rebuilt CLI, and native observability through the new @nestjs/observe SDK.

Existing CommonJS applications keep working — migrating your own code to ESM is entirely optional.

📖 Full migration guide

---

Upgrading

Upgrade the CLI first, since the upgrade command ships with it:

npm i -g @nestjs/cli@latest

Then, from the root of your project:

nest upgrade

nest upgrade moves every @nestjs/* package to its v12-compatible major at once and applies the mechanical parts of the migration for you — nest-cli.json webpack options, the GraphQL playground → graphiql rename and subscriptions transport swap, the NATS package replacement, @nestjs/config validation options, Jest and Joi bumps — then prints a report of everything it changed and everything you still need to review by hand. Run it with --dry-run first to see that report without touching your files.

It deliberately does not migrate your project to ESM, Vitest, or oxlint. Those are the defaults for newly generated projects; existing projects adopt them on their own schedule.

Node.js: v12 requires Node.js v20.19+ or v22.12+. Both require(esm) and the ESM packages depend on it; the upgrade command refuses to run on older releases (including the 21.x line). The latest active LTS is recommended.

---

Highlights

ESM packages

All core Nest packages now ship as ESM. Thanks to require(esm) in modern Node.js, most existing CommonJS applications continue to work without a rewrite. Review custom bootstrapping scripts, build tooling, and test runners if they assume CommonJS-only packages.

nest new now asks whether to scaffold a CommonJS or an ESM project.

Standard Schema validation

Route parameter decorators — @Body(), @Query(), @Param(), @RawBody() — accept a new schema option, designed for Standard Schema compatible libraries such as Zod, Valibot, and ArkType:

@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
  return this.usersService.create(body);
}
</tr></table> 

... (truncated)

Commits

• 4c751c5 chore(release): publish v12.0.1 release
• 6494a6c chore(release): publish v12.0.0 release
• e306724 fix(deps): update dependency file-type to v22
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• e255755 chore: resolve conflicts, minor fixes
• 5d1b19b Merge branch 'master' into v12.0.0
• f2a7e4b chore(release): publish v11.2.0 release
• b2e7fb5 Merge pull request #17469 from nestjs/feat/sse-signal
• 6498f11 feat: signal should finalize in every case
• Additional commits viewable in compare view

Updates @nestjs/config from 4.0.4 to 12.0.0

Release notes

Sourced from @​nestjs/config's releases.

12.0.0

What's Changed

@nestjs/config is now a native ES module, environment validation is built on Standard Schema instead of Joi-specific code, and the major version is aligned with the Nest 12 release line (there is no 5.x — 4.0.4 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root.

// ✅
import { ConfigModule, ConfigService } from '@nestjs/config';
// ❌ no longer resolvable
import { ConfigService } from '@​nestjs/config/dist/config.service';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support (Node 20.19+ / 22.12+), a CommonJS app can keep using require('@nestjs/config') unchanged.

Validation is now Standard Schema based

validationSchema accepts any schema implementing the Standard Schema spec — Zod (v3, v4, v4-mini), Valibot, ArkType, Joi 18+, and anything else that adopts it. There is no longer any Joi-specific code path in the module, and Joi is no longer implied as the validation library.

ConfigModule.forRoot({
  validationSchema: z.object({
    PORT: z.coerce.number().default(3000),
    DATABASE_NAME: z.string(),
  }),
});

Joi keeps working — it implements Standard Schema as of v18 — and the historical abortEarly: false / allowUnknown: true defaults are still applied automatically for Joi schemas, so existing Joi setups behave as before.

Breaking: validationOptions shape

Options are now the Standard Schema Options object, and library-specific settings move under libraryOptions:

// Before (4.x)
validationOptions: { allowUnknown: false, abortEarly: true }
// Now (12.x)
validationOptions: { libraryOptions: { allowUnknown: false, abortEarly: true } }

The generic parameter changed accordingly: ConfigModuleOptions<ValidationOptions extends StandardSchemaV1.Options>, and validationSchema is typed as StandardSchemaV1 rather than any — a schema that does not implement the spec is now a compile-time error instead of a runtime one.

... (truncated)

Commits

• 269312f chore(): release v12.0.0
• 5748c1f chore: upgrade to v12
• d833a6a chore(deps): update dependency oxlint to v1.80.0 (#2408)
• 4555cbc chore(deps): update nest monorepo to v11.2.3 (#2407)
• 4561739 chore(deps): update dependency vite to v8.2.2 (#2406)
• 0fc13bb chore(deps): update dependency joi to v18.2.5 (#2405)
• 22642b8 chore(deps): update dependency oxlint to v1.79.0 (#2404)
• d3a7dd5 chore(deps): update dependency vitest to v4.1.11 (#2403)
• 8c87973 chore(deps): update dependency zod to v4.4.3 (#2402)
• 949dc88 Merge pull request #2356 from nestjs/renovate/cimg-node-24.x
• Additional commits viewable in compare view

Updates @nestjs/core from 11.1.28 to 12.0.1

Release notes

Sourced from @​nestjs/core's releases.

v12.0.0

NestJS v12.0.0

NestJS 12 is centered around ESM-ready packages, first-class Standard Schema support for validation and serialization, a rebuilt CLI, and native observability through the new @nestjs/observe SDK.

Existing CommonJS applications keep working — migrating your own code to ESM is entirely optional.

📖 Full migration guide

---

Upgrading

Upgrade the CLI first, since the upgrade command ships with it:

npm i -g @nestjs/cli@latest

Then, from the root of your project:

nest upgrade

nest upgrade moves every @nestjs/* package to its v12-compatible major at once and applies the mechanical parts of the migration for you — nest-cli.json webpack options, the GraphQL playground → graphiql rename and subscriptions transport swap, the NATS package replacement, @nestjs/config validation options, Jest and Joi bumps — then prints a report of everything it changed and everything you still need to review by hand. Run it with --dry-run first to see that report without touching your files.

It deliberately does not migrate your project to ESM, Vitest, or oxlint. Those are the defaults for newly generated projects; existing projects adopt them on their own schedule.

Node.js: v12 requires Node.js v20.19+ or v22.12+. Both require(esm) and the ESM packages depend on it; the upgrade command refuses to run on older releases (including the 21.x line). The latest active LTS is recommended.

---

Highlights

ESM packages

All core Nest packages now ship as ESM. Thanks to require(esm) in modern Node.js, most existing CommonJS applications continue to work without a rewrite. Review custom bootstrapping scripts, build tooling, and test runners if they assume CommonJS-only packages.

nest new now asks whether to scaffold a CommonJS or an ESM project.

Standard Schema validation

Route parameter decorators — @Body(), @Query(), @Param(), @RawBody() — accept a new schema option, designed for Standard Schema compatible libraries such as Zod, Valibot, and ArkType:

@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
  return this.usersService.create(body);
}
</tr></table> 

... (truncated)

Commits

• 4c751c5 chore(release): publish v12.0.1 release
• 3c25112 chore: update peer deps
• 6494a6c chore(release): publish v12.0.0 release
• c9d59f2 chore: expose missing internals
• 45485b5 fix(core): circular durable providers issue #17562
• f94e9eb fix(core): preserve middleware arity and harden instance decorator
• 1dcbc25 fix(core): instrument midldeware issue #17554
• f5bf4dd docs(core): update Mercure SSE header comment to current path
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• Additional commits viewable in compare view

Updates @nestjs/platform-fastify from 11.1.28 to 12.0.1

Release notes

Sourced from @​nestjs/platform-fastify's releases.

v12.0.0

NestJS v12.0.0

NestJS 12 is centered around ESM-ready packages, first-class Standard Schema support for validation and serialization, a rebuilt CLI, and native observability through the new @nestjs/observe SDK.

Existing CommonJS applications keep working — migrating your own code to ESM is entirely optional.

📖 Full migration guide

---

Upgrading

Upgrade the CLI first, since the upgrade command ships with it:

npm i -g @nestjs/cli@latest

Then, from the root of your project:

nest upgrade

nest upgrade moves every @nestjs/* package to its v12-compatible major at once and applies the mechanical parts of the migration for you — nest-cli.json webpack options, the GraphQL playground → graphiql rename and subscriptions transport swap, the NATS package replacement, @nestjs/config validation options, Jest and Joi bumps — then prints a report of everything it changed and everything you still need to review by hand. Run it with --dry-run first to see that report without touching your files.

It deliberately does not migrate your project to ESM, Vitest, or oxlint. Those are the defaults for newly generated projects; existing projects adopt them on their own schedule.

Node.js: v12 requires Node.js v20.19+ or v22.12+. Both require(esm) and the ESM packages depend on it; the upgrade command refuses to run on older releases (including the 21.x line). The latest active LTS is recommended.

---

Highlights

ESM packages

All core Nest packages now ship as ESM. Thanks to require(esm) in modern Node.js, most existing CommonJS applications continue to work without a rewrite. Review custom bootstrapping scripts, build tooling, and test runners if they assume CommonJS-only packages.

nest new now asks whether to scaffold a CommonJS or an ESM project.

Standard Schema validation

Route parameter decorators — @Body(), @Query(), @Param(), @RawBody() — accept a new schema option, designed for Standard Schema compatible libraries such as Zod, Valibot, and ArkType:

@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
  return this.usersService.create(body);
}
</tr></table> 

... (truncated)

Commits

• 4c751c5 chore(release): publish v12.0.1 release
• 3c25112 chore: update peer deps
• 6494a6c chore(release): publish v12.0.0 release
• c921a60 fix(fastify): append headers instead of overwriting
• 41402b0 fix(deps): update dependency find-my-way to v9.9.0
• e5ea7dd fix(deps): update dependency fastify to v5.12.1
• e03cf5c fix(express,fastify): apply falsy status codes in reply()
• 31ecde0 Merge pull request #17512 from nestjs/renovate/fastify-5.x
• b4de1c5 fix(deps): update dependency find-my-way to v9.8.0
• ce9b428 fix(deps): update dependency fastify to v5.12.0
• Additional commits viewable in compare view

Updates @nestjs/swagger from 11.4.6 to 12.0.0

Release notes

Sourced from @​nestjs/swagger's releases.

Release 12.0.0

What's Changed

@nestjs/swagger is now a native ES module, requires Nest 12, and changes how nullable schemas are spelled in the generated document.

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.ts / plugin.js / plugin.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root (@nestjs/swagger) or from @nestjs/swagger/plugin.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, a CommonJS app can keep doing const { SwaggerModule } = require('@nestjs/swagger'). The CLI plugin entry (@nestjs/swagger/plugin) also keeps a require condition so nest-cli.json setups load it unchanged.

This is why the package now declares "engines": { "node": "^20.19.0 || >=22.12.0" } — those are the Node versions where require(esm) is available without a flag.

Nest 12 peer dependencies

@nestjs/common and @nestjs/core peers are now ^12.0.0. @nestjs/mapped-types moves to 12.0.0 (itself ESM, with its major aligned to the Nest 12 line), so PartialType, PickType, OmitType and IntersectionType come from an ESM build too.

Standard Schema support

Schemas passed to Nest 12's route decorators (for example @Body({ schema: z.object({ ... }) })) can now be reflected into the OpenAPI document. Supply an adapter via the new standardSchemaConverter document option:

import { SwaggerModule, DocumentBuilder } from '@nestjs/swagger';
import type { SwaggerDocumentOptions } from '@nestjs/swagger';
import { createSchema } from 'zod-openapi';
import type { ZodType } from 'zod';
// Standard Schema exposes the producing library under ~standard.vendor,
// which is how you narrow the raw value to a library-specific type.
function isZodSchema(schema: unknown): schema is ZodType {
return (
!!schema &&
typeof schema === 'object' &&
(schema as { '~standard'?: { vendor?: string } })['~standard']?.vendor ===
'zod'
);
}
const options: SwaggerDocumentOptions = {
standardSchemaConverter: (schema, { schemaType }) => {
if (isZodSchema(schema)) {
const { schema: converted, components } = createSchema(schema, {
io: schemaType,
openapiVersion: '3.0.0'
});
return { schema: converted, components };
}
}
</tr></table>

... (truncated)

Commits

• 4366c7c chore(): release v12.0.0
• b220e3a chore: upgrade to v12
• de89f82 Merge pull request #4070 from micalevisk/fix/issue-4063
• 799e59e refactor(nullable): normalize at the document boundary instead of threading t...
• 9eaf8e2 fix(responses): spell nullable responses per the declared document version
• c2df819 fix(schema): emit 3.1 nullability instead of the 3.0 nullable keyword
• e005535 Merge pull request #4060 from nestjs/renovate/zod-4.x
• 743f6b0 Merge pull request #4061 from nestjs/renovate/es-toolkit-1.x
• 1bce683 Merge pull request #4062 from nestjs/renovate/apidevtools-swagger-parser-12.x
• 3aa9051 chore(deps): update dependency @​apidevtools/swagger-parser to v12
• Additional commits viewable in compare view

Updates @prisma/adapter-pg from 7.9.0 to 7.10.0

Release notes

Sourced from @​prisma/adapter-pg's releases.

7.10.0

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version
npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
})

Without an explicit --config option, Prisma 7 searches for:

1. Root-level prisma7.config.* files.
2. .config/prisma7.* files.
3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

... (truncated)

Commits

• 3fa65ac fix(p2002): correct modelName in nested create unique constraint errors #2959...
• a180209 fix(adapter-pg): map PostgreSQL deadlocks to P2034 (#29717)
• 800f1d1 fix(adapter-pg): preserve constraint name for unique violations (23505) (#29587)
• 7ef2104 fix(postgres): handle SQLSTATE 23001 for RESTRICT violations (#29554)
• See full diff in compare view

Updates @prisma/client from 7.9.0 to 7.10.0

Release notes

Sourced from @​prisma/client's releases.

7.10.0

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version
npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
})

Without an explicit --config option, Prisma 7 searches for:

1. Root-level prisma7.config.* files.
2. .config/prisma7.* files.
3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

... (truncated)

Commits

• 05c1b88 Teach Prisma 7 to prefer versioned config files (#30020)
• cf2bc1f Rename prisma7 package to @​prisma/prisma7 (#30002)
• ce5a34c Complete downstream actionable Prisma 7 guidance propagation (#29994)
• 3f13ec6 Complete CLI-owned prisma7 distribution identity (#29969)
• 179ba0c feat(prisma7): add side-by-side CLI wrapper (#29949)
• 3fa65ac fix(p2002): correct modelName in nested create unique constraint errors #2959...
• 6b6d9e9 chore(deps): update engines to 7.10.0-4.0edf323efd1d98336f3f0a68684b56f689b90...
• b64e33c chore(deps): update engines to 7.10.0-3.9d90ce2c89d5c95a1148aef15e5561ab6c490...
• 2046f9b feat(client): expose ModelName to compute function in Result extensions (#29782)
• f2b3abd chore(deps): update engines to 7.10.0-1.6d040c802892de6d56c7e0061b7a10b3e6a0c...
• Additional commits viewable in compare view

Updates @scalar/nestjs-api-reference from 1.2.11 to 1.2.16

Changelog

Sourced from @​scalar/nestjs-api-reference's changelog.

1.2.16

Patch Changes

• #9941: Republish every package through npm trusted publishing. No functional changes.

1.2.15

1.2.14

1.2.13

1.2.12

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​scalar/nestjs-api-reference since your current version.

Updates fastify from 5.10.0 to 5.12.1

Release notes

Sourced from fastify's releases.

v5.12.1

⚠️ Security release

• Fix for GHSA-w2qp-rph6-63g4
• Fix for GHSA-3m5p-2c4r-xxw2

What's Changed

• [Backport 5.x] test: fix reply.mediaType by @​github-actions[bot] in fastify/fastify#6950
• [Backport 5.x] ci: allow backport in pr title by @​github-actions[bot] in fastify/fastify#6952
• [Backport 5.x] fix: run preClose hook exactly once per declaring instance by @​github-actions[bot] in fastify/fastify#6954
• [Backport 5.x] fix: report canonical route url for hidden prefix slash route by @​github-actions[bot] in fastify/fastify#6961

Full Changelog: fastify/fastify@v5.12.0...v5.12.1

v5.12.0

What's Changed

• chore(sponsor): add testmu ai by @​Eomm in fastify/fastify#6922
• docs: add per-route logging for Google Cloud Functions by @​slegarraga in fastify/fastify#6907
• test: remove @​sinonjs/fake-timers by @​climba03003 in fastify/fastify#6934
• [Backport 5.x] fix: remove raw response headers by @​github-actions[bot] in fastify/fastify#6939
• [Backport 5.x] test: use process-warning spyWarning for testing by @​github-actions[bot] in fastify/fastify#6945
• [Backport 5.x] feat: add Reply.prototype.mediaType by @​github-actions[bot] in fastify/fastify#6946
• [Backport 5.x] fix(content-type): return undefined for invalid media types by @​github-actions[bot] in fastify/fastify#6947

Full Changelog: fastify/fastify@v5.11.3...v5.12.0

v5.11.3

What's Changed

• fix: clear trailer state when removing all trailers by @​Ram-blip in fastify/fastify#6845
• docs: document percent-decoded route params as untrusted input by @​mcollina in fastify/fastify#6903
• docs(errors): document what the default error handler sends by @​basteez in fastify/fastify#6894
• docs(readme): fix grammar and cjs capitalization by @​minirang in fastify/fastify#6899
• fix: pass null instead of undefined to requestCompleted on success by @​lazerg in fastify/fastify#6837
• docs(encapsulation): clarify nested plugin scopes by @​jean-michelet in fastify/fastify#6893
• chore: Bump fastify/workflows/.github/workflows/lock-threads.yml from 6.0.0 to 7.0.0 by @​dependabot[bot] in fastify/fastify#6916
• chore: Bump fastify/workflows/.github/workflows/nested-quality.yml from 6.0.0 to 7.0.0 by @​dependabot[bot] in fastify/fastify#6917
• fix: recognize constructor-assigned built-in properties as decorator … by @​aquie00t in fastify/fastify#6892
• fix: reset lastIndex before testing global/sticky content-type RegExp parsers by @​zelinewang in fastify/fastify#6846

New Contributors

• @​minirang made their first contribution in fastify/fastify#6899
• @​lazerg made their first contribution in fastify/fastify#6837
• @​zelinewang made their first contribution in fastify/fastify#6846

Full Changelog: fastify/fastify@v5.11.2...v5.11.3

v5.11.2

What's Changed

... (truncated)

Commits

• 7d196a9 Bumped v5.12.1
• 1ef8a60 fix(validation): preserve coerced root values
• 8acfea7 fix: disable numeric trustProxy hop-count trust
• 268e439 fix: report canonical route url for hidden prefix slash route (#6719) (#6961)
• b3b8be1 fix: run preClose hook exactly once per declaring instance (#6940) (#6954)
• 4708a98 ci: allow backport in pr title (#6948) (#6952)
• 65d12da test: fix reply.mediaType (#6949) (#6950)
• 27d1fec Bumped v5.12.0
• 430dd4e fix(content-type): return undefined for invalid media types (#6942) (#6947)
• fd5fe53 feat: add Reply.prototype.mediaType (#6932) (#6946)
• Additional commits viewable in compare view

Updates ioredis from 5.11.1 to 6.0.0

Release notes

Sourced from ioredis's releases.

v6.0.0

6.0.0 (2026-07-31)

• Add RESP3 (#2127) (5d0862e)

Bug Fixes

• clear stale socket timeout on reconnect (#2148) (6455dbe)
• cluster: recreate stale connection on circular MOVED (#2135) (08c8967)
• cluster: validate MOVED slot to prevent Array.prototype pollution (#2151) (9618206), closes #1267
• command: serialize large integer arguments in decimal notation (#2136) (09b8d04)
• redis: keep reconnecting when connection closes during client setup (#2099) (#2123) (f9a66bc)
• sentinel: preserve zero preferred slave priority (#2129) (a3f9f2d)
• tracing: redact values for GETSET and PSETEX (#2134) (832765d)
• types: export ScanStreamOptions, RedisStatus and ClusterStatus (#2158) (cf3bf71)

Features

• add LMOVEM and BLMOVEM command support (#2144) (c26af46)
• add Redis 8.10 set cardinality commands (#2143) (301099b)
• himport managed fieldsets (#2159) (729f174)
• improve default connection resilience (#2160) (6d0716e)
• support MAXCOUNT and MAXSIZE for stream reads (#2142) (ae5e41b)

BREAKING CHANGES

• ioredis now requires Node.js 20 or newer and uses RESP3 by default. Set protocol: 2 to retain the v5 wire protocol.

v6.0.0-beta.1

6.0.0-beta.1 (2026-07-29)

• Add RESP3 (#2127) (5d0862e)

Bug Fixes

• clear stale socket timeout on reconnect (#2148) (6455dbe)
• cluster: recreate stale connection on circular MOVED (#2135) (08c8967)
• cluster: validate MOVED slot to prevent Array.prototype pollution (#2151) (