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.
NestJS 11.2.9 fixes wildcard middleware behavior for excluded routes across versions and corrects handling of certain absolute-form request targets in the Fastify platform. It also updates Multer and Fastify dependencies to address a named security advisory and advisories affecting Fastify.
Users of NestJS core middleware, the Express platform, or the Fastify platform are affected by the respective fixes and dependency updates.
Upgrade to NestJS 11.2.9 to receive the middleware and Fastify request-handling fixes and the dependency security updates.
Adds a native Node.js HTTP platform adapter. The release also fixes issues across core, HTTP platform adapters, and microservices, including middleware behavior, error handling, streaming responses, and transport retries.
NestJS users may benefit from the new native Node.js HTTP adapter and reliability fixes, particularly those using Express, Fastify, WebSockets, or microservices transports.
Upgrade to v12.3.0 to receive the adapter addition, bug fixes, and marked security dependency update.
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 primarily addresses a security vulnerability in the `multer` dependency and fixes an issue with error handling for unexpected file field names.
Users relying on `@nestjs/platform-express` with file uploads are affected by the security fix and error handling changes.
Upgrade to v11.2.6 to mitigate the security vulnerability and ensure proper error handling.
This release introduces several enhancements and bug fixes across the NestJS framework, including support for array of global prefixes, built-in CSRF protection, and adapter-agnostic cookies.
Developers using NestJS for web applications will benefit from enhanced security features and improved middleware handling.
Update to v12.1.0 to take advantage of new security features and bug fixes.
This release focuses on hardening the TCP transport in the `@nestjs/microservices` package against potential security risks from hostile peers.
Users of `@nestjs/microservices` with TCP transport are affected by this security improvement.
Upgrade to v11.2.5 to benefit from the enhanced security measures.