fix(deps): update dependency io.nats:jnats to v2.18.1 #478
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:
2.17.6
->2.18.1
Release Notes
nats-io/nats.java (io.nats:jnats)
v2.18.1
Compare Source
Core
JetStream
Doc
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
JetStream
Doc
Misc
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
JetStream
Doc
Misc
Configuration
📅 Schedule: Branch creation - "after 10pm" in timezone Europe/Prague, 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.
This PR has been generated by Mend Renovate. View repository job log here.