fix(deps): update dependency amqplib to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
amqplib (source)	^0.10.0 → ^2.0.0

---

Release Notes

amqp-node/amqplib (amqplib)

v2.0.1

Compare Source

• 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

Compare Source

• 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

Compare Source

• Add bundled TypeScript type definitions (fixes #​843)

v1.1.1

Compare Source

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

v1.1.0

Compare Source

• 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

Compare Source

• 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

Compare Source

• 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

Compare Source

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

v1.0.4

Compare Source

• 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

Compare Source

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

v1.0.2

Compare Source

• Replace url-parse with WHATWG URL API

v1.0.1

Compare Source

• 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

Compare Source

• 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
• Add block scoping to switch statement cases to prevent variable declaration issues
• Enforce const usage for variables that are never reassigned
• Add node: protocol prefix to Node.js builtin module imports for clarity
• Use modern exponentiation operator (**) instead of Math.pow()
• Replace string concatenation with modern template literals
• Remove redundant 'use strict' directives as modules are automatically in strict mode
• Refactor assignment-in-expression patterns to improve code clarity and readability
• Replace comma operators with individual statements for clearer, more readable code
• Split comma-separated variable declarations into individual statements for consistency
• Replace Object.prototype.hasOwnProperty() with safer Object.hasOwn() method
• Enforce strict equality checks (=== and !==) instead of loose equality (== and !=)
• Replace global isNaN with Number.isNaN for safer type checking
• Ensure no variable redeclarations exist to prevent shadowing issues
• Replace global isFinite with Number.isFinite for safer numeric validation
• Enable useArrowFunction lint rule to prefer arrow functions for cleaner syntax
• Enable noUselessCatch lint rule to prevent useless catch blocks that only rethrow errors
• Enable noArguments rule to enforce modern rest parameters instead of legacy arguments object
• Enable bracketSpacing formatting rule to add spaces inside object literals
• Migrate test suite from Mocha to Node.js built-in test runner

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.