NestJS 11.1.27

NestJS 11.1.27 has been released — a minor patch release that fixes two regression-level issues in Server-Sent Events and Fastify middleware routing. Before you hit that upgrade button, let's check what broke and whether it affects you.

Let's Not Get Carried Away

Version 11.1.27 is a patch release, so expectations should be calibrated. NestJS 11 itself has been stable since its debut, and point releases in the 11.1.x line have been predominantly maintenance-focused. If you're expecting groundbreaking new features, this isn't it — and that's fine. What this release does is fix two genuine bugs that could cause production headaches.

What Actually Changed

Two fixes, both addressing issues that were introduced in earlier 11.1.x releases:

• SSE async handlers teardown fix — Server-Sent Events endpoints using async handlers could fail to clean up resources properly when connections were terminated. This manifested as dangling database connections and memory leaks in long-running SSE streams. The fix ensures proper teardown of async handler contexts.
• Fastify platform middleware ending slash — When using forRoutes with the Fastify adapter, middleware registered with trailing-slash route patterns was not matching correctly. This could cause authentication or logging middleware to be skipped on certain routes.

The Skeptic's Upgrade Guide

Before you run npm update across all your services, consider whether these fixes apply to you:

• Are you using SSE (Server-Sent Events)? The teardown fix matters if you have long-lived event streams that clients frequently disconnect from. Without the fix, you risk memory accumulation over time.
• Are you on platform-fastify? The trailing-slash middleware fix only affects the Fastify adapter (not the default Express adapter). If you're on Express, this change is irrelevant to you.
• Are you on an older NestJS version? The update from 11.0.x or 10.x to 11.1.27 is a bigger jump. Both of these fixes are 11.1.x specific, so a major version upgrade involves more than just these patches.

The Verdict

If you're on NestJS 11.1.x and using Fastify or SSE, update now — these are real bugs that can cause runtime issues. If you're on the Express adapter without SSE usage, this release offers nothing new. Skip it and wait for 11.2 when feature work resumes.