v2.5.0

Warning

This version has introduced a regression in which an assert is triggered during PushTelemetry call. This happens when no metric is matched on the client side among those requested by broker subscription.

You won't face any problem if:

• Broker doesn't support KIP-714.
• KIP-714 feature is disabled on the broker side.
• KIP-714 feature is disabled on the client side. This is enabled by default. Set configuration enable.metrics.push to false.
• If KIP-714 is enabled on the broker side and there is no subscription configured there.
• If KIP-714 is enabled on the broker side with subscriptions that match the KIP-714 metrics defined on the client.

Having said this, we strongly recommend using v2.5.3 and above to not face this regression at all.

This is a feature release.

• Adds an AdminAPI DeleteRecords() (#1141, @PratRanj07).
• Add support for metadata and ruleSet in the schema registry client, which together support data
  contracts.
• Add a new Avro package "avrov2" which uses the Avro hamba library. The old package "avro" uses
  Avro libraries which are no longer maintained and should not be used in new code.
• Move rest service for schema registry client into internal package for use by both the SR client
  and the DEK Registry client.
• Add support for CSFLE (client-side field-level encryption) for AWS, Azure, GCP, and HashiCorp
  Vault. See the encryption examples in the examples directory.
• Add support for CEL, CEL_FIELD, and JSONata rules.

Fixes

• Issues: #965
  Windows builds are linked to libssp in addition to other libraries, since
  the bundled zstd and zlib are built with -fstack-protector, and not linking
  causes build failures.
  Happening since 2.0.0 (#1184).

confluent-kafka-go is based on librdkafka v2.5.0, see the librdkafka v2.5.0 release notes for a complete list of changes, enhancements, fixes and upgrade considerations.