chore(deps-dev): bump @nestjs/common from 9.4.3 to 11.1.3

[dependabot]

Bumps @nestjs/common from 9.4.3 to 11.1.3.

Release notes

Sourced from @​nestjs/common's releases.

v11.1.3 (2025-06-06)

Bug fixes

• core
  • #15201 fix(core): gracefully shutdown the app when repl exits (@​dzhlobo)

Enhancements

• common
  • #15209 feat: add string array type to disposition (@​fjodor-rybakov)
• common, core
  • #15203 feat(core): defer initialization connected microservice (@​isaryy)

Dependencies

• platform-express
  • #15232 chore(deps): bump multer from 2.0.0 to 2.0.1 (@​dependabot[bot])

Committers: 3

• Dmitry Zhlobo (@​dzhlobo)
• @​fjodor-rybakov
• @​isaryy

v11.1.2 (2025-05-26)

Bug fixes

• microservices
  • #15172 fix(microservices): support custom strategy in async usefactory config (@​mag123c)
  • #15166 fix(microservice): prevent error logs during redis client shutdown (@​janroker)

Dependencies

• common
  • #15185 chore(deps): bump file-type from 20.5.0 to 21.0.0 (@​dependabot[bot])
• platform-express
  • #15159 chore(deps): bump multer from 1.4.5-lts.2 to 2.0.0 (@​dependabot[bot])

Committers: 2

• JaeHo Jang (@​mag123c)
• Jan Roček (@​janroker)

v11.1.1 (2025-05-14)

Bug fixes

• core
  • #15056 fix(core): HTTP adapter error mapping (@​maxbronnikov10)
• microservices
  • #15062 fix(microservices): ensure all redis and amqp client closes properly (@​yatin166)
  • #15032 fix(microservices): ensure all the amqp connections are closed properly (@​yatin166)
  • #15020 fix(microservices): ensure all redis connections are closed (@​yatin166)
• core, platform-fastify
  • #15061 fix(core): bring back getHeader and appendHeader methods from AbstractHttpAdapter (@​micalevisk)
• platform-express

... (truncated)

Commits

• 1613f50 chore(@​nestjs) publish v11.1.3 release
• 1e1bcea Merge pull request #15209 from fjodor-rybakov/fix/add-missing-disposition-type
• 4b74585 feat: add string array type to disposition
• 1c4a20a feat(core): defer initialization connected microservice
• 32b5feb chore(@​nestjs) publish v11.1.2 release
• 8863c12 chore(deps): bump file-type from 20.5.0 to 21.0.0
• f262812 chore: update package.json
• 2cccff1 chore(@​nestjs) publish v11.1.1 release
• 8a93b85 chore(common): fix incorrect comment
• 0e95b3b refactor(common): move logger utils to dedicated files
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nestjs/​common@​9.4.3 ⏵ 11.1.3		+5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		[email protected] has a Critical CVE. CVE: GHSA-h755-8qp9-cq85 protobufjs Prototype Pollution vulnerability (CRITICAL) Affected versions: >= 7.0.0 < 7.2.5; >= 6.10.0 < 6.11.4 Patched version: 6.11.4 From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a High CVE. CVE: GHSA-g954-5hwp-pp24 Prototype Pollution in protobufjs (HIGH) Affected versions: >= 6.11.0 < 6.11.3; >= 6.10.0 < 6.10.3 Patched version: 6.10.3 From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@grpc/[email protected] has a Medium CVE. CVE: GHSA-7v5v-9h63-cj86 @grpc/grpc-js can allocate memory for incoming messages well above configured limits (MODERATE) Affected versions: >= 1.10.0 < 1.10.9; >= 1.9.0 < 1.9.15; < 1.8.22 Patched version: 1.10.9 From: package-lock.json → npm/@nestjs/[email protected] → npm/[email protected] → npm/@grpc/[email protected] ℹ Read more on: This package | This alert | What is a medium CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known medium severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@grpc/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Copyleft License. Location: Package overview From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What do I need to know about license files? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Determine whether use of copyleft material works for you Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Copyleft License. Location: Package overview From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What do I need to know about license files? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Determine whether use of copyleft material works for you Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report