Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 16, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-nats-streaming (source) 0.0.51 -> 0.3.2 age adoption passing confidence

Release Notes

nats-io/stan.js

v0.3.2

Compare Source

v0.3.0

Compare Source

  • Implemented getRedeliveryCount() on a message which returns the number of times the message has been redelivered. This requires nats-streaming-server v0.17.0 - See #​155
  • Fixed an issue related to the client lifecycle when the client is created with an existing nats connection, the connect handler was not triggered, thus the client would appear to hang.
  • Exposed recent connection properties in the typescript bindings. See #​145.
  • Adopted standardjs for project formatting
  • Updated dependencies

v0.2.6

Compare Source

[FIX] Changed protobuf generation to commonjs_strict removing the global variable global 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
  • internal request/reply timeouts of the stan protocol now have their timeouts specified by the connectTimeout property as done in the go-nats-streaming client.
ES6 Changes
  • changed var to const/let. Use of arrow functions everywhere it could simplify code.
Tests
  • move to nyc from istanbul exposed a number of tests hanging because timers were not properly closed under some conditions (this required changes in node-nats), as well as insuring that all tests call close() on the connection.
Updated Samples/Bench tools
  • the samples and tools hadn't been updated or reviewed since initially written. They received some love.
Dependency updates
  • updated all dev depedencies
  • replaced istanbul with nyc

v0.2.0

Compare Source

  • [CHANGE] The properties maxPingOut and pingInterval were renamed to stanMaxPingOut and stanPingInterval 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 the connection_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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Feb 16, 2019

Codecov Report

Merging #50 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ccca468...6b4e519. Read the comment docs.

@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.0.52 fix(deps): update dependency node-nats-streaming to v0.1.0 Mar 20, 2019
@renovate renovate bot force-pushed the renovate/node-nats-streaming-0.x branch 2 times, most recently from db7bae4 to 022e591 Compare March 21, 2019 19:39
@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.1.0 fix(deps): update dependency node-nats-streaming to v0.2.0 Mar 21, 2019
@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.2.0 fix(deps): update dependency node-nats-streaming to v0.2.2 Mar 29, 2019
@renovate renovate bot force-pushed the renovate/node-nats-streaming-0.x branch from 022e591 to c5c9863 Compare March 29, 2019 15:39
@renovate renovate bot force-pushed the renovate/node-nats-streaming-0.x branch from c5c9863 to a68fdf7 Compare July 13, 2019 05:58
@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.2.2 fix(deps): update dependency node-nats-streaming to v0.2.4 Jul 13, 2019
@renovate renovate bot force-pushed the renovate/node-nats-streaming-0.x branch from a68fdf7 to b51cfab Compare August 10, 2019 07:59
@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.2.4 fix(deps): update dependency node-nats-streaming to v0.2.6 Aug 10, 2019
@renovate renovate bot force-pushed the renovate/node-nats-streaming-0.x branch from b51cfab to 6b4e519 Compare June 30, 2020 21:57
@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.2.6 fix(deps): update dependency node-nats-streaming to v0.3.2 Jun 30, 2020
@renovate renovate bot changed the title fix(deps): update dependency node-nats-streaming to v0.3.2 Update dependency node-nats-streaming to v0.3.2 Dec 17, 2022
@renovate renovate bot changed the title Update dependency node-nats-streaming to v0.3.2 fix(deps): update dependency node-nats-streaming to v0.3.2 Dec 17, 2022
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant