chore(deps): Update dependency io.nats:jnats to v2.19.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.nats:jnats	2.17.6 -> 2.19.1

---

Release Notes

nats-io/nats.java (io.nats:jnats)

v2.19.1

Compare Source

Core

• [Bug] Maximum Message Size accepted a long, but should accept an int #​1161 @​scottf
• [Bug] Poison pill comparison was failing #​1162 @​scottf
• Augmented force reconnect #​1165 @​scottf

Object Store

• Object Store use over leaf-hub domain #​1160 @​scottf

Misc

• Serialization changed, fixed javadocs #​1159 @​scottf

v2.19.0

Compare Source

Core

Improve socket close behavior #​1155 @​scottf

Tests

Additional NKey Tests #​1154 @​scottf

Misc

Experimental Retrier utility removed to its own project/repo #​1153 @​scottf

v2.18.1

Compare Source

Core

• General Retry Functionality #​1145 @​scottf
• Cluster string in Placement is optional. #​1150 @​scottf
• Remove duplicate reconnect event #​1151 @​scottf

JetStream

• Support 409 Leadership Change #​1144 @​scottf

Doc

• Update docs and comments (MessageQueue, forceReconnect) #​1142 @​scottf

v2.18.0

Compare Source

2.18.0 and 2.17.7 are identical.

2.18.0 attempts to start us on the road to properly Semantic Version (semver). In the last few patch releases, changes that should have been exposed via a minor version bump were numbered as a patch.

Even if just one api is newly added, semver requires that we bump the minor version. The forceReconnect api is an example of one api being added to the Connection interface. It should have resulted in a minor version bump.

Going forward, when a release contains only bug fixes, it's appropriate to simply bump the patch. But if an api is added, even one, then the minor version will be bumped.

Core

• Revert headers from being read-only upon message creation #​1123 @​scottf
• tls_available support #​1127 @​scottf
• Revisit Write Timeout Handling #​1128 @​scottf
• Remove rethrowable runtime exception during connection #​1137 @​ajax-surovskyi-y

JetStream

• Fix #​1125 NatsJetStreamMetaData timestamp timezone #​1126 @​mrmx

Doc

• Update Readme with links to docs and examples. #​1119 @​scottf

Misc

• Refactor Encoding util for easier replacement of Base64 encoding class #​1121 @​scottf

v2.17.7

Compare Source

2.18.0 and 2.17.7 are identical.

2.18.0 attempts to start us on the road to properly Semantic Version (semver). In the last few patch releases, changes that should have been exposed via a minor version bump were numbered as a patch.

Even if just one api is newly added, semver requires that we bump the minor version. The forceReconnect api is an example of one api being added to the Connection interface. It should have resulted in a minor version bump.

Going forward, when a release contains only bug fixes, it's appropriate to simply bump the patch. But if an api is added, even one, then the minor version will be bumped.

Core

• Revert headers from being read-only upon message creation #​1123 @​scottf
• tls_available support #​1127 @​scottf
• Revisit Write Timeout Handling #​1128 @​scottf
• Remove rethrowable runtime exception during connection #​1137 @​ajax-surovskyi-y

JetStream

• Fix #​1125 NatsJetStreamMetaData timestamp timezone #​1126 @​mrmx

Doc

• Update Readme with links to docs and examples. #​1119 @​scottf

Misc

• Refactor Encoding util for easier replacement of Base64 encoding class #​1121 @​scottf

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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.