Overview - Nestjs-tools

nestjs-tools

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/fastify-upload-file-interceptor-body-fields
36bf7f5e fix(nestjs-tools-amqp-transport): warn when using amq.rabbitmq.reply-to with noAck=false Add explicit warning when user configures amq.rabbitmq.reply-to with noAck=false, which is incompatible with RabbitMQ 4.x. This helps users understand the configuration issue before encountering runtime errors. The warning suggests either: - Setting noAck=true in options - Using a custom reply queue name instead Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
21 days ago by getlarge
Succeeded
fix/fastify-upload-file-interceptor-body-fields
6cd7dde6 fix(nestjs-tools-amqp-transport): force noAck=true for amq.rabbitmq.reply-to in RabbitMQ 4 RabbitMQ 4 doesn't allow acknowledgments on the special amq.rabbitmq.reply-to pseudo-queue. This was causing test failures with: "PRECONDITION_FAILED - reply consumer cannot acknowledge" When using the direct reply-to mechanism, we now force noAck=true regardless of the user's noAck configuration, since acks are not supported on this queue. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
21 days ago by getlarge
Failed
fix/fastify-upload-file-interceptor-body-fields
23e78f06 fix(nestjs-tools-amqp-transport): upgrade amqplib to 0.10.9 for RabbitMQ 4 compatibility RabbitMQ 4.1.0+ requires minimum frame_max of 8192, but amqplib <0.10.7 defaults to 4096, causing connection negotiation failures. This was causing CI tests to hang with continuous reconnection attempts until timeout. Updated peer dependency from "0.10" to ">=0.10.7" to ensure compatibility. Fixes connection errors: "negotiated frame_max = 4096 is lower than the minimum allowed value (8192)" Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
21 days ago by getlarge
Succeeded
fix/fastify-upload-file-interceptor-body-fields
7a1dbf2e chore: fix formatting issues Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
21 days ago by getlarge