Bump github.com/nats-io/nats-server/v2 from 2.1.9 to 2.2.6 in /distributor

[dependabot]

Bumps github.com/nats-io/nats-server/v2 from 2.1.9 to 2.2.6.

Release notes

Sourced from github.com/nats-io/nats-server/v2's releases.

Release v2.2.6

Changelog

Go Version

• 1.16.4: Both release executables and Docker images are built with this Go release.

Changed

• pinned_certs is now also checked by servers initiating connections, not only when accepting them. Furthermore, connections whose certificate is no longer present in the pinned_cert list after a configuration reload, will be closed (#2247)

Fixed

• JetStream:
  • Possible message corruption with inbound messages that would have an existing header (#2241)
  • In cluster mode and with replicas greater than 1, after a valid "duplicate" error was returned (when using the Nats-Msg-Id header), the server would fail subsequent publish calls of non duplicate messages. It would take several attempts before the message would be accepted without error. Thanks to @​krisdaniels for the report (#2245)
  • Messages would not be removed from the stream with WorkQueuePolicy and replicas greater than 1. Thanks to @​danpoland for the report (#2246)
  • When using domains, cross domain transfers would stop working after updating the account JWT (#2248)
  • The monitoring endpoint /varz was showing total account usage instead of server usage. Thanks to @​cjbottaro for the report (#2249)

Complete Changes

nats-io/nats-server@v2.2.5...v2.2.6

Release v2.2.5

Changelog

Go Version

• 1.16.4: Both release executables and Docker images are built with this Go release.

Added

• pinned_certs configuration in TLS blocks, which contains "fingerprint" of accepted certificates. If a connection presents a certificate with a fingerprint that is not in this list, the connection will be rejected (#2233)

Fixed

• JetStream:
  • Bad redelivered values on consumer state should not cause a panic (#2223)
  • Restoring snapshots would require access to /tmp directory, which is not available in docker images (#2227)
  • Ensure that removal of a peer is replicated (#2231)
  • Reject an invalid API prefix for source or mirror is used (#2237)
• MQTT:
  • Reduce replicas value when creating session streams if some servers in the cluster are not running (#2226)
• Monitoring:
  • Always initialize httpReqStats, which allows users embedding NATS Server to use the NATS server http handlers in their own http server, without producing a panic. Thanks to @​BlizzTom for the contribution (#2224)
• Under double import scenarios, the server could possibly map to the wrong subject (#2225)

Complete Changes

nats-io/nats-server@v2.2.4...v2.2.5

... (truncated)

Commits

• cf433ae Merge pull request #2250 from nats-io/release_2_2_6
• 1c00f77 Release v2.2.6
• b1dee29 [changed] pinned certs to check the server connected to as well (#2247)
• f5c3da3 Merge pull request #2249 from nats-io/varz-js
• 0d6b022 Fix for varz JetStream usage showing total account usage vs server usage.
• 252558c Merge pull request #2248 from nats-io/js-mappings
• 748b7c3 [fixed] deletion of js mappings on account jwt update
• 9d86788 Merge pull request #2246 from nats-io/wq-retention
• 8888ab5 Fix for #2243. We were not allowing replicated acks processing for workqueues...
• 11539ec Merge pull request #2245 from nats-io/msgid
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 #141.