Releases: amqp-node/amqplib
v2.0.1
v2.0.0
BREAKING CHANGE
heartbeat: 0 now correctly disables heartbeats, sending 0 in the ConnectionTuneOk frame regardless of the server's suggestion. This aligns with the AMQP 0-9-1 spec, which defines heartbeat=0 as "disabled".
Previously, 0 was passed through negotiate() which treated it as "no preference", causing the server's suggested value to be used instead.
Migration: if you are passing heartbeat: 0 and want to preserve the old behaviour of accepting the server's value, omit the option or pass null instead.
1.2.0
Add bundled TypeScript type definitions (fixes #843)
For full history see CHANGELOG.md.
v0.8.0
amqplib still works with NodeJS v0.6 through v16, but future versions will not be tested for compatibility with NodeJS < v10.
This is to unlock other improvements that can now be made, like
- using the built-in
Promiseobject - updating or switching libraries that previously couldn't be updated, because they had dropped support for older NodeJS
- removing code that is now covered in the standard library, e.g., checking whether a number is an integer
This release also includes an improvement to TLS connections for people using an AMQP server behind a load balancer. amqplib will now copy the hostname of the connection URL or object to the server name indication field.