[Snyk] Upgrade nats.ws from 1.2.0 to 1.5.0

[snyk-bot]

Snyk has created this PR to upgrade nats.ws from 1.2.0 to 1.5.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 9 versions ahead of your current version.
• The recommended version was released a month ago, on 2021-11-11.

Release notes

Package name: nats.ws

• 1.5.0 - 2021-11-11
  

  This release updates NBC to 1.4.0, there are a couple of small fixes and enhancements. Please see https://github.com/nats-io/nats.deno/releases/tag/v1.4.0 for a complete list of changes.

  What's Changed

  [UPDATE] nbc to 1.4.0

  Full Changelog: v1.4.1...v1.5.0

• 1.4.2-1 - 2021-11-04
• 1.4.1 - 2021-11-02
  

  What's Changed

  [UPDATE] nbc to v1.3.1 the base library has a few small fixes and adds additional JetStream functionality. See https://github.com/nats-io/nats.deno/releases/tag/v1.3.0 and https://github.com/nats-io/nats.deno/releases/tag/v1.3.0 for more information
  [CHORE] set node NODE_EXTRA_CA_CERTS to point to the cert to prevent rejection in #109
  [FIX] changed check on peek to insure we got data before processing connect from the server #114

  Full Changelog: v1.3.0...v1.4.1

• 1.4.0 - 2021-11-01
  

  What's Changed

  [UPDATE] nbc to v1.3.0 the base library has a few small fixes and adds additional JetStream functionality. See https://github.com/nats-io/nats.deno/releases/tag/v1.3.0 for more information

  Full Changelog: v1.3.0...v1.4.0

• 1.4.0-1 - 2021-11-01
  

  v1.4.0-1

• 1.3.1-3 - 2021-10-19
• 1.3.1-2 - 2021-10-01
• 1.3.1-1 - 2021-10-01
• 1.3.0 - 2021-08-25
  

  BREAKING CHANGES

  This release contains a set of changes that are API-breaking for JetStream. Since the JetStream APIs on the JavaScript clients are Preview, only the minor version of the client has been bumped. Because of these changes, you should carefully read the Breaking Changes section to ensure you are not affected.

  JetStream Push Consumers In Queue Groups

  The Push Consumer Queue feature has changed. A new nats-server (2.4.0) is in the works that modifies how this feature works.
  The new JavaScript clients have been modified to work with the new server and will fail to work with an existing server using push consumers with queue groups.

  Previously it was possible to create a push consumer and properly get it working in a queue group with a regular NatsConnection#subscribe or NatsConnection#jetstream()#subscribe() if all queue subscriptions used the same queue name and no plain (non-queue) subscriptions were used.

  If the mix of subscriptions and queues referenced the same consumer but provided different queue names or no queue names, the delivery of messages was incorrect and could create conditions where some messages were seen in duplicate or have unexpected side effects.

  The new nats-server changes will make an old consumer configuration with a queue group a noop - the server will not send messages to the client. To enable a queue group to work on a consumer:

  • The consumer configuration must specify a deliver_group matching the queue group name.
  • Configurations that use the consumer with a non-matching queue group will be invalid.
  • Configurations that use a queue group consumer without a queue group will be invalid.

  The nats client for JavaScript on 1.2.0 and beyond, enforces the above rules, so an Error is thrown from NatsConnection#jetstream().subscribe() for configurations that try to use the queue group incorrectly.

  Because an old server will not report deliver_group for the consumer, any jetstream#subscribe() that attempts to specify a queue group will fail the validation.

  If you are creating nats your own nats subscription to handle the consumer, and have an old server, you may continue to do that until you upgrade the server, at which point the nets-server will stop delivering messages to your client. Please do ensure that you don't use the consumer from different queue groups in the meanwhile.

  JetStreamManager#streams#getMessage(number)

  This API has been removed (it was deprecated and printing console messages). To retrieve a message by its sequence,
  replace with JetStreamManager#streams#getMessage({seq: number}).

  JetStream SequencePair was renamed SequenceInfo

  This matches changes in the server. These types are referenced from ConsumerInfo.

  Other Changes

  • [FEAT] Added DeliveryPolicy#LastPerSubject which allows a consumer to get the last message for each subject in a stream.

  • [FEAT] PubAck now reports a domain field representing the JetStream domain if set or returning an empty string. This feature requires a newer server.

  • [FIX] ConsumerConfig now have fields deliver_group, description.

• 1.2.0 - 2021-07-02
  

  This release sports a number of updates enhancing the JavaScript JetStream functionality.
  For a complete list of changes, see https://github.com/nats-io/nats.deno/releases/tag/v1.1.0.

from nats.ws GitHub release notes

Commit messages

Package name: nats.ws

• 4d7eeff [UPDATE] nbc to 1.4.0 (#121)
• e9130ac [CHORE] referencing nbc main (#120)
• 8f580e3 nbc handling of request exception rejecting rather than throwing (#119)
• df205e6 1.4.0 (#118)
• 62c113c Preparing for release (#117)
• 9c0d3ba fixed check of protocol message on peek to insure that we didn't get an empty string. (#114)
• 5e496bb set node NODE_EXTRA_CA_CERTS to point to the cert to prevent rejection (#109)
• 02c6c69 preparing for 1.3.0 (#108)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs