fix(deps): update dependency amqp-as-promised to v5 #12
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:
^4.1.0
->^5.0.0
Release Notes
ttab/amqp-as-promised (amqp-as-promised)
v5.6.2
Compare Source
amqplib
andcoffeelint
due to security vulnerabilities.v5.6.1
Compare Source
v5.6.0
Compare Source
hopefully preserves resource usage on the server side.
v5.5.0
Compare Source
v5.4.1
Compare Source
logLevel
configuration option should of course be optional.v5.4.0
Compare Source
amqp
), to support selectivelogging. The log level can be set using the
logLevel
connectionparameter, or by calling
log.getLogger('amqp').setLevet('debug')
v5.3.2
Compare Source
property.
v5.3.1
Compare Source
v5.3.0
Compare Source
v5.2.3
Compare Source
serve()
5.2.2 - 2020-07-07
topic
argument forexchange()
is optional.accepts an exchange or queue object, respectively.
5.2.1 - 2020-05-20
queue.bind()
5.2.0 - 2020-05-19
5.1.0 - 2018-11-30
exception on underlying connection errors. This has not worked
properly recently, making error handling hard. This release fixes
that.
error
events.new Buffer()
in favor ofBuffer.from()
npm audit
problems.5.0.2 - 2018-11-29
5.0.1 - 2018-08-07
shutting down.
5.0.0 - 2018-07-31
connection management. See Running for
details.
4.2.0 - 2018-01-30
setMaxListeners()
on the created channel in order to avoidmisleading memory leak warnings.
4.1.1 - 2016-12-14
4.1.0 - 2016-12-05
waitForConnection
feature to wait for rabbitmq server to becomeavailable. This is not a reconnect feature.
4.0.3 - 2016-12-01
4.0.1 - 2016-11-28
RpcError
as an exported class.4.0.0 - 2016-11-18
RpcBackend.serve()
will now serialize errors in a slightly differentformat, preserving
message
,code
anderrno
if present inthe error object.
Rpc.rpc()
will treat any return message that is a JSON objectcontaining an
error
property as a remote error, resulting in arejected promise. Previously we didn't care to inspect return
messages, so remote errors would still yield fulfilled promises.
3.0.2 - 2016-11-08
rpc()
3.0.1 - 2016-11-02
text/plain
payloads correctly.3.0.0 - 2016-10-19
node-amqp
toamqplib
. Efforts have been made to keep everything as backwardscompatible as possible.
queue.shift()
is no longer supported.Q
has been dropped in favor of native promises. As a result,support for promise progress notifications over RPC is no longer
supported.
0.3.0 - 2015-01-29
0.2.2 - 2014-09-18
0.2.1 - 2014-09-18
Changed
amqpc.queue()
,amqpc.exchange()
andamqpc.bind()
; errors caught during queue and exchange declarationwill now properly reject the promise.
amqpc.bind()
: omitting the queue name didn't work asadvertised in version 0.2.0, but should be fine now.
0.2.0 - 2014-09-08
Changed
exchange.publish()
now returns a promise, asadvertised. Previously it did not, even though the docs said so.
amqpc.queue()
have changed to be more intuitiveand in line with how
amqpc.exchange()
works.amqpc.bind()
, which previously expected an exchange name and aqueue name, now accepts both names or exchange/queue objects.
queue.bind()
, which previously expected an exchange object, notaccepts both a name or an object.
0.1.6
Changed
deliveryMode
for RPC calls.0.1.5
Changed
node-amqp
0.2.0 under the hood.v5.2.2
Compare Source
topic
argument forexchange()
is optional.accepts an exchange or queue object, respectively.
v5.2.1
Compare Source
queue.bind()
v5.2.0
Compare Source
v5.1.0
Compare Source
exception on underlying connection errors. This has not worked
properly recently, making error handling hard. This release fixes
that.
error
events.new Buffer()
in favor ofBuffer.from()
npm audit
problems.v5.0.2
Compare Source
v5.0.1
Compare Source
shutting down.
v5.0.0
Compare Source
connection management. See Running for
details.
v4.2.0
Compare Source
setMaxListeners()
on the created channel in order to avoidmisleading memory leak warnings.
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.