Repository navigation
fix(peer-deps): ⬆️ update dependency amqplib to ^2.4.0 - #111
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
renovate
Bot
force-pushed
the
renovate/amqplib-2.x
branch
2 times, most recently
from
November 5, 2026 19:29
8905569 to
67ed3af
Compare
renovate
Bot
force-pushed
the
renovate/amqplib-2.x
branch
from
November 8, 2026 18:14
67ed3af to
dace84c
Compare
renovate
Bot
force-pushed
the
renovate/amqplib-2.x
branch
2 times, most recently
from
November 11, 2026 18:30
cf1cd32 to
cd11e46
Compare
renovate
Bot
force-pushed
the
renovate/amqplib-2.x
branch
from
November 16, 2026 04:21
cd11e46 to
9d3d136
Compare
renovate
Bot
force-pushed
the
renovate/amqplib-2.x
branch
from
November 16, 2026 14:51
9d3d136 to
c2852c8
Compare
This branch has not been deployed
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.2.0→^2.4.0Release Notes
amqp-node/amqplib (amqplib)
v2.4.0Compare Source
!, and is the value of a header, argument or array element, as{ '!': 'table', value: <the table> }. Previously it was decoded as the bare table, which the encoder reads as an explicit type such as{ '!': 'timestamp', value: 1 }. Publishing headers that had been received with such a table therefore threwUnknown type to encode, or sent a different value without an error when the key held a valid type name. A received table can now also be told apart from a received timestamp or decimal. Upgrade note: a consumer that reads a table containing a!key must now read it fromvalue. Tables without a!key, and a!key at the top level of the headers, are decoded as beforetableas an explicit type.{ '!': 'table', value: { ... } }is encoded as a table whose keys are taken literally, so it can contain a key named!v2.3.3Compare Source
NaN,-Infinityand fractions of 2^50 or more as doubles in headers andargumentstables. Previouslypublishthrew aRangeErrorfor these, including when the table had been received from the broker and was being published again. Numbers that could be encoded before are encoded as beforetimestampof 2^64, or an explicitlongof 2^63, in a headers orargumentstable as the largest value of that type, as versions before 2.0.1 did. The largest timestamp is decoded as 2^64, because 2^64 - 1 cannot be represented as a number, so since 2.0.1 a received table containing it could not be published again. Larger numbers still throw aRangeErrortimestampproperty of 2^64, or any other unsigned 64-bit method field of 2^64, as the largest value in the same way, so a message received with a timestamp of 2^64 - 1 can be published again (also a regression in 2.0.1)v2.3.2Compare Source
Maximum call stack size exceeded, the message was requeued, and each reconnecting consumer failed the same way. There is no depth limit, and everything that encoded or decoded before produces the same result (GHSA-gfjv-mq5g-xjfw, reported by Dickson Wu (@DicksonWu654))__proto__as an ordinary property. Previously it replaced the decoded table's prototype: a table value was inherited from, a null value removed the prototype, and any other value was dropped. With a byte array value followed by a numeric key, decoding threw aTypeErrorand closed the connection in the same way. Upgrade note: headers received with a__proto__key now have it as an own property (GHSA-gfjv-mq5g-xjfw)v2.3.1Compare Source
RangeErrorfrompublishwhen an encoded headers orargumentstable exceeds the 64 KiB encoding buffer. Previously the outcome depended on where the boundary fell: a string or Buffer value crossing the end of the buffer was silently truncated, producing a frame whose table length prefix did not match its contents, which RabbitMQ rejected by closing the connection with a 541INTERNAL_ERRORafterpublishhad returned; at other positions a bareoffset is out of rangeerror escaped frompublishinstead (fixes #867)v2.3.0Compare Source
connection.tunewhoseframeMaxis below the protocol minimum of 4096 (the spec allows 0 or at least frame-min-size). Previously such a value was accepted, and the first publish whose encoded frames total 2048 bytes or more entered a loop insendContentthat never advanced, exhausting memory.sendContentnow also throws ifframeMaxleaves no room for a body frame (GHSA-37f9-7m79-6866, reported by Rizwan Bedekar (@r-bedekar); fix based in part on their patch and tests)maxFrameSizeconnection option, also settable as a URL query parameter, bounding the payload size of frames accepted from the server. The default is 64 MiB, or the negotiatedframeMaxif that is larger, so raisingframeMaxneeds no second option;0disables the limit. Incoming frame sizes were previously unchecked, so a frame header declaring up to 4 GiB made the client buffer, and repeatedly re-copy, that much data before looking at it. An oversized frame is now refused from its header alone and closes the connection withFrame size N exceeds maxFrameSize M. The limit is deliberately separate from the negotiatedframeMax, since some brokers send larger frames without splitting them (see #784). Upgrade note: a broker that delivers an unsplit frame larger than the limit will now have that connection closed; passmaxFrameSize: 0, or a higher value, to restore the previous behaviour (GHSA-37f9-7m79-6866)v2.2.1Compare Source
channel.cancel, matching the callback API (thanks @edsonsims).cancelreplies asReplies.Cancel({ consumerTag }) in both the promise and callback API declarations, which previously claimedReplies.Empty.waitForConfirmsnever calling back when invoked after the confirm channel closed with unconfirmed messages; it now yields achannel closederror, matching the promise API (thanks @youdie006).waitForConfirms(both APIs) now always fails withchannel closedafter 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.waitForConfirmscallback is now required in the TypeScript declarations, matching the docs. Calling it without one threw at runtime..npmignorewith afilesallowlist inpackage.jsonso 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)Configuration
📅 Schedule: (in timezone Europe/Madrid)
🚦 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.