Skip to content

build(deps): bump the nestjs-framework group in /Backend with 11 updates - #489

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/Backend/nestjs-framework-a17de7a067
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/Backend/nestjs-framework-a17de7a067

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the nestjs-framework group in /Backend with 11 updates:

Package From To
@nestjs/common 11.1.27 12.1.2
@nestjs/config 4.0.4 12.0.1
@nestjs/core 11.1.27 12.1.2
@nestjs/mapped-types 2.1.1 12.0.0
@nestjs/platform-express 11.1.27 12.1.2
@nestjs/swagger 11.4.4 12.0.2
@nestjs/throttler 6.5.0 6.7.1
@nestjs/typeorm 11.0.2 12.0.2
@nestjs/cli 11.0.23 12.0.8
@nestjs/schematics 11.1.0 12.0.6
@nestjs/testing 11.1.28 12.1.2

Updates @nestjs/common from 11.1.27 to 12.1.2

Release notes

Sourced from @​nestjs/common's releases.

v12.1.1 (2026-09-28)

Bug fixes

  • common, core, microservices, testing
  • microservices
    • #17891 fix(microservices): let the mqtt client retry after a failed connect (@​hktitof)
    • #17888 fix(microservices): keep tcp event listeners across reconnects (@​KAPUIST)
    • #17887 fix(microservices): ignore events from a replaced tcp client socket (@​KAPUIST)
    • #17878 fix(microservices): keep a newer nats connection when a stale one fails (@​hktitof)
    • #17869 fix(microservices): keep a newer kafka connection when a stale one fails (@​kamilmysliwiec)
    • #17865 fix(microservices): let the rmq client retry after a failed connect (@​hktitof)
    • #17866 fix(microservices): reply on the request channel when redis wildcards are enabled (@​fadiroot)
    • #17861 fix(microservices): recover the nats client after it gives up reconnecting (@​xia-chao)
  • common
    • #17884 fix(common): preserve string enum values matching numeric member names (@​KAPUIST)
  • core
    • #17871 fix(core): detect circular dependencies across more than two providers (@​erezcor)
  • platform-fastify
    • #17867 fix(fastify): treat a JSON content type with parameters as JSON in reply() (@​fadiroot)
  • core, testing

Enhancements

Committers: 13

v12.1.0 (2026-09-23)

Bug fixes

... (truncated)

