Skip to content

chore(dev-deps): Bump amqlib for node-integration-tests to 0.10.7 #16074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2025

Conversation

mydea
Copy link
Member

@mydea mydea commented Apr 16, 2025

See https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0. the rabbitmq image v4.1.0 requires this new amqlib version to work.

Quote of braking changes in rabbitmq 4.1.0

Before a client connection can negotiate a maximum frame size (frame_max), it must authenticate
successfully. Before the authenticated phase, a special lower frame_max value
is used.

With this release, the value was increased from the original 4096 bytes to 8192
to accommodate larger JWT tokens.

Clients that do override frame_max now must use values of 8192 bytes or greater.
We recommend using the default server value of 131072: do not override the frame_max
key in rabbitmq.conf and do not set it in the application code.

amqplib is a popular client library that has been using
a low frame_max default of 4096. Its users must upgrade to a compatible version
(starting with 0.10.7) or explicitly use a higher frame_max.

@mydea mydea self-assigned this Apr 16, 2025
@mydea mydea marked this pull request as ready for review April 16, 2025 10:07
@mydea mydea requested review from lforst and chargome April 16, 2025 10:07
@mydea mydea merged commit 55cb92c into develop Apr 16, 2025
164 checks passed
@mydea mydea deleted the fn/bump-amqlib branch April 16, 2025 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants