what stackpulse tracks
NestJS releases from GitHub
StackPulse watches NestJS release notes and keeps the original source link close to every summary.
A progressive Node.js framework for scalable server-side apps StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches NestJS release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release adds configurable limits for message sizes, buffering, pending work, and multipart requests across WebSocket, Socket.IO, TCP, gRPC, Redis, RabbitMQ, and Fastify. It also changes several defaults and runtime behaviors, including TCP binding to localhost when the host is empty, multipart part limits, streamed-response serialization, and earlier startup validation; the supplied notes end mid-section, so additional changes may be omitted.
Applications using TCP, WebSocket, Socket.IO, multipart uploads, or startup-validated providers and middleware may need configuration or code changes to accommodate the new defaults and validation.
Review network binding and resource-limit settings, and test application startup for configurations now rejected as invalid.
This release is a broad bug-fix update across NestJS common, core, and related integrations. It improves validation and request handling, middleware routing and enhancer behavior, and stream/SSE error handling, including safeguards that prevent internal error messages from being exposed in responses.
NestJS v11 applications using validation pipes, middleware, global enhancers, file streams, SSE, or HTTP error handling may see corrected behavior; apps with request-scoped class global enhancers may encounter a startup failure.
Upgrade to v11.2.8 and verify startup for applications that register global enhancers with request-scoped dependencies.
This release introduces new configuration options for event streaming, WebSocket adapters, and validation pipes, along with several behavior changes and bug fixes. Notable changes include deprecation warnings for certain microservice patterns and updates to middleware exclusion behavior.
Developers using `@EventPattern()` handlers with `ClientProxy#send()` on certain microservices will see deprecation warnings and need to prepare for future breaking changes.
Review deprecation warnings for `@EventPattern()` handlers and update middleware exclusions if using `MiddlewareConsumer.exclude()`.
NestJS v12 introduces ESM-ready packages, Standard Schema support, a rebuilt CLI, and native observability. It requires Node.js v20.19+ or v22.12+ and includes several breaking changes.
All NestJS users upgrading from v11 to v12 are affected, particularly those using custom bootstrapping, bundler configurations, or older Node.js versions.
Follow the migration guide and use `nest upgrade` to automate parts of the upgrade process.