Commits
  • 8ab60aa chore(release): publish v12.1.2 release
  • ab3fb3d chore(release): publish v12.1.2 release
  • 50fb722 docs(core): fix resolve() @​returns tags to match their Promise signatures (#1...
  • 4ea29cc feat(common): export UUIDVersion and support 'all' and numeric versions in Pa...
  • a054312 fix(common): keep StreamableFile from mutating the caller options (#17925)
  • 41a3a54 feat(common): support uuid v1, v2, v6 and v8 in ParseUUIDPipe (#17904)
  • 9feedff chore(release): publish v12.1.1 release
  • daf6883 fix(common): logger bugs in json output, level changes, fatal and buffered lo...
  • 34c9965 fix(common): preserve string enum values matching numeric member names (#17884)
  • 1fbe1c5 fix(common): reject non-numeric items in ParseArrayPipe with items Number (#1...
  • Additional commits viewable in compare view

Updates @nestjs/config from 4.0.4 to 12.0.1

Release notes

Sourced from @​nestjs/config's releases.

Release 12.0.1

What's Changed

New Contributors

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

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:

... (truncated)

Commits
  • 2785b5f chore(): release v12.0.1
  • 0c0a0d6 fix(deps): update dependency dotenv to v18.0.3 (#2444)
  • 130ee69 fix(deps): update dependency es-toolkit to v1.52.0 (#2411)
  • ab84892 chore(deps): update node.js to v24.21.0 (#2420)
  • d71b4a8 fix(config): prevent prefix corruption and escape propertyPath in updateInter...
  • 498b207 fix(deps): update dependency dotenv to v18 (#2437)
  • c32556f chore(deps): update dependency oxlint to v1.85.0 (#2443)
  • 58af4ad chore(deps): update nest monorepo to v12.0.4 (#2442)
  • 56fdf53 chore(deps): update commitlint monorepo to v21.2.3 (#2441)
  • 73353eb chore(deps): update dependency @​types/node to v24.13.6 (#2440)
  • Additional commits viewable in compare view

Updates @nestjs/core from 11.1.27 to 12.1.2

Release notes

Sourced from @​nestjs/core's releases.

v12.1.1 (2026-09-28)

Bug fixes

  • common, core, microservices, testing
  • microservices
    • #17891 fix(microservices): let the mqtt client retry after a failed connect (@​hktitof)
    • #17888 fix(microservices): keep tcp event listeners across reconnects (@​KAPUIST)
    • #17887 fix(microservices): ignore events from a replaced tcp client socket (@​KAPUIST)
    • #17878 fix(microservices): keep a newer nats connection when a stale one fails (@​hktitof)
    • #17869 fix(microservices): keep a newer kafka connection when a stale one fails (@​kamilmysliwiec)
    • #17865 fix(microservices): let the rmq client retry after a failed connect (@​hktitof)
    • #17866 fix(microservices): reply on the request channel when redis wildcards are enabled (@​fadiroot)
    • #17861 fix(microservices): recover the nats client after it gives up reconnecting (@​xia-chao)
  • common
    • #17884 fix(common): preserve string enum values matching numeric member names (@​KAPUIST)
  • core
    • #17871 fix(core): detect circular dependencies across more than two providers (@​erezcor)
  • platform-fastify
    • #17867 fix(fastify): treat a JSON content type with parameters as JSON in reply() (@​fadiroot)
  • core, testing

Enhancements

Committers: 13

v12.1.0 (2026-09-23)

Bug fixes

... (truncated)

Commits
  • 8ab60aa chore(release): publish v12.1.2 release
  • ab3fb3d chore(release): publish v12.1.2 release
  • 50fb722 docs(core): fix resolve() @​returns tags to match their Promise signatures (#1...
  • dee19bb fix(core): resolve durable global filters with the strategy's context id (#17...
  • 9feedff chore(release): publish v12.1.1 release
  • daf6883 fix(common): logger bugs in json output, level changes, fatal and buffered lo...
  • b1014b6 fix(core): detect circular dependencies across more than two providers (#17871)
  • b5f3273 fix(core): honor class and factory overrides of value providers (#17860)
  • 5100837 fix(core): recommend {*path} in the legacy wildcard warning (#17859)
  • 6739656 chore(release): publish v12.1.0 release
  • Additional commits viewable in compare view

Updates @nestjs/mapped-types from 2.1.1 to 12.0.0

Release notes

Sourced from @​nestjs/mapped-types's releases.

Release 12.0.0

What's Changed

@nestjs/mapped-types is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 3.x — 2.1.1 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.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, this keeps working:

const { PartialType } = require('@nestjs/mapped-types');
Commits
  • 47bf940 chore(): release v12.0.0
  • cd569d5 chore: upgrade to v12 deps
  • 54c3e26 chore(deps): update dependency oxlint to v1.80.0 (#2026)
  • 6b06282 chore(deps): update dependency @​nestjs/common to v11.2.3 (#2025)
  • ab015f0 chore(deps): update dependency vite to v8.2.2 (#2024)
  • c7960d5 chore(deps): update dependency oxlint to v1.79.0 (#2023)
  • fdc3f31 chore(deps): update dependency vitest to v4.1.11 (#2022)
  • 84b5a54 Merge pull request #1989 from nestjs/renovate/vite-8.x-lockfile
  • a4e403e chore(deps): update dependency vite to v8.2.1
  • 9a7c342 test: update vitest config
  • Additional commits viewable in compare view

Updates @nestjs/platform-express from 11.1.27 to 12.1.2

Release notes

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

v12.1.1 (2026-09-28)

Bug fixes

  • common, core, microservices, testing
  • microservices
    • #17891 fix(microservices): let the mqtt client retry after a failed connect (@​hktitof)
    • #17888 fix(microservices): keep tcp event listeners across reconnects (@​KAPUIST)
    • #17887 fix(microservices): ignore events from a replaced tcp client socket (@​KAPUIST)
    • #17878 fix(microservices): keep a newer nats connection when a stale one fails (@​hktitof)
    • #17869 fix(microservices): keep a newer kafka connection when a stale one fails (@​kamilmysliwiec)
    • #17865 fix(microservices): let the rmq client retry after a failed connect (@​hktitof)
    • #17866 fix(microservices): reply on the request channel when redis wildcards are enabled (@​fadiroot)
    • #17861 fix(microservices): recover the nats client after it gives up reconnecting (@​xia-chao)
  • common
    • #17884 fix(common): preserve string enum values matching numeric member names (@​KAPUIST)
  • core
    • #17871 fix(core): detect circular dependencies across more than two providers (@​erezcor)
  • platform-fastify
    • #17867 fix(fastify): treat a JSON content type with parameters as JSON in reply() (@​fadiroot)
  • core, testing

Enhancements

Committers: 13

v12.1.0 (2026-09-23)

Bug fixes

... (truncated)

Commits
  • 8ab60aa chore(release): publish v12.1.2 release
  • ab3fb3d chore(release): publish v12.1.2 release
  • 1685a43 fix(express,fastify): keep +json content types on error replies (#17916)
  • 697ff89 fix(express,fastify): read media type version from any accept param
  • 9feedff chore(release): publish v12.1.1 release
  • 8ff59f3 fix(express): map multer array index and invalid field name codes to 400 (#17...
  • 6739656 chore(release): publish v12.1.0 release
  • fb5e699 fix: three typos (subcription x2, propery) (#17833)
  • 2dfba68 chore: update readme
  • 899dbe3 chore(release): publish v12.0.4 release
  • Additional commits viewable in compare view

Updates @nestjs/swagger from 11.4.4 to 12.0.2

Release notes

Sourced from @​nestjs/swagger's releases.

12.0.2

What's Changed

New Contributors

Full Changelog: nestjs/swagger@12.0.1...12.0.2

Release 12.0.1

12.0.1 (2026-08-28)

Bug fixes

Dependencies

Committers: 1

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.

... (truncated)

Commits
  • 8f00eb9 chore(): release v12.0.2
  • bfb2315 fix(swagger-ui): preserve $ characters when building swagger-ui-init.js (#4119)
  • 2bea96a feat: support the HTTP QUERY method (RFC 10008) (#4007)
  • 752e5c7 chore(deps): update dependency supertest to v7.3.0 (#4142)
  • 4faed70 fix(deps): update dependency @​microsoft/tsdoc to v0.17.0 (#4124)
  • d0e7976 fix(deps): update dependency swagger-ui-dist to v5.33.0 (#4128)
  • abce2be fix: declare typescript as an optional peer dependency (#4134)
  • 234c20c fix(standard-schema): promote schema description to parameter object (#4140)
  • 9652868 chore(deps): update dependency oxlint to v1.85.0 (#4141)
  • 92ee181 chore(deps): update nest monorepo to v12.0.4 (#4138)
  • Additional commits viewable in compare view

Updates @nestjs/throttler from 6.5.0 to 6.7.1

Release notes

Sourced from @​nestjs/throttler's releases.

v6.7.1

Patch Changes

  • e8368b3: Set rate limit headers through res.setHeader() when the response has no res.header() method, so the guard no longer throws res.header is not a function on custom HTTP adapters. The logic lives in a new protected setResponseHeader() method that subclasses can override.
  • a482ef9: Coerce numeric strings for limit, ttl and blockDuration to numbers, as returned for example by ConfigService.get<number>() for environment variables. Previously Date.now() + '60000' concatenated instead of adding, which silently corrupted every expiry and X-RateLimit-Reset. A value that is not numeric now fails with an error naming the option and the throttler.
  • a9a28b9: Respect an explicit 0 for limit, ttl and blockDuration in @Throttle() and the module options instead of falling back to the default. blockDuration: 0 now means "no extra block": the in-memory storage rejects requests while the window is full and lets them through again as soon as the oldest hit expires, without recording the rejected ones.
  • bf81677: Import shared interfaces from the public Nest package entry point for Nest 12 compatibility.
  • caaabc9: Stop the in-memory storage from retaining request contexts. It used to schedule one setTimeout per counted hit, and each timer kept the request's AsyncLocalStorage stores (for example an ORM's per-request entity manager) in memory until the TTL expired. It now records when each hit expires and prunes expired hits on access. The idle-record sweep is also no longer tied to the context of the first request. With blockDuration: 0, Retry-After now reports when the oldest hit expires rather than when the window ends.
  • 7703c10: Log a warning when no throttler is configured. The guard limits nothing in that case and previously said nothing at boot, so ThrottlerModule.forRoot() and ThrottlerModule.forRoot([]) looked like a working setup.

v6.7.0

Minor Changes

  • 7004a97: Normalize IPv6 source addresses in the default tracker, and evict expired records from the in-memory storage.

    The built-in getTracker returned req.ip verbatim, so a client holding an IPv6 allocation could send every request from a different address within its own subnet and never share a counter, defeating the rate limit. Addresses are now masked to a /64 before being used as the tracker; the prefix length is configurable via the new ipv6SubnetPrefix module option. IPv4 addresses, IPv4-mapped addresses, the loopback, and custom getTracker implementations are unaffected.

    ThrottlerStorageService also never removed records, so a stream of requests from distinct trackers grew the internal map for the lifetime of the process. Idle records are now swept out once their window has fully elapsed. Limiting behaviour is unchanged: a record is only dropped after every pending hit has expired and any block has lapsed.

    Note that the tracker string for IPv6 clients changes shape (2001:db8:0:1::/64), so storage keys rotate once on upgrade.

v6.6.0

Minor Changes

  • c342bad: Declare the supported Node versions in engines, matching the range the CI matrix tests
  • c625e98: Update to allow for support for Nest version 12
Changelog

Sourced from @​nestjs/throttler's changelog.

6.7.1

Patch Changes

  • e8368b3: Set rate limit headers through res.setHeader() when the response has no res.header() method, so the guard no longer throws res.header is not a function on custom HTTP adapters. The logic lives in a new protected setResponseHeader() method that subclasses can override.
  • a482ef9: Coerce numeric strings for limit, ttl and blockDuration to numbers, as returned for example by ConfigService.get<number>() for environment variables. Previously Date.now() + '60000' concatenated instead of adding, which silently corrupted every expiry and X-RateLimit-Reset. A value that is not numeric now fails with an error naming the option and the throttler.
  • a9a28b9: Respect an explicit 0 for limit, ttl and blockDuration in @Throttle() and the module options instead of falling back to the default. blockDuration: 0 now means "no extra block": the in-memory storage rejects requests while the window is full and lets them through again as soon as the oldest hit expires, without recording the rejected ones.
  • bf81677: Import shared interfaces from the public Nest package entry point for Nest 12 compatibility.
  • caaabc9: Stop the in-memory storage from retaining request contexts. It used to schedule one setTimeout per counted hit, and each timer kept the request's AsyncLocalStorage stores (for example an ORM's per-request entity manager) in memory until the TTL expired. It now records when each hit expires and prunes expired hits on access. The idle-record sweep is also no longer tied to the context of the first request. With blockDuration: 0, Retry-After now reports when the oldest hit expires rather than when the window ends.
  • 7703c10: Log a warning when no throttler is configured. The guard limits nothing in that case and previously said nothing at boot, so ThrottlerModule.forRoot() and ThrottlerModule.forRoot([]) looked like a working setup.

6.7.0

Minor Changes

  • 7004a97: Normalize IPv6 source addresses in the default tracker, and evict expired records from the in-memory storage.

    The built-in getTracker returned req.ip verbatim, so a client holding an IPv6 allocation could send every request from a different address within its own subnet and never share a counter, defeating the rate limit. Addresses are now masked to a /64 before being used as the tracker; the prefix length is configurable via the new ipv6SubnetPrefix module option. IPv4 addresses, IPv4-mapped addresses, the loopback, and custom getTracker implementations are unaffected.

    ThrottlerStorageService also never removed records, so a stream of requests from distinct trackers grew the internal map for the lifetime of the process. Idle records are now swept out once their window has fully elapsed. Limiting behaviour is unchanged: a record is only dropped after every pending hit has expired and any block has lapsed.

    Note that the tracker string for IPv6 clients changes shape (2001:db8:0:1::/64), so storage keys rotate once on upgrade.

6.6.0

Minor Changes

  • c342bad: Declare the supported Node versions in engines, matching the range the CI matrix tests
  • c625e98: Update to allow for support for Nest version 12

6.4.0

6.5.1

Patch Changes

  • 603cb82: handles edge case where multiple clients making frequent requests interfere with each other
Commits
  • 91f4912 Merge pull request #2706 from nestjs/changeset-release/master
  • c5e8c90 chore: version packages
  • 9ec3aa3 Merge pull request #2668 from nestjs/renovate/major-nest-monorepo
  • 5d3b9ae Merge pull request #2712 from nestjs/fix/coerce-numeric-options
  • 4335230 Merge pull request #2711 from nestjs/fix/timer-free-storage
  • a482ef9 fix(guard): coerce numeric string options
  • e082222 chore(deps): update nest monorepo to v12
  • caaabc9 fix(storage): do not retain request contexts in timers
  • 4ab8c63 Merge pull request #2697 from nestjs/renovate/node-24.x
  • c36f011 Merge pull request #2703 from nestjs/renovate/nest-graphql-monorepo
  • Additional commits viewable in compare view
Maintainer changes

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


Updates @nestjs/typeorm from 11.0.2 to 12.0.2

Release notes

Sourced from @​nestjs/typeorm's releases.

Release 12.0.2

What's Changed

New Contributors

Full Changelog: nestjs/typeorm@12.0.1...12.0.2

Release 12.0.1

  • fix: add default condition to exports so CJS can resolve the package (01874dc)

Release 12.0.0

What's Changed

@nestjs/typeorm is now a native ES module, and the major version is aligned with the Nest 12 release line (11.0.3 → 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.

The minimum supported Node version is now >=20.19.0.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, CJS apps still work.

Release 11.0.3

  • chore: warn instead of throwing error, partially revert #2584 (4fbe9a7)
Commits
  • 8618d67 chore(): release v12.0.2
  • b06c8ab Merge pull request #2717 from phankieuphu/fix/async-named-datasource-shutdown
  • 16c80f7 fix(core): register async data source names symmetrically on shutdown
  • eb1c089 fix(core): resolve named data source on shutdown for async registrations
  • a268eeb chore(deps): update dependency lint-staged to v17.6.0 (#2715)
  • 5fc8c04 chore(deps): update dependency @​types/node to v24.19.0 (#2714)
  • 3e225ae chore(deps): update dependency vitest to v5.0.2 (#2713)
  • 565ad6b chore(deps): update nest monorepo to v12.1.0 (#2712)
  • 7fa911e chore(deps): update dependency prettier to v3.9.9 (#2711)
  • 4164538 fix(common): make the default retryAttempts 10 attempts, as documented
  • Additional commits viewable in compare view

Updates @nestjs/cli from 11.0.23 to 12.0.8

Release notes

Sourced from @​nestjs/cli's releases.

Release 12.0.8

What's Changed

Full Changelog: nestjs/nest-cli@12.0.7...12.0.8

Release 12.0.7

What's Changed

New Contributors

Full Changelog: nestjs/nest-cli@12.0.6...12.0.7

Release 12.0.6

What's Changed

New Contributors

Full Changelog: nestjs/nest-cli@12.0.5...12.0.6

Release 12.0.5

What's Changed

New Contributors

Bumps the nestjs-framework group in /Backend with 11 updates:

| Package | From | To |
| --- | --- | --- |
| [@nestjs/common](https://github.com/nestjs/nest/tree/HEAD/packages/common) | `11.1.27` | `12.1.2` |
| [@nestjs/config](https://github.com/nestjs/config) | `4.0.4` | `12.0.1` |
| [@nestjs/core](https://github.com/nestjs/nest/tree/HEAD/packages/core) | `11.1.27` | `12.1.2` |
| [@nestjs/mapped-types](https://github.com/nestjs/mapped-types) | `2.1.1` | `12.0.0` |
| [@nestjs/platform-express](https://github.com/nestjs/nest/tree/HEAD/packages/platform-express) | `11.1.27` | `12.1.2` |
| [@nestjs/swagger](https://github.com/nestjs/swagger) | `11.4.4` | `12.0.2` |
| [@nestjs/throttler](https://github.com/nestjs/throttler) | `6.5.0` | `6.7.1` |
| [@nestjs/typeorm](https://github.com/nestjs/typeorm) | `11.0.2` | `12.0.2` |
| [@nestjs/cli](https://github.com/nestjs/nest-cli) | `11.0.23` | `12.0.8` |
| [@nestjs/schematics](https://github.com/nestjs/schematics) | `11.1.0` | `12.0.6` |
| [@nestjs/testing](https://github.com/nestjs/nest/tree/HEAD/packages/testing) | `11.1.28` | `12.1.2` |


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

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

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

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

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

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

Updates `@nestjs/throttler` from 6.5.0 to 6.7.1
- [Release notes](https://github.com/nestjs/throttler/releases)
- [Changelog](https://github.com/nestjs/throttler/blob/master/CHANGELOG.md)
- [Commits](nestjs/throttler@v6.5.0...v6.7.1)

Updates `@nestjs/typeorm` from 11.0.2 to 12.0.2
- [Release notes](https://github.com/nestjs/typeorm/releases)
- [Commits](nestjs/typeorm@11.0.2...12.0.2)

Updates `@nestjs/cli` from 11.0.23 to 12.0.8
- [Release notes](https://github.com/nestjs/nest-cli/releases)
- [Commits](nestjs/nest-cli@11.0.23...12.0.8)

Updates `@nestjs/schematics` from 11.1.0 to 12.0.6
- [Release notes](https://github.com/nestjs/schematics/releases)
- [Commits](nestjs/schematics@11.1.0...12.0.6)

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

---
updated-dependencies:
- dependency-name: "@nestjs/common"
  dependency-version: 12.1.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/config"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/core"
  dependency-version: 12.1.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/mapped-types"
  dependency-version: 12.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/platform-express"
  dependency-version: 12.1.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/swagger"
  dependency-version: 12.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/throttler"
  dependency-version: 6.7.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/typeorm"
  dependency-version: 12.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/cli"
  dependency-version: 12.0.8
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/schematics"
  dependency-version: 12.0.6
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
- dependency-name: "@nestjs/testing"
  dependency-version: 12.1.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: nestjs-framework
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added backend Imported from docs/ISSUES_100.md (label "backend"). dependencies Imported from docs/ISSUES_100.md (label "dependencies"). labels Oct 12, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend Imported from docs/ISSUES_100.md (label "backend"). dependencies Imported from docs/ISSUES_100.md (label "dependencies").

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants