Repository navigation
chore(deps): ⬆️ update dependency amqplib to ^2.3.3 - #118
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.3.1→^2.3.3Release Notes
amqp-node/amqplib (amqplib)
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)Configuration
📅 Schedule: (in timezone Europe/Madrid)
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.