NestJS 11.1.29
NestJS 11.1.29 landed on August 10, 2026, and let's not get carried away — this is a patch release full of small, surgical fixes, not a headline-grabbing feature drop. That doesn't mean you should ignore it, though. Patch releases are where the framework quietly pays down its debt, and this one touches a few spots worth knowing about.
What's Actually In It
Two features made the cut. The first: the file type validator in @nestjs/common now accepts an override mimetype option, which is useful when you're validating uploads against a stricter or custom MIME list. The second is more interesting for real-time apps — the core now supports SSE comments, and the SSE retry field is now serialized correctly when its value is zero.
Beyond that, it's a fix parade: the microservices package corrects the pub/sub client type in Redis listeners, the Express adapter maps a missing multer field nesting error, and the gRPC client is properly nullified on close when a graceful shutdown attempt fails.
Where It Could Bite
The change to watch is in the core module: NestJS now stops import lookup after the first direct export match. In plain English, if a module re-exports the same provider through multiple paths, the resolver won't keep walking the graph once it finds a direct hit. For the vast majority of apps this changes nothing — but if you've been relying on quirky multi-path re-export behavior, this is the release that may surface it.
There's also a fix that drops the g flag from middleware overlap regexes. That's a correctness win (stateful regexes with the global flag are a classic source of alternating-match bugs), but it also means middleware matching patterns were, in effect, behaving differently than documented before.
The Bottom Line
No breaking changes, no migration notes, eleven merged pull requests, ten first-time contributors. If you're running 11.x, upgrading is low-risk — the usual caveat applies: read the two core-resolution changes above and run your test suite before you ship to production.