feat(deps): Bump amqplib from 0.10.9 to 2.0.1

[dependabot]

Bumps amqplib from 0.10.9 to 2.0.1.

Release notes

Sourced from amqplib's releases.

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

• BREAKING: Update minimum Node.js requirement to v18
• Introduce Biome formatter for consistent code formatting
• Add automated formatting via pre-commit hooks using Lefthook
• Format entire codebase with standardised formatting rules
• Add npm format script for manual code formatting
• Enable noUnusedFunctionParameters lint rule and fix all violations
• Enable noUnusedVariables lint rule and remove all unused variables from codebase
• Replace all var declarations with let/const for modern JavaScript standards
• Ensure parseInt calls use explicit radix parameter for clarity and reliability
• Fix precision loss in test data generators by using JavaScript safe integer limits

... (truncated)

Commits

• 7706d75 2.0.1
• 658fd13 Prep for release
• 4c15c08 Merge pull request #854 from amqp-node/feat/remove-buffer-more-ints
• 3645d4f Remove buffer-more-ints dependency, use Node.js built-in BigInt Buffer methods
• 7e4b002 2.0.0
• 2dbdaee Prep for release
• 97b9f26 Merge pull request #853 from amqp-node/feat/heartbeat-zero
• de9e660 Make heartbeat:0 disable heartbeats rather than deferring to server
• 5e9a65e 1.2.0
• 851b75d Prep for release
• Additional commits viewable in compare view

[andreiborza]

Tests are failing because amqplib >= 1.0.0 is not supported by our otel instrumentation. Depends on #20786 being merged first.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0c64572. Configure here.}

[cursor]

Stale @types/amqplib mismatches bumped amqplib version

Low Severity

Bumping amqplib to ^2.0.1 while keeping @types/amqplib at ^0.10.5 in devDependencies creates a type version mismatch. Since amqplib 1.2.0+ bundles its own TypeScript type definitions, the separate @types/amqplib package is now stale and redundant. Having both could cause type conflicts or provide incorrect type information if TypeScript code importing from amqplib is added later.

Additional Locations (1)

• dev-packages/node-integration-tests/package.json#L91-L92

 

^{Reviewed by Cursor Bugbot for commit 0c64572. Configure here.}

[andreiborza]

We will not support this version until we vendor in the instrumentation.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.