chore(deps): bump @nestjs/core from 11.1.12 to 11.1.28 in /queueConsumer

[dependabot]

Bumps @nestjs/core from 11.1.12 to 11.1.28.

Release notes

Sourced from @​nestjs/core's releases.

v11.1.28 (2026-07-08)

Bug fixes

• core
  • #17239 fix(core): trigger teardown of SSE producer Observable on client disconnect with interceptor (@​jyx-07)
• common
  • #17257 fix(common): Add missing exception classes to HttpErrorByCode (@​Se3do)
• websockets
  • #17188 fix(websockets): correct type guard to check value not key (@​Se3do)

Enhancements

• core
  • #17241 feat(core): include auto-converted route in legacy route path warning (@​ronielli)

Dependencies

• platform-fastify
  • #17262 chore(deps): bump fastify from 5.8.5 to 5.10.0 (@​dependabot[bot])
• platform-express
  • #17164 fix(deps): update dependency multer to v2.2.0 [security] (@​renovate[bot])

Committers: 4

• Mohammed Said (@​Se3do)
• Ronielli (@​ronielli)
• greymoth (@​greymoth-jp)
• 종윤 (@​jyx-07)

v11.1.27

What's Changed

• fix(core): sse async handlers teardown issue by @​kamilmysliwiec in nestjs/nest#17131
• fix(platform-fastify): forRoutes middleware ending slash by @​kamilmysliwiec in nestjs/nest#17138

Full Changelog: nestjs/nest@v11.1.26...v11.1.27

v11.1.26

What's Changed

• fix(core): post sse endpoint empty response #17098 by @​kamilmysliwiec in nestjs/nest#17099

Full Changelog: nestjs/nest@v11.1.25...v11.1.26

v11.1.25

What's Changed

• fix(microservices): reject pending Redis requests on close by @​yudin-s in nestjs/nest#17024
• fix(core): register SSE close listener before async setup by @​fallintoplace in nestjs/nest#17018
• fix(platform-fastify): remove pathname ending slash by @​kamilmysliwiec in nestjs/nest#17094

New Contributors

• @​fallintoplace made their first contribution in nestjs/nest#17018
• @​DucMinhNe made their first contribution in nestjs/nest#17085

... (truncated)

Commits

• dfaa376 chore(release): publish v11.1.28 release
• 053a316 Merge pull request #17239 from jyx-07/fix/sse-interceptor-teardown
• 8e7a2ee feat(core): include auto-converted route in legacy route path warning
• c5b7164 fix(core): trigger sse observable teardown on disconnect
• 660a124 chore(release): publish v11.1.27 release
• 5c5e9ba fix(core): sse async handlers teardown issue #17128
• aa5c4f1 chore: update readme and package.json
• 9ff83d5 chore(release): publish v11.1.26 release
• 0f398fd test: fix broken unit test
• d152eec fix(core): post sse endpoint empty response #17098
• Additional commits viewable in compare view

[greptile-apps]

Greptile Summary

This PR bumps the NestJS core dependency used by the queue consumer.

• Updates queueConsumer to require @nestjs/core@11.1.28.
• Leaves the rest of the package manifest unchanged.

Confidence Score: 4/5

This should be fixed before merging.

• The manifest requires a new exact dependency version.
• The committed lockfile still points at the old queue consumer dependency version.
• Lockfile-based installs can fail before the queue consumer builds or starts.

queueConsumer/package.json and the pnpm lockfile

Important Files Changed

Filename	Overview
queueConsumer/package.json	Bumps @nestjs/core for the queue consumer package.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
queueConsumer/package.json:31
**Lockfile Still Mismatched**

This manifest now requires exact `@nestjs/core@11.1.28`, but the committed pnpm lockfile still records the queue consumer dependency with the old `11.1.12` specifier and resolution. When CI or the Docker build installs from the committed lockfile, pnpm can reject the install before the queue consumer builds or starts. Please commit the matching lockfile update with this package bump.

_{Reviews (2): Last reviewed commit: "chore(deps): bump @nestjs/core from 11.1..." | Re-trigger Greptile}

[greptile-apps]

Frozen Install Lockfile Mismatch

When CI or deployment runs pnpm with a frozen lockfile, this manifest now requires @nestjs/core@11.1.27 but the PR does not include the matching lockfile change. That can make the queue consumer fail before build or startup instead of installing the dependency graph declared here.

Prompt To Fix With AI

This is a comment left during a code review.
Path: queueConsumer/package.json
Line: 31

Comment:
**Frozen Install Lockfile Mismatch**

When CI or deployment runs pnpm with a frozen lockfile, this manifest now requires `@nestjs/core@11.1.27` but the PR does not include the matching lockfile change. That can make the queue consumer fail before build or startup instead of installing the dependency graph declared here.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Lockfile Still Mismatched

This manifest now requires exact @nestjs/core@11.1.28, but the committed pnpm lockfile still records the queue consumer dependency with the old 11.1.12 specifier and resolution. When CI or the Docker build installs from the committed lockfile, pnpm can reject the install before the queue consumer builds or starts. Please commit the matching lockfile update with this package bump.

Prompt To Fix With AI

This is a comment left during a code review.
Path: queueConsumer/package.json
Line: 31

Comment:
**Lockfile Still Mismatched**

This manifest now requires exact `@nestjs/core@11.1.28`, but the committed pnpm lockfile still records the queue consumer dependency with the old `11.1.12` specifier and resolution. When CI or the Docker build installs from the committed lockfile, pnpm can reject the install before the queue consumer builds or starts. Please commit the matching lockfile update with this package bump.

How can I resolve this? If you propose a fix, please make it concise.