fix(deps): update dependency amqplib to v2.2.0 - #201
Merged
Merged
Conversation
argoyle
approved these changes
Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.1.0→2.2.0Release Notes
amqp-node/amqplib (amqplib)
v2.2.0Compare Source
calculateDelayrecovery option for supplying a custom reconnect delay strategy, e.g. full jitter, decorrelated jitter or a fixed schedule. When set,maxDelayis not applied to its return value; when it throws or returns an invalid value, recovery gives up as ifmaxRetrieswere exhausted (fixes #855, thanks @GiHoon1123)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 atmaxDelay / (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-36sreconnect-failed) now reject with the failure instead of waiting foreverinitialMaxRetriesrecovery option to bound retries before the first successful connection separately frommaxRetries, so startup can fail fast while steady-state recovery retries indefinitely (fixes #856)Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.