chore(deps): bump the production-dependencies group in /api with 19 updates

[dependabot]

Bumps the production-dependencies group in /api with 19 updates:

Package	From	To
@nestjs/cache-manager	2.3.0	12.0.0
@nestjs/common	10.4.22	12.0.1
@nestjs/core	10.4.22	12.0.1
@nestjs/jwt	10.2.0	12.0.1
@nestjs/platform-express	10.4.22	12.0.1
@nestjs/platform-socket.io	10.4.22	12.0.1
@nestjs/schedule	4.1.2	12.0.1
@nestjs/swagger	7.4.2	12.0.1
@nestjs/terminus	10.3.0	11.1.1
@nestjs/websockets	10.4.22	12.0.1
@opentelemetry/auto-instrumentations-node	0.54.0	0.79.0
@opentelemetry/exporter-trace-otlp-http	0.57.2	0.221.0
@opentelemetry/sdk-node	0.57.2	0.221.0
cache-manager	5.7.6	7.2.9
helmet	8.1.0	8.3.0
nodemailer	6.10.1	9.0.6
pg	8.21.0	8.23.0
reflect-metadata	0.1.14	0.2.2
sanitize-html	2.17.5	2.17.7

Updates @nestjs/cache-manager from 2.3.0 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.

Release 3.1.3

What's Changed

• fix: add keyv dummy check for swc builds #756 by @​kamilmysliwiec in nestjs/cache-manager#1076

Full Changelog: nestjs/cache-manager@3.1.2...3.1.3

Release 3.1.2

• chore: fix trackby api breaking change (cab7694)

3.1.1

... (truncated)

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 10.4.22 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/core from 10.4.22 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/jwt from 10.2.0 to 12.0.1

Release notes

Sourced from @​nestjs/jwt's releases.

Release 12.0.1

• fix: jsonwebtoken esm imports (05d0075)

Release 12.0.0

What's Changed

@nestjs/jwt is now a native ES module, and the major version is aligned with the Nest 12 release line

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 { JwtModule, JwtService } from '@nestjs/jwt';
// ❌ no longer resolvable
import { JwtService } from '@​nestjs/jwt/dist/jwt.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+, and all of 24.x), a CommonJS Nest application can keep requiring the package exactly as before:

const { JwtModule, JwtService } = require('@nestjs/jwt');

TypeScript users compiling to CommonJS are unaffected as long as their runtime is on a supported Node version. On older Node releases, require() of this package will throw ERR_REQUIRE_ESM — upgrade Node, or switch the consuming code to import.

jsonwebtoken re-exports

The error classes re-exported from jsonwebtoken (TokenExpiredError, NotBeforeError, JsonWebTokenError) are now re-exported explicitly by name instead of via a star export, so they resolve correctly under ESM interop with the CJS jsonwebtoken package. No import changes are needed on your side:

import { TokenExpiredError } from '@nestjs/jwt';

Upgrading

npm install @nestjs/jwt@12

For most applications this is a drop-in upgrade. Action is only required if you were relying on deep imports into dist/, or are running a Node version older than 20.19 with a CommonJS app.

Release 11.0.2

What's Changed

• fix(deps): update dependency jsonwebtoken to v9.0.3 by @​renovate[bot] in nestjs/jwt#2088

... (truncated)

Commits

• 6c75fa6 chore(): release v12.0.1
• 05d0075 fix: jsonwebtoken esm imports
• 8853ee8 chore(): release v12.0.0
• b8455f2 chore: upgrade to v12
• 542e29e chore(deps): update dependency oxlint to v1.80.0 (#2260)
• ae0d0d7 chore(deps): update nest monorepo to v11.2.3 (#2259)
• af3ad43 chore(deps): update dependency oxlint to v1.79.0 (#2258)
• 53c8fee chore(deps): update dependency vitest to v4.1.11 (#2257)
• 7014c3a Merge pull request #2205 from nestjs/renovate/cimg-node-24.x
• 54a4c5c Merge pull request #2186 from nestjs/chore/esm-migration
• Additional commits viewable in compare view

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

Updates @nestjs/platform-express from 10.4.22 to 12.0.1

Release notes

Sourced from @​nestjs/platform-express'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
• e03cf5c fix(express,fastify): apply falsy status codes in reply()
• 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
• 03587a1 chore(release): publish v11.1.29 release
• Additional commits viewable in compare view

Updates @nestjs/platform-socket.io from 10.4.22 to 12.0.1

Release notes

Sourced from @​nestjs/platform-socket.io'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
• 5ec2e58 Update io-adapter.ts
• e333721 Merge branch 'master' into platform-socket-types
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• 5d1b19b Merge branch 'master' into v12.0.0
• f2a7e4b chore(release): publish v11.2.0 release
• 03587a1 chore(release): publish v11.1.29 release
• Additional commits viewable in compare view

Updates @nestjs/schedule from 4.1.2 to 12.0.1

Release notes

Sourced from @​nestjs/schedule's releases.

Release 12.0.1

What's Changed

• feat: export ScheduleExplorer from the package entry point by @​kamilmysliwiec in nestjs/schedule#2349

Full Changelog: nestjs/schedule@12.0.0...12.0.1

Release 12.0.0

What's Changed

@nestjs/schedule is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 7.x — 6.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 { ScheduleModule, Cron, CronExpression } from '@nestjs/schedule';
// ❌ no longer resolvable
import { CronExpression } from '@​nestjs/schedule/dist/enums/cron-expression.enum';

Only . and ./package.json are exported.

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 { ScheduleModule } = require('@nestjs/schedule');

This is why the package now declares "engines": { "node": ">=20.19.0" } — require(esm) is unflagged from Node 20.19 / 22.12 onward. On older Node versions the require will throw ERR_REQUIRE_ESM.

Fixes

• Duplicate scheduler names are now rejected at startup. Two @Cron, @Interval, or @Timeout declarations sharing an explicit name previously slipped past decorator collection and only conflicted later; the DUPLICATE_SCHEDULER error is now thrown during initialization, where you can actually see it.

Upgrading

npm i @nestjs/schedule@12

• Node 20.19+ (or 22.12+) is required.
• Replace any deep imports with root imports.
• If you were importing from the removed root index.js shim path explicitly, drop the path — @nestjs/schedule resolves on its own.

... (truncated)

Commits

• 1df146c chore(): release v12.0.1
• 7c241a5 Merge pull request #2349 from nestjs/feat/export-schedule-explorer
• 00d3db8 feat: export ScheduleExplorer from the package entry point
• 55e94dd Merge pull request #2347 from nestjs/renovate/cimg-node-24.x
• 7e5d551 Merge pull request #2348 from nestjs/renovate/nest-monorepo
• 5237ab0 chore(deps): update nest monorepo to v12.0.1
• 6bd6e14 chore(): release v12.0.0
• 6719285 feat: support nestjs v12
• 3bcca07 chore(deps): update node.js to v24.20.0
• 1b24bb7 chore(deps): update nest monorepo to v11.2.3 (#2346)
• Additional commits viewable in compare view

Updates @nestjs/swagger from 7.4.2 to 12.0.1

Release notes

Sourced from @​nestjs/swagger's releases.

Release 12.0.1

12.0.1 (2026-08-28)

Bug fixes

• #4082 fix: esm hoist static imports (@​kamilmysliwiec)

Dependencies

• #4077 chore(deps): update dependency swagger-ui-dist to v5.32.14 (@​renovate[bot])

Committers: 1

• Kamil Mysliwiec (@​kamilmysliwiec)

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'
);
</tr></table>

... (truncated)

Commits

• 4274e7c chore(): release v12.0.1
• 325d009 Merge pull request #4082 from nestjs/fix/esm-hoist-static-imports
• 8980a54 fix: esm hoist static imports
• 31b0bf4 chore(deps): update dependency lint-staged to v17.4.1 (#4078)
• b71a812 Merge pull request #4077 from nestjs/renovate/swagger-ui-dist-5.x-lockfile
• ec18a13 chore(deps): update dependency swagger-ui-dist to v5.32.14
• 0f85b4c Merge pull request #4072 from nestjs/renovate/js-yaml-5.x
• 7d8b38e Merge pull request #4076 from nestjs/renovate/vite-8.x-lockfile
• ebc4cb8 Merge pull request #4069 from nestjs/renovate/zod-openapi-6.x
• 71e1769 Merge pull request #4068 from nestjs/renovate/swagger-ui-dist-5.x
• Additional commits viewable in compare view

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

Updates @nestjs/terminus from 10.3.0 to 11.1.1

Release notes

Sourced from @​nestjs/terminus's releases.

Release 11.1.1

11.1.1 (2026-02-18)

Bug Fixes

• use dependency injection to provide custom loggers (8d7226b), closes #2694, @​flovouin @​BrunnerLivio

Release 11.1.0

11.1.0 (2026-02-17)

Bug Fixes

• disallow using reserved keyword status for health indicators (303948f), closes #2682

Features

• add support for dynamic configuration with Terminus.forRootAsync (489904f), closes #2649
• infer health check result (4e59375)

Release 11.0.0

11.0.0 (2025-01-25)

Migration Guide

Features

• simplify custom health indicator creation (9f10a9b)
• upgrade to nestjs v11 (c2569df), closes #2570
• update dependencies

BREAKING CHANGES

• Drop support for Node 16 / 18

---

For users who have implemented a custom health indicator, an enhanced API is now available. However, the existing API will continue to function as-is without requiring any changes.

The new and improved HealthIndicatorService provides a streamlined way to indicate whether a health indicator is up or down.

Please note that the HealthIndicator and HealthCheckError classes have been marked as deprecated and are scheduled for removal in the next major release, version 12.0.0.

@Injectable()
export class DogHealthIndicator {
</tr></table> 

... (truncated)

Changelog

Sourced from @​nestjs/terminus's changelog.

Changelog

11.1.0 (2026-02-17)

Bug Fixes

• deps: update dependency @​grpc/grpc-js to v1.12.6 (7dd0d5f)
• deps: update dependency @​mikro-orm/nestjs to v6.1.0 (177fc8c)
• deps: update dependency @​mikro-orm/nestjs to v6.1.1 (8e3b253)
• deps: update dependency @​nestjs/mongoose to v11.0.1 (0af02b5)
• deps: update dependency @​nestjs/typeorm to v11 (687a4fe)
• deps: update dependency ioredis to v5.4.2 (47125b6)
• deps: update dependency mongoose to v8.10.1 (4b8e133)
• deps: update dependency mysql2 to v3.12.0 (0970ecd)
• deps: update dependency rxjs to v7.8.2 (4cceadb)
• deps: update dependency typeorm to v0.3.22 (b0e6662)
• deps: update mikro-orm monorepo to v6.4.5 (5ece0f8)
• deps: update nest monorepo (eb4cab2)
• deps: update nest monorepo (abd9ba8)
• deps: update nest monorepo to v11 (207b45d)
• deps: update nest monorepo to v11.0.11 (a36f951)
• deps: update nest monorepo to v11.0.9 (2865a5b)
• deps: update prisma monorepo to v6.3.0 (4c42699)
• deps: update prisma monorepo to v6.3.1 (1ed2ff0)
• disallow using reserved keyword status for health indicators (303948f), closes #2682

Features

• add support for dynamic configuration with Terminus.forRootAsync (489904f), closes #2649
• infer health check result (4e59375)

11.0.0 (2025-01-25)

11.0.0-beta.1 (2025-01-25)

Bug Fixes

• deps: update dependency @​grpc/proto-loader to v0.7.13 (bf08ece)
• deps: update dependency @​nestjs/typeorm to v10.0.2 (8430d1f)
• deps: update dependency mysql2 to v3.9.8 [security] (eae8679)
• deps: update dependency reflect-metadata to v0.2.2 (004d971)

Features

• update dependencies (969bfd7)

... (truncated)

Commits

• a5dc4a5 chore: release 1.11.1
• ff8dbcf Merge pull request #2696 from nestjs/next
• a5c030d chore: release 11.1.1-beta.1
• e45f528 chore: formatting
• eb3e234 chore: release 11.1.1-beta.0
• 8d7226b fix: use dependency injection to provide custom loggers
• 5a2647e chore(): release v11.1.0
• c9386ae Merge pull request #2621 from nestjs/renovate/mikro-orm-monorepo
• c6862f4 Merge pull request #2678 from nestjs/next
• f2a33b4 chore(deps): update mikro-orm monorepo to v6.6.7
• Additional commits viewable in compare view

Updates @nestjs/websockets from 10.4.22 to 12.0.1

Release notes

Sourced from @​nestjs/websockets'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
• 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
• 03587a1 chore(release): publish v11.1.29 release
• 92bc05d chore: update readme
• Additional commits viewable in compare view

Updates @opentelemetry/auto-instrumentations-node from 0.54.0 to 0.79.0

Release notes

Sourced from @​opentelemetry/auto-instrumentations-node's releases.

auto-instrumentations-node: v0.79.0

0.79.0 (2026-07-23)

Features

• deps: update deps matching '@opentelemetry/*' (#3629) (466d5de)

Bug Fixes

• auto-instrumentations-node: avoid duplicate diag logger warning in register.js (#3601) (3ae8a1b)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​opentelemetry/instrumentation-amqplib bumped from ^0.67.0 to ^0.68.0
    • @​opentelemetry/instrumentation-aws-lambda bumped from ^0.72.0 to ^0.73.0
    • @​opentelemetry/instrumentation-aws-sdk bumped from ^0.75.0 to ^0.76.0
    • @​opentelemetry/instrumentation-bunyan bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-cassandra-driver bumped from ^0.65.0 to ^0.66.0
    • @​opentelemetry/instrumentation-connect bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-cucumber bumped from ^0.36.0 to ^0.37.0
    • @​opentelemetry/instrumentation-dataloader bumped from ^0.37.0 to ^0.38.0
    • @​opentelemetry/instrumentation-dns bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-express bumped from ^0.68.0 to ^0.69.0
    • @​opentelemetry/instrumentation-fs bumped from ^0.39.0 to ^0.40.0
    • @​opentelemetry/instrumentation-generic-pool bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-graphql bumped from ^0.68.0 to ^0.69.0
    • @​opentelemetry/instrumentation-hapi bumped from ^0.66.0 to ^0.67.0
    • @​opentelemetry/instrumentation-host-metrics bumped from ^0.3.0 to ^0.4.0
    • @​opentelemetry/instrumentation-ioredis bumped from ^0.68.0 to ^0.69.0
    • @​opentelemetry/instrumentation-kafkajs bumped from ^0.29.0 to ^0.30.0
    • @​opentelemetry/instrumentation-knex bumped from ^0.64.0 to ^0.65.0
    • @​opentelemetry/instrumentation-koa bumped from ^0.68.0 to ^0.69.0
    • @​opentelemetry/instrumentation-lru-memoizer bumped from ^0.64.0 to ^0.65.0
    • @​opentelemetry/instrumentation-memcached bumped from ^0.63.0 to ^0.64.0
    • @​opentelemetry/instrumentation-mongodb bumped from ^0.73.0 to ^0.74.0
    • @​opentelemetry/instrumentation-mongoose bumped from ^0.66.0 to ^0.67.0
    • @​opentelemetry/instrumentation-mysql bumped from ^0.66.0 to ^0.67.0
    • @​opentelemetry/instrumentation-mysql2 bumped from ^0.66.0 to ^0.67.0
    • @​opentelemetry/instrumentation-nestjs-core bumped from ^0.66.0 to ^0.67.0
    • @​opentelemetry/instrumentation-net bumped from ^0.64.0 to ^0.65.0
    • @​opentelemetry/instrumentation-openai bumped from ^0.18.0 to ^0.19.0
    • @​opentelemetry/instrumentation-oracledb bumped from ^0.45.0 to ^0.46.0
    • @​opentelemetry/instrumentation-pg bumped from ^0.72.0 to ^0.73.0
    • @​opentelemetry/instrumentation-pino bumped from ^0.66.0 to ^0.67.0
    • @​opentelemetry/instrumentation-redis bumped from ^0.68.0 to ^0.69.0

... (truncated)

Changelog

Sourced from @​opentelemetry/auto-instrumentations-node's changelog.

0.79.0 (2026-07-23)

Features

• deps: update deps matching '@opentelemetry/*' (#3629) (466d5de)

Bug Fixes

• auto-instrumentations-node: avoid duplicate diag logger warning in register.js (#3601) (

[dependabot]

Labels

The following labels could not be found: area:api, ci, dependencies. Please create them before Dependabot can add them to a pull request.

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