chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@kafkats/client@0.8.0

Minor Changes

• fe140c0: ShareConsumer: Kafka 4.2 share groups GA support (ShareFetch/ShareAcknowledge v2)
  • KIP-1206: new acquireMode config ('batch_optimized' default | 'record_limit') — record_limit strictly caps each fetch at maxRecords.
  • KIP-1222: new message.renew() to extend the acquisition lock without finalizing delivery; safe to call multiple times per message.
  • ShareAcknowledgeResponse.acquisitionLockTimeoutMs is now decoded on v2 responses.
  • AckManager dedupes same-offset RENEW + finalizing-ack pairs and collapses duplicate same-offset RENEWs so the wire never carries overlapping batches.
  • @experimental markers removed; share groups are GA in Kafka 4.2.
  • Backward compatible: against Kafka 4.1 brokers the client negotiates v1 and produces byte-identical wire output to before this change. record_limit and renew() throw with a clear "requires v2 (Kafka 4.2+)" error against older brokers.

@kafkats/codec-zod@0.8.0

Minor Changes

• fe140c0: ShareConsumer: Kafka 4.2 share groups GA support (ShareFetch/ShareAcknowledge v2)
  • KIP-1206: new acquireMode config ('batch_optimized' default | 'record_limit') — record_limit strictly caps each fetch at maxRecords.
  • KIP-1222: new message.renew() to extend the acquisition lock without finalizing delivery; safe to call multiple times per message.
  • ShareAcknowledgeResponse.acquisitionLockTimeoutMs is now decoded on v2 responses.
  • AckManager dedupes same-offset RENEW + finalizing-ack pairs and collapses duplicate same-offset RENEWs so the wire never carries overlapping batches.
  • @experimental markers removed; share groups are GA in Kafka 4.2.
  • Backward compatible: against Kafka 4.1 brokers the client negotiates v1 and produces byte-identical wire output to before this change. record_limit and renew() throw with a clear "requires v2 (Kafka 4.2+)" error against older brokers.

Patch Changes

• Updated dependencies [fe140c0]
  • @kafkats/client@0.8.0

@kafkats/flow@0.8.0

Minor Changes

• fe140c0: ShareConsumer: Kafka 4.2 share groups GA support (ShareFetch/ShareAcknowledge v2)
  • KIP-1206: new acquireMode config ('batch_optimized' default | 'record_limit') — record_limit strictly caps each fetch at maxRecords.
  • KIP-1222: new message.renew() to extend the acquisition lock without finalizing delivery; safe to call multiple times per message.
  • ShareAcknowledgeResponse.acquisitionLockTimeoutMs is now decoded on v2 responses.
  • AckManager dedupes same-offset RENEW + finalizing-ack pairs and collapses duplicate same-offset RENEWs so the wire never carries overlapping batches.
  • @experimental markers removed; share groups are GA in Kafka 4.2.
  • Backward compatible: against Kafka 4.1 brokers the client negotiates v1 and produces byte-identical wire output to before this change. record_limit and renew() throw with a clear "requires v2 (Kafka 4.2+)" error against older brokers.

Patch Changes

• Updated dependencies [fe140c0]
  • @kafkats/client@0.8.0

@kafkats/flow-state-lmdb@0.8.0

Minor Changes

• fe140c0: ShareConsumer: Kafka 4.2 share groups GA support (ShareFetch/ShareAcknowledge v2)
  • KIP-1206: new acquireMode config ('batch_optimized' default | 'record_limit') — record_limit strictly caps each fetch at maxRecords.
  • KIP-1222: new message.renew() to extend the acquisition lock without finalizing delivery; safe to call multiple times per message.
  • ShareAcknowledgeResponse.acquisitionLockTimeoutMs is now decoded on v2 responses.
  • AckManager dedupes same-offset RENEW + finalizing-ack pairs and collapses duplicate same-offset RENEWs so the wire never carries overlapping batches.
  • @experimental markers removed; share groups are GA in Kafka 4.2.
  • Backward compatible: against Kafka 4.1 brokers the client negotiates v1 and produces byte-identical wire output to before this change. record_limit and renew() throw with a clear "requires v2 (Kafka 4.2+)" error against older brokers.

Patch Changes

• Updated dependencies [fe140c0]
  • @kafkats/flow@0.8.0