Skip to content

chore(deps): bump the prod-deps group across 1 directory with 13 updates - #127

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/prod-deps-50ed0aec86
Closed

chore(deps): bump the prod-deps group across 1 directory with 13 updates#127
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/prod-deps-50ed0aec86

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the prod-deps group with 13 updates in the / directory:

Package From To
@aws-sdk/client-s3 3.1097.0 3.1119.0
@aws-sdk/s3-presigned-post 3.1097.0 3.1119.0
@aws-sdk/s3-request-presigner 3.1097.0 3.1119.0
@nestjs/cache-manager 3.1.3 12.0.0
@nestjs/common 11.1.28 12.0.1
@nestjs/core 11.1.28 12.0.1
@nestjs/platform-express 11.1.28 12.0.1
@nestjs/schedule 6.1.3 12.0.1
@nestjs/swagger 11.4.6 12.0.0
iovalkey 0.3.3 0.4.0
ipaddr.js 2.4.0 2.5.0
nanoid 6.0.0 6.0.1
pg 8.22.0 8.23.0

Updates @aws-sdk/client-s3 from 3.1097.0 to 3.1119.0

Release notes

Sourced from @​aws-sdk/client-s3's releases.

v3.1119.0

3.1119.0(2026-08-26)

Chores
  • codegen: smithy-aws-typescript-codegen 0.53.0 (#8276) (dffb383b)
New Features
  • client-sagemaker: Amazon SageMaker AI now supports ml.g7 instances for model optimization. You can now run model optimization jobs on ml.g7 instances, in supported AWS Regions. (6d5e1066)
  • client-devops-agent: AWS DevOps Agent now supports trigger filter groups for Release Readiness Review, letting you control when the capability auto-triggers based on webhook events and target branches. (bc3d53d5)
  • client-license-manager-user-subscriptions: Released support for License Expiry field in ListProductSubscriptions API (454d7f7f)
  • client-ec2: Adds deleting state to possible VPC States. (43091d55)
  • client-network-firewall: Adding new status enum for Firewalls. (4cb21cb3)

For list of updated packages, view updated-packages.md in assets-3.1119.0.zip

v3.1118.0

3.1118.0(2026-08-25)

Documentation Changes
  • client-marketplace-metering: Updated documentation to clarify duplicate-billing prevention and BatchMeterUsage retry guidance (32231025)
New Features
  • clients: update client endpoints as of 2026-08-25 (c732c7ae)
  • client-iot: As part of this release, we are extending capability of AWS IoT Rules Engine to support IoT InfluxDB Action. The IoT InfluxDB action lets customers send messages from IoT sensors and applications to InfluxDB. (9e82d71c)
  • client-iam-toolbox: AWS Identity and Access Management (IAM) announces access troubleshooter, helping you debug access denied errors faster. Supported error messages now include an identifier you can use to retrieve detailed evaluations of the policies considered and their results. Preview in US East (N. Virginia). (3187bf7a)
  • client-ec2: Fleet feature to support Capacity Reservation Resource Groups with Amazon EC2 Capacity Blocks and interruptible Capacity Reservations (144e9945)
  • client-eks: This feature would give customers the ability to tune TerminatedPodGcThreshold configuration in an Amazon EKS cluster. (bdc0470b)
  • client-evs: EVS now supports i7i.metal-48xl EC2 bare metal instance type, delivering high random IOPS performance with real-time latency, ideal for IO intensive and latency-sensitive workloads such as transactional databases, real-time analytics, and AI ML pre-processing. (7b66b723)
  • client-auto-scaling: Adds support for Distribution Segments in mixed instances policies, providing ordered prioritization across On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and On-Demand capacity. (986ae924)
  • client-devops-agent: Adds the UpdateApprovalAction API for resolving agent action approvals in AWS DevOps Agent agent spaces. (6dfd3b34)

For list of updated packages, view updated-packages.md in assets-3.1118.0.zip

v3.1117.0

3.1117.0(2026-08-24)

Documentation Changes
  • client-batch: Doc Update, Add note that UpdatePolicy applies only to EC2 managed compute environments (26c213cf)

... (truncated)

Changelog

Sourced from @​aws-sdk/client-s3's changelog.

3.1119.0 (2026-08-26)

Note: Version bump only for package @​aws-sdk/client-s3

3.1118.0 (2026-08-25)

Note: Version bump only for package @​aws-sdk/client-s3

3.1117.0 (2026-08-24)

Note: Version bump only for package @​aws-sdk/client-s3

3.1116.0 (2026-08-21)

Note: Version bump only for package @​aws-sdk/client-s3

3.1115.0 (2026-08-20)

Note: Version bump only for package @​aws-sdk/client-s3

3.1114.0 (2026-08-19)

Note: Version bump only for package @​aws-sdk/client-s3

3.1113.0 (2026-08-18)

... (truncated)

Commits

Updates @aws-sdk/s3-presigned-post from 3.1097.0 to 3.1119.0

Release notes

Sourced from @​aws-sdk/s3-presigned-post's releases.

v3.1119.0

3.1119.0(2026-08-26)

Chores
  • codegen: smithy-aws-typescript-codegen 0.53.0 (#8276) (dffb383b)
New Features
  • client-sagemaker: Amazon SageMaker AI now supports ml.g7 instances for model optimization. You can now run model optimization jobs on ml.g7 instances, in supported AWS Regions. (6d5e1066)
  • client-devops-agent: AWS DevOps Agent now supports trigger filter groups for Release Readiness Review, letting you control when the capability auto-triggers based on webhook events and target branches. (bc3d53d5)
  • client-license-manager-user-subscriptions: Released support for License Expiry field in ListProductSubscriptions API (454d7f7f)
  • client-ec2: Adds deleting state to possible VPC States. (43091d55)
  • client-network-firewall: Adding new status enum for Firewalls. (4cb21cb3)

For list of updated packages, view updated-packages.md in assets-3.1119.0.zip

v3.1118.0

3.1118.0(2026-08-25)

Documentation Changes
  • client-marketplace-metering: Updated documentation to clarify duplicate-billing prevention and BatchMeterUsage retry guidance (32231025)
New Features
  • clients: update client endpoints as of 2026-08-25 (c732c7ae)
  • client-iot: As part of this release, we are extending capability of AWS IoT Rules Engine to support IoT InfluxDB Action. The IoT InfluxDB action lets customers send messages from IoT sensors and applications to InfluxDB. (9e82d71c)
  • client-iam-toolbox: AWS Identity and Access Management (IAM) announces access troubleshooter, helping you debug access denied errors faster. Supported error messages now include an identifier you can use to retrieve detailed evaluations of the policies considered and their results. Preview in US East (N. Virginia). (3187bf7a)
  • client-ec2: Fleet feature to support Capacity Reservation Resource Groups with Amazon EC2 Capacity Blocks and interruptible Capacity Reservations (144e9945)
  • client-eks: This feature would give customers the ability to tune TerminatedPodGcThreshold configuration in an Amazon EKS cluster. (bdc0470b)
  • client-evs: EVS now supports i7i.metal-48xl EC2 bare metal instance type, delivering high random IOPS performance with real-time latency, ideal for IO intensive and latency-sensitive workloads such as transactional databases, real-time analytics, and AI ML pre-processing. (7b66b723)
  • client-auto-scaling: Adds support for Distribution Segments in mixed instances policies, providing ordered prioritization across On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and On-Demand capacity. (986ae924)
  • client-devops-agent: Adds the UpdateApprovalAction API for resolving agent action approvals in AWS DevOps Agent agent spaces. (6dfd3b34)

For list of updated packages, view updated-packages.md in assets-3.1118.0.zip

v3.1117.0

3.1117.0(2026-08-24)

Documentation Changes
  • client-batch: Doc Update, Add note that UpdatePolicy applies only to EC2 managed compute environments (26c213cf)

... (truncated)

Changelog

Sourced from @​aws-sdk/s3-presigned-post's changelog.

3.1119.0 (2026-08-26)

Note: Version bump only for package @​aws-sdk/s3-presigned-post

3.1118.0 (2026-08-25)

Note: Version bump only for package @​aws-sdk/s3-presigned-post

3.1117.0 (2026-08-24)

Note: Version bump only for package @​aws-sdk/s3-presigned-post

3.1116.0 (2026-08-21)

Note: Version bump only for package @​aws-sdk/s3-presigned-post

3.1115.0 (2026-08-20)

Note: Version bump only for package @​aws-sdk/s3-presigned-post

3.1114.0 (2026-08-19)

Note: Version bump only for package @​aws-sdk/s3-presigned-post

3.1113.0 (2026-08-18)

... (truncated)

Commits

Updates @aws-sdk/s3-request-presigner from 3.1097.0 to 3.1119.0

Release notes

Sourced from @​aws-sdk/s3-request-presigner's releases.

v3.1119.0

3.1119.0(2026-08-26)

Chores
  • codegen: smithy-aws-typescript-codegen 0.53.0 (#8276) (dffb383b)
New Features
  • client-sagemaker: Amazon SageMaker AI now supports ml.g7 instances for model optimization. You can now run model optimization jobs on ml.g7 instances, in supported AWS Regions. (6d5e1066)
  • client-devops-agent: AWS DevOps Agent now supports trigger filter groups for Release Readiness Review, letting you control when the capability auto-triggers based on webhook events and target branches. (bc3d53d5)
  • client-license-manager-user-subscriptions: Released support for License Expiry field in ListProductSubscriptions API (454d7f7f)
  • client-ec2: Adds deleting state to possible VPC States. (43091d55)
  • client-network-firewall: Adding new status enum for Firewalls. (4cb21cb3)

For list of updated packages, view updated-packages.md in assets-3.1119.0.zip

v3.1118.0

3.1118.0(2026-08-25)

Documentation Changes
  • client-marketplace-metering: Updated documentation to clarify duplicate-billing prevention and BatchMeterUsage retry guidance (32231025)
New Features
  • clients: update client endpoints as of 2026-08-25 (c732c7ae)
  • client-iot: As part of this release, we are extending capability of AWS IoT Rules Engine to support IoT InfluxDB Action. The IoT InfluxDB action lets customers send messages from IoT sensors and applications to InfluxDB. (9e82d71c)
  • client-iam-toolbox: AWS Identity and Access Management (IAM) announces access troubleshooter, helping you debug access denied errors faster. Supported error messages now include an identifier you can use to retrieve detailed evaluations of the policies considered and their results. Preview in US East (N. Virginia). (3187bf7a)
  • client-ec2: Fleet feature to support Capacity Reservation Resource Groups with Amazon EC2 Capacity Blocks and interruptible Capacity Reservations (144e9945)
  • client-eks: This feature would give customers the ability to tune TerminatedPodGcThreshold configuration in an Amazon EKS cluster. (bdc0470b)
  • client-evs: EVS now supports i7i.metal-48xl EC2 bare metal instance type, delivering high random IOPS performance with real-time latency, ideal for IO intensive and latency-sensitive workloads such as transactional databases, real-time analytics, and AI ML pre-processing. (7b66b723)
  • client-auto-scaling: Adds support for Distribution Segments in mixed instances policies, providing ordered prioritization across On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and On-Demand capacity. (986ae924)
  • client-devops-agent: Adds the UpdateApprovalAction API for resolving agent action approvals in AWS DevOps Agent agent spaces. (6dfd3b34)

For list of updated packages, view updated-packages.md in assets-3.1118.0.zip

v3.1117.0

3.1117.0(2026-08-24)

Documentation Changes
  • client-batch: Doc Update, Add note that UpdatePolicy applies only to EC2 managed compute environments (26c213cf)

... (truncated)

Changelog

Sourced from @​aws-sdk/s3-request-presigner's changelog.

3.1119.0 (2026-08-26)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.1118.0 (2026-08-25)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.1117.0 (2026-08-24)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.1116.0 (2026-08-21)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.1115.0 (2026-08-20)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.1114.0 (2026-08-19)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.1113.0 (2026-08-18)

... (truncated)

Commits

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/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-express from 11.1.28 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/schedule from 6.1.3 to 12.0.1

Release notes

Sourced from @​nestjs/schedule's releases.

Release 12.0.1

What's Changed

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.
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 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 iovalkey from 0.3.3 to 0.4.0

Release notes

Sourced from iovalkey's releases.

v0.4.0

What's Changed

New Contributors

Full Changelog: valkey-io/iovalkey@v0.3.1...v0.4.0

Commits

Updates ipaddr.js from 2.4.0 to 2.5.0

Changelog

Sourced from ipaddr.js's changelog.

2.5.0 - 2026-08-04

  • remove ipaddr.min.js, end users must provide own minification/bundling
  • fix: compress the leftmost zero run in toString (...

    Description has been truncated

@dependabot
chore(deps): bump the prod-deps group across 1 directory with 13 updates
333029d 
Bumps the prod-deps group with 13 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@aws-sdk/client-s3](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3) | `3.1097.0` | `3.1119.0` |
| [@aws-sdk/s3-presigned-post](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/packages/s3-presigned-post) | `3.1097.0` | `3.1119.0` |
| [@aws-sdk/s3-request-presigner](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/packages/s3-request-presigner) | `3.1097.0` | `3.1119.0` |
| [@nestjs/cache-manager](https://github.com/nestjs/cache-manager) | `3.1.3` | `12.0.0` |
| [@nestjs/common](https://github.com/nestjs/nest/tree/HEAD/packages/common) | `11.1.28` | `12.0.1` |
| [@nestjs/core](https://github.com/nestjs/nest/tree/HEAD/packages/core) | `11.1.28` | `12.0.1` |
| [@nestjs/platform-express](https://github.com/nestjs/nest/tree/HEAD/packages/platform-express) | `11.1.28` | `12.0.1` |
| [@nestjs/schedule](https://github.com/nestjs/schedule) | `6.1.3` | `12.0.1` |
| [@nestjs/swagger](https://github.com/nestjs/swagger) | `11.4.6` | `12.0.0` |
| [iovalkey](https://github.com/valkey-io/iovalkey) | `0.3.3` | `0.4.0` |
| [ipaddr.js](https://github.com/whitequark/ipaddr.js) | `2.4.0` | `2.5.0` |
| [nanoid](https://github.com/ai/nanoid) | `6.0.0` | `6.0.1` |
| [pg](https://github.com/brianc/node-postgres/tree/HEAD/packages/pg) | `8.22.0` | `8.23.0` |



Updates `@aws-sdk/client-s3` from 3.1097.0 to 3.1119.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-s3/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1119.0/clients/client-s3)

Updates `@aws-sdk/s3-presigned-post` from 3.1097.0 to 3.1119.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/packages/s3-presigned-post/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1119.0/packages/s3-presigned-post)

Updates `@aws-sdk/s3-request-presigner` from 3.1097.0 to 3.1119.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/packages/s3-request-presigner/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1119.0/packages/s3-request-presigner)

Updates `@nestjs/cache-manager` from 3.1.3 to 12.0.0
- [Release notes](https://github.com/nestjs/cache-manager/releases)
- [Commits](nestjs/cache-manager@3.1.3...12.0.0)

Updates `@nestjs/common` from 11.1.28 to 12.0.1
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.0.1/packages/common)

Updates `@nestjs/core` from 11.1.28 to 12.0.1
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.0.1/packages/core)

Updates `@nestjs/platform-express` from 11.1.28 to 12.0.1
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.0.1/packages/platform-express)

Updates `@nestjs/schedule` from 6.1.3 to 12.0.1
- [Release notes](https://github.com/nestjs/schedule/releases)
- [Commits](nestjs/schedule@6.1.3...12.0.1)

Updates `@nestjs/swagger` from 11.4.6 to 12.0.0
- [Release notes](https://github.com/nestjs/swagger/releases)
- [Commits](nestjs/swagger@11.4.6...12.0.0)

Updates `iovalkey` from 0.3.3 to 0.4.0
- [Release notes](https://github.com/valkey-io/iovalkey/releases)
- [Commits](https://github.com/valkey-io/iovalkey/commits/v0.4.0)

Updates `ipaddr.js` from 2.4.0 to 2.5.0
- [Changelog](https://github.com/whitequark/ipaddr.js/blob/main/Changes.md)
- [Commits](https://github.com/whitequark/ipaddr.js/commits)

Updates `nanoid` from 6.0.0 to 6.0.1
- [Release notes](https://github.com/ai/nanoid/releases)
- [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md)
- [Commits](ai/nanoid@6.0.0...6.0.1)

Updates `pg` from 8.22.0 to 8.23.0
- [Changelog](https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md)
- [Commits](https://github.com/brianc/node-postgres/commits/pg@8.23.0/packages/pg)

---
updated-dependencies:
- dependency-name: "@aws-sdk/client-s3"
  dependency-version: 3.1119.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-deps
- dependency-name: "@aws-sdk/s3-presigned-post"
  dependency-version: 3.1119.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-deps
- dependency-name: "@aws-sdk/s3-request-presigner"
  dependency-version: 3.1119.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-deps
- dependency-name: "@nestjs/cache-manager"
  dependency-version: 12.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: prod-deps
- dependency-name: "@nestjs/common"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: prod-deps
- dependency-name: "@nestjs/core"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: prod-deps
- dependency-name: "@nestjs/platform-express"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: prod-deps
- dependency-name: "@nestjs/schedule"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: prod-deps
- dependency-name: "@nestjs/swagger"
  dependency-version: 12.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: prod-deps
- dependency-name: iovalkey
  dependency-version: 0.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-deps
- dependency-name: ipaddr.js
  dependency-version: 2.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-deps
- dependency-name: nanoid
  dependency-version: 6.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: prod-deps
- dependency-name: pg
  dependency-version: 8.23.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: prod-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Aug 29, 2026
@dependabot @github

dependabot Bot commented on behalf of github Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

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

@dependabot dependabot Bot closed this Sep 5, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/prod-deps-50ed0aec86 branch September 5, 2026 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code package

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants