Skip to content

chore: bump the nestjs group across 1 directory with 8 updates - #3736

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nestjs-43b4da70e8
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nestjs-43b4da70e8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the nestjs group with 8 updates in the / directory:

Package From To
@nestjs/axios 4.0.1 12.0.2
@nestjs/config 4.0.4 12.1.1
@nestjs/jwt 11.0.2 12.0.5
@nestjs/passport 11.0.5 12.0.2
@nestjs/schedule 6.1.3 12.0.4
@nestjs/swagger 11.4.7 12.1.2
@nestjs/throttler 6.5.0 6.7.1
@nestjs/typeorm 11.0.3 12.0.3

Updates @nestjs/axios from 4.0.1 to 12.0.2

Release notes

Sourced from @​nestjs/axios's releases.

Release 12.0.2

Bug fixes

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

Release 12.0.1

What's Changed

New Contributors

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

Release 12.0.0

What's Changed

@nestjs/axios is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 5.x — 4.0.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 / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root:

import { HttpModule, HttpService } from '@nestjs/axios';

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 { HttpModule, HttpService } = require('@nestjs/axios');

This is why the supported Node range is now declared explicitly:

"engines": {
</tr></table> 

... (truncated)

Commits
  • 4ec9468 chore(): release v12.0.2
  • 1e505e4 fix(http): abort the underlying request on unsubscription (#1840)
  • d30bfd5 chore(deps): update nest monorepo to v12.5.0 (#1843)
  • 4baf0b6 chore(deps): update dependency prettier to v3.10.1 (#1842)
  • 2c2fbc0 chore(deps): update dependency prettier to v3.10.0 (#1841)
  • 818db23 chore(deps): update dependency vite to v8.3.8 (#1839)
  • ababa59 chore(deps): update dependency oxlint to v1.93.0 (#1838)
  • 3986cab chore(deps): update nest monorepo to v12.4.2 (#1837)
  • 7e5bea5 chore(deps): update dependency vite to v8.3.7 (#1836)
  • 291bbe4 chore(deps): update dependency axios to v1.21.1 (#1835)
  • Additional commits viewable in compare view

Updates @nestjs/config from 4.0.4 to 12.1.1

Release notes

Sourced from @​nestjs/config's releases.

Release 12.1.1

Dependencies

Full Changelog: nestjs/config@12.1.0...12.1.1

Release 12.1.0

Security

This release fixes several security issues in how ConfigService resolves property paths and how ConfigModule.forRoot() loads and validates environment variables. See GHSA-q989-84g5-qg72 for details. Upgrading is recommended.

Behavior changes

Some fixes change what ConfigService returns. Please review them before upgrading:

  • Property paths only resolve members a configuration object defines (own properties and members of your own classes). Members inherited from built-ins resolve to undefined, e.g. get('database.toString'), get('constructor.prototype') or get('cert.length') for a Buffer. set() never writes through them, and paths through __proto__, constructor or prototype are ignored.
  • Validated variables take precedence:
    • A variable that the validator maps to undefined is no longer served from process.env. get(key, defaultValue) returns the default.
    • A variable that a validationSchema declares and removes (e.g. Joi .strip()) is no longer merged back. Undeclared variables are still kept.
    • With skipProcessEnv: true and a validationSchema, undeclared variables from process.env are no longer served. Declared ones still are. A validate function's output is served as it is.
    • With validatePredefined: false, a predefined variable now takes precedence over a different value from the env file, and get() returns it as it is.
    • A second validated forRoot() no longer replaces the converted values of another one.
  • expandVariables:
    • Expanded values are assigned to process.env after validation, not before.
    • Several env files are expanded once, so $ and \$ in earlier files are no longer expanded again.
    • With override: true, a variable's reference to itself (e.g. PATH=/opt/bin:$PATH) expands to its previous value.
  • Env files: a value containing a NUL character now fails startup instead of being truncated in process.env. __proto__ keys returned by a custom parser are ignored.
  • ConfigService.set():
    • Dependent variables are re-expanded from the definitions loaded at startup. The env files are not read again.
    • Values passed to earlier set() calls and variables set in the environment are kept.
    • The expandVariables.processEnv target is honored.
    • A re-expanded value longer than 128 KiB throws.
  • Load order:
    • ConfigService from a plain imports: [ConfigModule] or ConfigModule.forFeature() is provided once forRoot() has merged its load factories.
    • ConfigModule.envVariablesLoaded (used by ConditionalModule.registerWhen()) waits until every forRoot() in progress has loaded its environment variables.
  • Validation errors no longer include the rejected value: Joi pattern() messages leave it out, and a quoted value is replaced with [redacted].

Features

  • validate may be an async function. A rejected promise stops startup.
  • ConfigService.set() re-interpolates variables that depend on the changed key, including chains of references (#2463).

Bug fixes

  • override: true takes precedence when expanding variables (#2465).
  • get('_PROCESS_ENV_VALIDATED') no longer returns the internal snapshot of validated variables.

Deprecations

... (truncated)

Commits

Updates @nestjs/jwt from 11.0.2 to 12.0.5

Release notes

Sourced from @​nestjs/jwt's releases.

Release 12.0.5

Bug fixes

Full Changelog: nestjs/jwt@12.0.4...12.0.5

Release 12.0.4

Bug fixes

Full Changelog: nestjs/jwt@12.0.3...12.0.4

Release 12.0.3

What's Changed

New Contributors

Full Changelog: nestjs/jwt@12.0.2...12.0.3

Release 12.0.2

What's Changed

New Contributors

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

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
</tr></table>

... (truncated)

Commits
  • b6e28a8 chore(): release v12.0.5
  • 11a32a6 chore(deps): update nest monorepo to v12.5.0 (#2321)
  • 2d0c5da chore(deps): update dependency prettier to v3.10.1 (#2320)
  • efa2fe1 chore(deps): update dependency prettier to v3.10.0 (#2319)
  • 0e0b866 fix(jwt): prioritize call-level asymmetric keys over module secret (#2318)
  • ca13520 chore(deps): update dependency oxlint to v1.93.0 (#2317)
  • a480238 chore(deps): update nest monorepo to v12.4.2 (#2316)
  • 7695560 chore(deps): update dependency oxlint to v1.92.0 (#2315)
  • 45c58d6 chore(deps): update nest monorepo to v12.4.0 (#2314)
  • d9deff3 chore(): release v12.0.4
  • Additional commits viewable in compare view

Updates @nestjs/passport from 11.0.5 to 12.0.2

Release notes

Sourced from @​nestjs/passport's releases.

Release 12.0.2

Bug fixes

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

Release 12.0.1

Bug fixes

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

Release 12.0.0

What's Changed

@nestjs/passport 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 (e.g. @nestjs/passport/dist/auth.guard) are no longer resolvable — import from the package root:

import { AuthGuard, PassportModule, PassportStrategy } from '@nestjs/passport';

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 { AuthGuard, PassportModule } = require('@nestjs/passport');

This requires Node.js 20.19+ or 22.12+ (where require(esm) is enabled by default). On older Node versions you must either upgrade Node or move your app to ESM.

AuthGuard no longer forwards module options to passport.authenticate()

defaultStrategy and property — options that belong to PassportModule.register(), not to Passport itself — were being passed straight through to passport.authenticate(), where they could collide with strategy-level options. They are now stripped before the call, so a strategy only ever receives real AuthenticateOptions.

The signature of getAuthenticateOptions() changed accordingly:

// before
getAuthenticateOptions(
  context: ExecutionContext,
): Promise<IAuthModuleOptions> | IAuthModuleOptions | undefined;
</tr></table>

... (truncated)

Commits
  • 6f16823 chore(): release v12.0.2
  • 72aba26 chore(deps): update nest monorepo to v12.5.0 (#2363)
  • 3f07685 chore(deps): update dependency prettier to v3.10.1 (#2362)
  • 04a1e12 chore(deps): update dependency prettier to v3.10.0 (#2361)
  • 479871c chore(deps): update dependency oxlint to v1.93.0 (#2360)
  • bcb3224 chore(deps): update nest monorepo to v12.4.2 (#2359)
  • e6b9b7e fix(memoize): key strategy arrays apart from single strategy names (#2358)
  • 296521a fix(memoize): cache guards in a map, not a plain object (#2357)
  • c1bbcac chore(deps): update nest monorepo to v12.4.0 (#2355)
  • 580a40d chore(deps): update dependency oxlint to v1.92.0 (#2356)
  • Additional commits viewable in compare view

Updates @nestjs/schedule from 6.1.3 to 12.0.4

Release notes

Sourced from @​nestjs/schedule's releases.

Release 12.0.4

Bug fixes

Full Changelog: nestjs/schedule@12.0.3...12.0.4

Release 12.0.3

Bug fixes

Full Changelog: nestjs/schedule@12.0.2...12.0.3

Release 12.0.2

  • feat(scheduler): add generic return type parameter to getInterval and getTimeout (a178f1b)
  • fix(cron): do not resurrect a deleted job after its initialDelay elapses (4473390)

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:

</tr></table> 

... (truncated)

Commits
  • 3c29c58 chore(): release v12.0.4
  • 9cab45d chore(deps): update nest monorepo to v12.5.0 (#2417)
  • 8c55228 chore(deps): update dependency prettier to v3.10.1 (#2416)
  • a8e320a chore(deps): update dependency prettier to v3.10.0 (#2415)
  • 23dd72e fix: skip aliased providers when exploring scheduled methods (#2413)
  • f2f7299 chore(deps): update dependency vite to v8.3.8 (#2414)
  • acd5c3a chore(deps): update dependency oxlint to v1.93.0 (#2412)
  • 04e0cf1 chore(deps): update nest monorepo to v12.4.2 (#2411)
  • 6ba1880 chore(deps): update dependency vite to v8.3.7 (#2410)
  • d89e448 chore(deps): update dependency oxlint to v1.92.0 (#2409)
  • Additional commits viewable in compare view

Updates @nestjs/swagger from 11.4.7 to 12.1.2

Release notes

Sourced from @​nestjs/swagger's releases.

Release 12.1.2

Bug fixes

Full Changelog: nestjs/swagger@12.1.1...12.1.2

Release 12.1.1

Bug fixes

Dependencies

Full Changelog: nestjs/swagger@12.1.0...12.1.1

... (truncated)

Commits
  • 28385b5 chore(): release v12.1.2
  • 49ace31 fix(schema): keep explicit array items next to a combinator (#4277)
  • 62b5c99 chore(deps): update nest monorepo to v12.5.0 (#4286)
  • 0675d8b chore(deps): update dependency prettier to v3.10.1 (#4283)
  • bd69a74 fix(explorer): document class-level params on inherited routes (#4284)
  • 92c5afe chore(deps): update dependency prettier to v3.10.0 (#4282)
  • d0ddcd6 fix(schema): keep Object typed query properties inline (#4275)
  • fae18ac fix(plugin): emit an enum array for enum member types (#4279)
  • f919d2f fix(type-helpers): do not stack transformers in IntersectionType (#4274)
  • f30cbb4 fix(swagger-ui): serialize method shorthand options into valid js (#4276)
  • 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.3 to 12.0.3

Release notes

Sourced from @​nestjs/typeorm's releases.

Release 12.0.3

Bug fixes

  • fix(core): keep object map entities when auto loading entities by @​RaphaelFakhri in nestjs/typeorm#2753
  • fix(core): check mongodb before tree repositories and test e2e (5d6362d)
  • fix(core): provide tree repository for entity schema trees (365a578)
  • fix(decorators): accept data source options in inject repository (2bf9505)
  • fix(common): resolve data source names in one place (7cd2256)

Other changes

  • refactor(common): merge data source name resolvers into one helper (7df73a6)

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

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.

Commits
  • 2e3a2d9 chore(): release v12.0.3
  • 71c6fb7 chore: describe the package on npm (#2755)
  • a144a43 chore(deps): update nest monorepo to v12.3.3 (#2754)
  • 7f532c3 fix(core): keep object map entities when auto loading entities (#2753)
  • 04b6773 chore(deps): update dependency oxlint to v1.91.0 (#2751)
  • 3034a65 chore(deps): update dependency vitest to v5.1.0 (#2750)
  • 742b0d5 chore(deps): update dependency release-it to v21.1.2 (#2749)
  • 6af4384 chore(deps): update nest monorepo to v12.3.2 (#2746)
  • e4c3dc6 chore(deps): update dependency oxlint to v1.90.0 (#2744)
  • f376944 ci: migrate circleci config to version 2.1 (#2745)
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from a team as a code owner November 11, 2026 18:39
@dependabot
dependabot Bot requested a review from steven-sheehy November 11, 2026 18:39
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Nov 11, 2026
@dependabot dependabot Bot changed the title chore: bump the nestjs group with 8 updates chore: bump the nestjs group across 1 directory with 8 updates Nov 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/nestjs-43b4da70e8 branch 3 times, most recently from 1ecfcee to 7c9e84d Compare November 17, 2026 13:59
Bumps the nestjs group with 8 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@nestjs/axios](https://github.com/nestjs/axios) | `4.0.1` | `12.0.2` |
| [@nestjs/config](https://github.com/nestjs/config) | `4.0.4` | `12.1.1` |
| [@nestjs/jwt](https://github.com/nestjs/jwt) | `11.0.2` | `12.0.5` |
| [@nestjs/passport](https://github.com/nestjs/passport) | `11.0.5` | `12.0.2` |
| [@nestjs/schedule](https://github.com/nestjs/schedule) | `6.1.3` | `12.0.4` |
| [@nestjs/swagger](https://github.com/nestjs/swagger) | `11.4.7` | `12.1.2` |
| [@nestjs/throttler](https://github.com/nestjs/throttler) | `6.5.0` | `6.7.1` |
| [@nestjs/typeorm](https://github.com/nestjs/typeorm) | `11.0.3` | `12.0.3` |



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

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

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

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

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

Updates `@nestjs/swagger` from 11.4.7 to 12.1.2
- [Release notes](https://github.com/nestjs/swagger/releases)
- [Commits](nestjs/swagger@11.4.7...12.1.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.3 to 12.0.3
- [Release notes](https://github.com/nestjs/typeorm/releases)
- [Commits](nestjs/typeorm@11.0.3...12.0.3)

---
updated-dependencies:
- dependency-name: "@nestjs/axios"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
- dependency-name: "@nestjs/config"
  dependency-version: 12.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
- dependency-name: "@nestjs/jwt"
  dependency-version: 12.0.4
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
- dependency-name: "@nestjs/passport"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
- dependency-name: "@nestjs/schedule"
  dependency-version: 12.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
- dependency-name: "@nestjs/swagger"
  dependency-version: 12.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
- dependency-name: "@nestjs/throttler"
  dependency-version: 6.7.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nestjs
- dependency-name: "@nestjs/typeorm"
  dependency-version: 12.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nestjs
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/nestjs-43b4da70e8 branch from 7c9e84d to f9a1653 Compare November 17, 2026 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants