Skip to content

chore(deps): bump amqplib from 0.10.9 to 2.2.1 - #96

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/amqplib-2.2.0
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/amqplib-2.2.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Bumps amqplib from 0.10.9 to 2.2.1.

Release notes

Sourced from amqplib's releases.

v2.2.1

No release notes provided.

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.1

  • Return the server acknowledgement from promise-based channel.cancel, matching the callback API (thanks @​edsonsims).
  • Type cancel replies as Replies.Cancel ({ consumerTag }) in both the promise and callback API declarations, which previously claimed Replies.Empty.
  • Fix callback-based waitForConfirms never calling back when invoked after the confirm channel closed with unconfirmed messages; it now yields a channel closed error, matching the promise API (thanks @​youdie006).
  • waitForConfirms (both APIs) now always fails with channel closed after the channel closes with unconfirmed messages. Previously it reported success if every outstanding message had its own callback, or on any call after the first.
  • The callback API's waitForConfirms callback is now required in the TypeScript declarations, matching the docs. Calling it without one threw at runtime.
  • Replace .npmignore with a files allowlist in package.json so the published package no longer includes tests, tooling config, dotfiles or the defs generator. Install size drops from 577 kB to 358 kB (fixes #859, thanks @​rubiesonthesky)

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)

... (truncated)

Commits
  • 0bf17a0 2.2.1
  • 1d38517 Prepare changelog for v2.2.1
  • f5696a3 Merge pull request #863 from amqp-node/fix/npm-package-files
  • 8fd6bbf Merge remote-tracking branch 'origin/main' into fix/npm-package-files
  • 4762f75 Share waitForConfirms between APIs and fail consistently after close
  • 8861ce4 Merge pull request #865 from youdie006/callback-wait-for-confirms-closed
  • 9f739bf Fix callback waitForConfirms hanging after the channel closes
  • 64f924f Type cancel replies as Replies.Cancel and simplify Channel#cancel
  • d63ac20 Merge pull request #864 from edsonsims/fix/promise-cancel-acknowledgement
  • f139242 fix: return cancellation acknowledgement from promise API
  • 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 dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 1, 2026
Bumps [amqplib](https://github.com/amqp-node/amqplib) from 0.10.9 to 2.2.1.
- [Release notes](https://github.com/amqp-node/amqplib/releases)
- [Changelog](https://github.com/amqp-node/amqplib/blob/main/CHANGELOG.md)
- [Commits](amqp-node/amqplib@v0.10.9...v2.2.1)

---
updated-dependencies:
- dependency-name: amqplib
  dependency-version: 2.2.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump amqplib from 0.10.9 to 2.2.0 chore(deps): bump amqplib from 0.10.9 to 2.2.1 Nov 11, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/amqplib-2.2.0 branch from 9b6ba2b to 9dd5644 Compare November 11, 2026 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants