-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency node-nats-streaming to v0.3.2 #50
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #50 +/- ##
=======================================
Coverage 79.89% 79.89%
=======================================
Files 22 22
Lines 378 378
=======================================
Hits 302 302
Misses 76 76 Continue to review full report at Codecov.
|
db7bae4
to
022e591
Compare
022e591
to
c5c9863
Compare
c5c9863
to
a68fdf7
Compare
a68fdf7
to
b51cfab
Compare
b51cfab
to
6b4e519
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
0.0.51
->0.3.2
Release Notes
nats-io/stan.js
v0.3.2
Compare Source
v0.3.0
Compare Source
getRedeliveryCount()
on a message which returns the number of times the message has been redelivered. This requires nats-streaming-server v0.17.0 - See #155v0.2.6
Compare Source
[FIX] Changed protobuf generation to
commonjs_strict
removing the global variableglobal
conflict for applications that use other protobuf-based libraries.v0.2.4
Compare Source
[NEW] subscriptions now emit errors/timeout event notifications
[NEW]
tokenhandler
options are now forwarded to the underlying nats connection options.v0.2.2
Compare Source
connectTimeout changes
connectTimeout
property as done in the go-nats-streaming client.ES6 Changes
var
toconst
/let
. Use of arrow functions everywhere it could simplify code.Tests
close()
on the connection.Updated Samples/Bench tools
Dependency updates
v0.2.0
Compare Source
[CHANGE] The properties
maxPingOut
andpingInterval
were renamed tostanMaxPingOut
andstanPingInterval
to prevent nats property shadowing. Any client that used these properties will have to be updated to use the new ones.The index.d.ts was updated: the StanOptions now extend most ClientOpts from node-nats.
AckHandlerCallback
now properly declares the error argument as possibly undefined.v0.1.0
Compare Source
This release introduces client-side pings to help keep track of streaming server connections. The feature introduces 2 new connection options:
pingInterval
which controls the number of milliseconds between client pings to the server (default is 5000 milliseconds)maxPingOut
the number of unanswered ping requests before theconnection_lost
event is emitted on the client notifying that the connection from the server was lost.You can read more about it here: https://github.com/nats-io/node-nats-streaming#connection-status.
Note that this release makes one change to client connection options. By default, NATS connections that are created by the library will set
maxReconnectAttempts
to infinite.v0.0.52
Compare Source
Configuration
📅 Schedule: Branch creation - "before 2am" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.