fix(deps): update amqplib to 0.10.6 for rmq 4.1+ compatibility #2673
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
25c7ea3 to
9bec124
Compare
|
Changed amqplib to 0.10.7 in accordance with the release notes recommendations of RabbitMQ 4.1.0 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
RabbitMQ health check tests fail when using RabbitMQ 4.1.0 or higher with the error:
"negotiated frame_max = 4096 is lower than the minimum allowed value (8192)"This blocks all CI/CD pipelines and affects any project using RabbitMQ 4.1+ with @nestjs/terminus.
Issue Number: #2672
What is the new behavior?
amqplibfrom0.10.5to0.10.6Does this PR introduce a breaking change?
Other information
Root cause
RabbitMQ 4.1.0 (April 2025) increased the minimum pre-authentication
frame_maxfrom 4096 to 8192 bytes to accommodate larger JWT tokens.Solution
amqplib 0.10.6 includes the fix that automatically negotiates compatible frame_max values with RabbitMQ 4.1+.
References
RabbitMQ 4.1.0 Release Notes, amqplib issue #791