[dependabot]

Bumps amqplib from 0.10.9 to 2.2.0.

Release notes

Sourced from amqplib's releases.

v2.2.0

No release notes provided.

v2.1.0

No release notes provided.

v2.0.1

• Remove buffer-more-ints dependency; use Node.js built-in BigInt Buffer methods (readBigInt64BE, readBigUInt64BE, writeBigInt64BE, writeBigUInt64BE) which have been available since Node.js v10.4

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.

Fixes #467. Supersedes #469.

1.2.0

Add bundled TypeScript type definitions (fixes #843)

For full history see CHANGELOG.md.

Changelog

Sourced from amqplib's changelog.

v2.2.0

• Add calculateDelay recovery option for supplying a custom reconnect delay strategy, e.g. full jitter, decorrelated jitter or a fixed schedule. When set, maxDelay is not applied to its return value; when it throws or returns an invalid value, recovery gives up as if maxRetries were exhausted (fixes #855, thanks @​GiHoon1123)
• The built-in reconnect delay no longer exceeds maxDelay. Previously the cap was applied before jitter, so delays could overshoot it by up to the jitter fraction. The exponential base is now capped at maxDelay / (1 + jitter) so the full jitter range fits under the cap; with default settings the steady-state delay is now spread over 20-30s rather than 24-36s
• Channel operations attempted after recovery has given up (reconnect-failed) now reject with the failure instead of waiting forever
• Add initialMaxRetries recovery option to bound retries before the first successful connection separately from maxRetries, so startup can fail fast while steady-state recovery retries indefinitely (fixes #856)

v2.1.0

• Add waitForConnect recovery option. When false, connect returns the recovering connection immediately instead of waiting for the first successful connection, so listeners for connect, connect-failed and reconnect-scheduled can be attached before the initial attempt, and close() can cancel it. Expose waitForConnect() on recovering connections to await the first connection (fixes #858)
• Fix setup being run when close() is called while the initial connection attempt is in flight

v2.0.1

• Remove buffer-more-ints dependency; use Node.js built-in BigInt Buffer methods (readBigInt64BE, readBigUInt64BE, writeBigInt64BE, writeBigUInt64BE) which have been available since Node.js v10.4

v2.0.0

• BREAKING: heartbeat: 0 now disables heartbeats, overriding any value suggested by the server. Previously, 0 was treated as "no preference" and the server's suggested value was used. If you are passing heartbeat: 0 and want to preserve the old behaviour, omit the option or pass null instead (fixes #467)

v1.2.0

• Add bundled TypeScript type definitions (fixes #843)

v1.1.1

• Forward handler-error events from the underlying connection to the recovery wrapper, so listeners attached to RecoveringPromiseModel/RecoveringCallbackModel receive handler errors

v1.1.0

• Add connection recovery via connectWithRecoveryPromise and connectWithRecoveryCallback — automatically reconnects on connection loss with configurable backoff delay, jitter, and retry limits (thanks @​ShiriNmi1520)

v1.0.7

• Fix update-secret-ok event not being forwarded by ChannelModel and CallbackModel (fixes #849)
• Add handler-error event to connections and channels. If a user-supplied event handler (e.g. connection.on('close', ...), channel.on('error', ...), channel.on('delivery', ...) etc.) throws a synchronous error, amqplib will emit a handler-error event on the same emitter with the thrown error and the name of the event whose handler threw — provided a handler-error listener is registered. If no handler-error listener is registered, behaviour is unchanged from previous versions. Note: in previous versions, errors thrown in connection close event handlers were silently swallowed; errors thrown in channel event handlers (other than delivery/return) would kill the channel and possibly the connection (fixes #334).

v1.0.6

• Fix channel.get() not invoking callback with error on channel close; previously only an error event was emitted (fixes #832). Note: if you use the callback API, ensure your channel.get() callbacks handle errors — they will now be invoked in error cases where previously they were not. If you use the promise API, the returned promise now rejects with a proper Error object (with .code, .classId and .methodId properties) rather than a raw close frame.

v1.0.5

• Fix ConfirmChannel callbacks silently dropped on channel close when some publishes had no callback (fixes #191)

v1.0.4

• Updated build to use RabbitMQ 4.2
• Fix memory leak in ConfirmChannel.publish when channel is already closed (fixes #842)
• Close connection immediately when close() is called while the connection is blocked (fixes #744)

v1.0.3

• Fix AssertionError crash when backpressure occurs while draining newStreams in Mux (fixes #841)

v1.0.2

• Replace url-parse with WHATWG URL API

v1.0.1

• Fix TLS connection failure when connecting to an AMQPS broker using an IP address (IPv4 or IPv6) — setting servername to an IP is not permitted by TLS SNI and throws ERR_INVALID_ARG_VALUE in Node.js 25+

v1.0.0

... (truncated)

Commits

• bcd72dd 2.2.0
• ced5456 Merge pull request #862 from amqp-node/feat/initial-max-retries
• 0283bba Remove spurious comment
• be9ddbf Add initialMaxRetries recovery option to bound the initial connection separately
• 3f486e6 Merge pull request #857 from GiHoon1123/feat/custom-reconnect-delay-strategy
• 69085d9 Reject channel operations once recovery has given up instead of hanging
• 5ac72e8 Add changelog entries for calculateDelay and the built-in delay cap
• d960972 Give up recovery cleanly when calculateDelay throws or returns an invalid value
• f413b87 Merge branch 'main' into feat/custom-reconnect-delay-strategy
• a6eec24 Stage releases on npm via OIDC trusted publishing instead of a dry-run
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for amqplib since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)