chore(deps): update dependency body-parser to ^2.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
body-parser	^2.2.1 → ^2.3.0

---

Release Notes

expressjs/body-parser (body-parser)

v2.3.0

Compare Source

========================

• fix: use static exports instead of lazy getters to improve ESM compatibility
• feat: add subpath exports for individual parsers
• fix: improve limit option validation (#​698)
  • Invalid limit values (e.g. unparseable strings or NaN) now throw instead of being silently ignored, which previously disabled size limit enforcement
  • null and undefined fall back to the default 100kb limit
• deps:
  • content-type@^2.0.0
  • http-errors@^2.0.1
  • iconv-lite^0.7.2
  • qs@^6.15.2
  • raw-body@^3.0.2
  • type-is@^2.1.0

v2.2.2

Compare Source

=========================

• deps: qs@^6.14.1
• refactor(json): simplify strict mode error string construction

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[underfisk]

@copilot Review the CI issue, it seems to be related to a mistmatch of Nest versions

[Copilot]

@copilot Review the CI issue, it seems to be related to a mistmatch of Nest versions

I reviewed the failing CI run (27575961362) and the failure is in packages/hasura tests, where Nest cannot resolve DiscoveryService dependencies (ModulesContainer). This lines up with a Nest dependency graph mismatch: the install resolves multiple peer variants of @nestjs/core/@nestjs/platform-express in the lock graph, so DI tokens don’t line up at runtime. I did not push a code change yet because the viable fix appears to be a lockfile/Nest alignment update (likely rebasing this branch onto latest base or refreshing lockfile with the same Nest peer set), which is broader than the body-parser bump itself.

[underfisk]

@copilot Review the CI issue, it seems to be related to a mistmatch of Nest versions

I reviewed the failing CI run (27575961362) and the failure is in packages/hasura tests, where Nest cannot resolve DiscoveryService dependencies (ModulesContainer). This lines up with a Nest dependency graph mismatch: the install resolves multiple peer variants of @nestjs/core/@nestjs/platform-express in the lock graph, so DI tokens don’t line up at runtime. I did not push a code change yet because the viable fix appears to be a lockfile/Nest alignment update (likely rebasing this branch onto latest base or refreshing lockfile with the same Nest peer set), which is broader than the body-parser bump itself.

@copilot in another PR please address the issue then, run pnpm install and make sure that the issues are gone

[Copilot]

@underfisk I've opened a new pull request, #1250, to work on those changes. Once the pull request is ready, I'll request review from you.