RabbitMQ 4.1.0 can't connect (frame_max bumped)

[slyk]

The RabbitMQ 4.1.0 is out and updates on ubuntu servers automatically.
Then all our services using @golevelup/nestjs-rabbitmq/AmqpConnection can't connect and I can't find any config for frameMax.

>,<<"46.202.143.29:39450 -> 16.22.15.6:5672">>,"3s","negotiated frame_max = 4096 is lower than the minimum allowed value (8192)"]}
2025-04-16T14:15:06.519010+03:00 error: FORMATTER CRASH: {"closing AMQP connection ~tp (~ts):~nfailed to negotiate connection parameters: ~ts",[<0.2540.0>,<<"4.20.14.2:39458 -> 16.22.15.6:5672">>,"3s","negotiated frame_max = 4096 is lower than the minimum allowed value (8192)"]}
2025-04-16T14:15:06.698826+03:00 error: FORMATTER CRASH: {"closing AMQP connection ~tp (~ts):~nfailed to negotiate connection parameters: ~ts",[<0.2585.0>,<<"4.20.14.2:39464 -> 16.22.15.6:5672">>,"3s","negotiated frame_max = 4096 is lower than the minimum allowed value (8192)"]}

On the release notes of the rabbitMQ told that we should upgrade to amqlib v0.10.7 to still make connections.

Can we bump the version in golevelup?
Or maybe someone give advice, if I set dependency of amqlib in own project will it be used?

[underfisk]

@slyk It seems to be an issue with the underlying driver, the amqlib upgrade to v0.10.7 was performed in #1003 therefore I'm hoping that once we release you're able to test with the most updated version

[noghartt]

I saw that we're able to customize the frameMax parameter on the amqplib, maybe a good idea would be allowing to pass it inside the connectionOptions object too.

Also, opened a PR to a fix on URI validation to allow pass the frameMax, I can take a look on the fix for that, by the way.

#1009

[underfisk]

@noghartt I appreciate if you could help us out with that change. I'm down to allow the customization of frameMax

[underfisk]

#1020 should bring the support for query param such as frameMax