chore(deps): update dependency nats to v2 #343
Closed
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/nats-2.x
branch
from
829fc7d
to
19406da
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
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:
^1.4.12->^1.4.12 || ^2.0.01.4.12->2.5.0Release Notes
nats-io/nats.js
v2.5.0Compare Source
What's Changed
This release updates the nats-base-client (NBC) to v1.5.0
Changes to NBC library
These changes are shared by all NATS.io supported JavaScript clients.
consumers.update(). TheConsumerUpdateConfigprovides some introspection into fields that can be modified. Modifying a consumer is only supported on servers 2.6.4 or better. @aricart in JSM consumerupdatenats-io/nats.deno#229streams.update()now requires the name of the stream. TheStreamUpdateConfigprovides some introspection into fields that can be modified. The previous API is shimmed, however, the shim will be removed on a future release. by @aricart in typed streamupdatenats-io/nats.deno#230 and [SHIM] added an interim shim to streams.update for the API change nats-io/nats.deno#235keys()now returns an iterator rather than a list of keys. If using the beta API you must change your code as no shim is possible by @aricart in [FIX] kv example in jetstream.md - changes to the keys() returning an iterator instead of a list of keys nats-io/nats.deno#240Other changes specific to NATS.js
requireto useimportfor code examples by @Rauno56 in Use import for code examples in the readme nats-io/nats.js#471New Contributors
Full Changelog: nats-io/nats.js@v2.4.0...v2.5.0
v2.4.0Compare Source
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: nats-io/nats.js@v2.3.0...v2.4.0
v2.3.0Compare Source
What's Changed
extractProtocolMessageadded explicit check on result from extractProtocolMessage nats-io/nats.js#456New Contributors
Full Changelog: nats-io/nats.js@v2.2.0...v2.3.0
v2.2.0Compare Source
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.
BREAKING CHANGES
JetStream Push Consumers In Queue Groups
The Push Consumer Queue feature has changed. A new nats-server (2.4.0) has been released 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#subscribeorNatsConnection#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:
deliver_groupmatching the queue group name.The NATS client for JavaScript on 2.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_groupfor the consumer, anyjetstream#subscribe()that attempts to specify a queue group will fail the validation.If you are creating 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 nats-server will stop delivering messages to your client. Please ensure you don't use the consumer from different queue groups in the meantime.
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
SequencePairwas renamedSequenceInfoThis matches changes in the server. These types are referenced from
ConsumerInfo.Other Changes
[FIX] #441 - when Istio is booting, it is possible for the socket to close, triggering a catch(err) where the error is undefined - this fix simply aliases that as a connection refused error.
[FEAT] Added
DeliveryPolicy#LastPerSubjectwhich allows a consumer to get the last message for each subject in a stream.[FEAT]
PubAcknow reports adomainfield representing the JetStream domain if set or returning an empty string. This feature requires a newer server.[FIX]
ConsumerConfignow have fieldsdeliver_group,description.v2.1.0Compare Source
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.
v2.0.8Compare Source
consumerOpts()to take an optionalConsumerConfigenabling the ability to specify any consumer option #433v2.0.6Compare Source
[update] updated nbc to version 1.0.6, there are small number of JetStream and header issues addressed in the base library
v2.0.4Compare Source
v2.0.2Compare Source
clusterto possible properties inServerInfomax_age- inStreamConfigmarked as NanosheadersinJetStreamPublishOptionsv2.0.1Compare Source
[update] updated to nats-base-client v1.0.1, this release contains an important fix regarding the munging of reply subjects on messages that were received during different socket reads. This would cause clients to timeout when expecting a response.
v2.0.0Compare Source
NATS 2.0.0 Release
Configuration
📅 Schedule: 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 these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.