build(deps): bump gnat from 1.13.0 to 1.14.0

[dependabot]

Bumps gnat from 1.13.0 to 1.14.0.

Release notes

Sourced from gnat's releases.

1.14.0

What's Changed

• Add PullConsumer.handle_connected/2 optional callback to get consumer info
• Add PullConsumer.handle_status/2 optional callback to observe status messages
• Added support for batch_size option in PullConsumer options to pull messages and acknowledge them in batches.
• Add Gnat.Jetstream.API.KV.Entry with from_message/2 for parsing a raw NATS message from a KV bucket's underlying stream into a structured entry (operation, key, value, revision, created, delta). Intended to be shared between the built-in KV.Watcher and user-supplied PullConsumer implementations (e.g. caches that need to detect when they are caught up with the stream). Returns :ignore for messages that are not KV records.
• KV.Watcher now uses KV.Entry internally; its public callback API is unchanged. The push consumer it creates now enables server-driven flow control and a 5s idle heartbeat (matching nats.go's ordered-consumer defaults), so slow handlers apply backpressure instead of being dropped as slow consumers.
• Behavior change (bugfix): PullConsumer no longer forwards JetStream informational status messages (e.g. 100 idle heartbeat, 409 leadership change) to c:handle_message/2. These are not stream records and cannot be acked. In single-message mode the consumer now drops them and re-issues a pull request.
• Add an optional c:handle_status/2 callback to Gnat.Jetstream.PullConsumer for users who want to observe status messages (e.g. log on 409).

Full Changelog: nats-io/nats.ex@v1.13.1...v1.14.0

1.13.1

What's Changed

• Use flow_control for Object.get by @​ppkn in nats-io/nats.ex#217

New Contributors

• @​ppkn made their first contribution in nats-io/nats.ex#217

Full Changelog: nats-io/nats.ex@v1.13.0...v1.13.1

Changelog

Sourced from gnat's changelog.

Changelog

1.14

• Add PullConsumer.handle_connected/2 optional callback to get consumer info
• Add PullConsumer.handle_status/2 optional callback to observe status messages
• Added support for batch_size option in PullConsumer options to pull messages and acknowledge them in batches.
• Add Gnat.Jetstream.API.KV.Entry with from_message/2 for parsing a raw NATS message from a KV bucket's underlying stream into a structured entry (operation, key, value, revision, created, delta). Intended to be shared between the built-in KV.Watcher and user-supplied PullConsumer implementations (e.g. caches that need to detect when they are caught up with the stream). Returns :ignore for messages that are not KV records.
• KV.Watcher now uses KV.Entry internally; its public callback API is unchanged. The push consumer it creates now enables server-driven flow control and a 5s idle heartbeat (matching nats.go's ordered-consumer defaults), so slow handlers apply backpressure instead of being dropped as slow consumers.
• Behavior change (bugfix): PullConsumer no longer forwards JetStream informational status messages (e.g. 100 idle heartbeat, 409 leadership change) to c:handle_message/2. These are not stream records and cannot be acked. In single-message mode the consumer now drops them and re-issues a pull request.
• Add an optional c:handle_status/2 callback to Gnat.Jetstream.PullConsumer for users who want to observe status messages (e.g. log on 409).

1.11

• Allow clients to force authentication without server auth_required by @​mmmries in #205
• Support ephemeral consumers and auto-cleanup consumers in the PullConsumer module by @​mmmries in #202
• Implement regularly scheduled PING/PONG health check by @​mmmries in #200
• Add Erlang 28 with Elixir 1.18 to the build matrix by @​davydog187 in #201
• Use Pager module for KV.contents by @​mmmries in #198
• Hint :timeout option in KV's typespec by @​rixmann in #193

1.10

• Clarify authentication setup during test by @​davydog187 in #187
• Test on Elixir 1.18 and NATS 2.10.24 by @​davydog187 in #188
• Gnat.Jetstream.API.KV.info/3 by @​davydog187 in #189
• Remove function_exported? check for Keyword.validate!/2 by @​davydog187 in #186
• Tiny optimization to KV.list_buckets/1 by @​davydog187 in #185
• make KV-watcher emit :key_added events when the message has a header by @​rixmann in #191
• add :compression to stream attributes by @​rixmann in #192
• fix: unknown field domain in Stream.create (#194) by @​c0deaddict
• feat: add jetstream message metadata helper (#197) by @​c0deaddict
• fix: deliver policy (#196) by @​c0deaddict

1.9

... (truncated)

Commits

• b6d2f37 1.14.0 Release Candidate (#219)
• 9638ef2 release 1.13.1
• dd4deaf Use flow_control for Object.get (#217)
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)