fix(deps): update dependency amqplib to ^1.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
amqplib (source)	^1.0.3 → ^1.2.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

amqp-node/amqplib (amqplib)

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)

---

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 becomes conflicted, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: boundaries/proxy/pnpm-lock.yaml

Progress: resolved 1, reused 0, downloaded 0, added 0
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@buf%2Fshortlink-org_shortlink-link-link.bufbuild_es: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/shortlink-org/shortlink/boundaries/proxy

@buf/shortlink-org_shortlink-link-link.bufbuild_es is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud