Bump nats from 1.4.12 to 2.4.0

[dependabot]

Bumps nats from 1.4.12 to 2.4.0.

Release notes

Sourced from nats's releases.

v2.4.0

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

What's Changed

• [UPDATE] nbc to v1.3.1 see 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.1 for more information.
• [FIX] explicit check on the result from extractProtocolMessage nats-io/nats.js#456
• [FEAT] [NBC] dns-resolve nats-io/nats.js#458
• [FIX] broken link in README by @​rjoly-qlik in nats-io/nats.js#463

New Contributors

• @​rjoly-qlik made their first contribution in nats-io/nats.js#463

Full Changelog: nats-io/nats.js@v2.2.0...v2.3.0

v2.2.0

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#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 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_group for the consumer, any jetstream#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,

... (truncated)

Commits

• de8e276 [UPDATE] nbc to 1.4.0 (#466)
• fda2785 [chore] changed to reference nbc main (#464)
• e316f1c package lock v2.3.0
• 314857f 230 (#462)
• af72a96 Update README.md (#463)
• c7c0bd2 [FEAT] [NBC] dns-resolve (#458)
• 17ff061 - Added explicit test to see if the peek yielded a protocol message and not a...
• 3127180 doc readme fix (#451)
• 950bf8b release 2.2.0 (#443)
• 84acc69 Merge pull request #442 from nats-io/fix-441
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #80.