# nestjs/release
NestJS v12.2.0
importance: mediumbreakingdeprecationmigrationfeature
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.
affected
Developers using `@EventPattern()` handlers with `ClientProxy#send()` on certain microservices will see deprecation warnings and need to prepare for future breaking changes.
action
Review deprecation warnings for `@EventPattern()` handlers and update middleware exclusions if using `MiddlewareConsumer.exclude()`.
release_signals
-Deprecation warning for `@EventPattern()` handlers that reply to `ClientProxy#send()` on TCP, Redis, NATS, MQTT, and RabbitMQ. In the next major version, event handlers will not reply to `send()`.
!`@EventPattern()` handlers that reply to `ClientProxy#send()` on TCP, Redis, NATS, MQTT, and RabbitMQ are now deprecated and will log a warning.
+`@Sse({ maxPendingDataLength })` to limit event data waiting for a client.
+`IoAdapter` and `WsAdapter` now support `maxConcurrentMessages` to limit messages handled at once.
+`ValidationPipe` now has `maxErrorMessagesLength` to limit validation error messages.
+Kafka `parser.maxMessageSize` to limit message size after decompression.
+TCP server `drainTimeout` to disconnect peers with unread responses.
migration_steps1 steps
- 01Update `@nestjs/core` together with `@nestjs/platform-express` or `@nestjs/platform-fastify` to ensure middleware exclusions work correctly with router matching options.
# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.