NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #2394 most downloaded on NuGet
Provides a Protobuf Serializer and Deserializer for use with Confluent.Kafka with Confluent Schema Registry integration
Last release today
07 Oct 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 43 of 45 stable releases
9 versions withdrawn
withdrawn after publishing
127 years old
81 releases · first in 1900
Serializers and deserializers can now be supplied to a producer, dependent producer or consumer as a builder , which the client invokes during its own
Set*SerializerBuilder andSet*DeserializerBuilder on the producer and consumer builders, the SchemaIClusterIdAware, ISerdeDisposable, SerdeExtensionsClusterId client extension are experimental: they are subject toTimestamp.Type being read as NotAvailable on big-endian platformsrd_kafka_timestamp_type_t out-parameter (a 32-bit enum)IntPtr, so the value landed in the high word and0 on big-endianOne column per quarter.
2.16.0-rc1
2.16.0-rc1 (#2668)
References librdkafka.redist 2.15.1. Refer to the librdkafka v2.15.1 release notes for more information.
Revert " DGS-24721 Add support for saving Azure key version with DEK ( #2641 )"
This reverts commit de9b874.
This reverts commit a81057f.
This reverts commit 01095e2.
This reverts commit 1ed651d.
This reverts commit e31a347.
v2.15.1-RC1
Use librdkafka 2.15.1 final version
Ensure you're not calling StoreOffset with an EOF message. As when calling Commit with an EOF message, it will throw an InvalidOperationException . Pr
Ensure you're not calling StoreOffset with an EOF message.
As when calling Commit with an EOF message, it will throw an InvalidOperationException.
Previously this could cause skipping an offset (<2.1.0) or message reprocessing (>=2.1.0).
Confluent.Kafka.OAuthBearer.Aws provides AWS IAM-basedGetWebIdentityToken. Activate bySaslOauthbearerMethod = SaslOauthbearerMethod.Oidc,SaslOauthbearerMetadataAuthenticationType.AwsIam, and supplyingregion and audience in SaslOauthbearerConfig. See the package's READMEnet8.0 and net10.0 alongside netstandard2.0 and net462. Builds on the approach proposed in #2545 by Fernando Luiz de Lima (@ffernandolima), adapted for the centralized Directory.Build.props structure on current master.v2.15.0-RC2
v2.15.0-RC2 (#2637)
References librdkafka.redist 2.14.2. Refer to the librdkafka v2.14.2 release notes for more information.
Address review: keep README at last final, note skipped 2.14.1
v2.14.2-RC1
Address review: keep README at last final, note skipped 2.14.1
References librdkafka.redist 2.14.0. Refer to the librdkafka v2.14.0 release notes for more information.
v2.14.0-RC1
v2.14.0-RC1 (#2600)
Preserve inner exceptions in RestService
Release version v2.13.2-RC1 comments fixed
Release version v2.13.2-RC1
comments fixed
Unify build configurations and remove redundant properties
References librdkafka.redist 2.13.0. Refer to the librdkafka v2.13.0 release notes for more information.
Nothing published for this version
There are few contract change associated with the new protocol and might cause breaking changes. GroupProtocol configuration property dictates whether…
Starting with Confluent.Kafka 2.12.0, the next generation consumer group rebalance protocol defined in KIP-848 is production-ready. Please refer to the following migration guide for moving from Classic to Consumer protocol.
Note: The new consumer group protocol defined in KIP-848 is not enabled by default. There are few contract change associated with the new protocol and might cause breaking changes. GroupProtocol configuration property dictates whether to use the new Consumer protocol or older Classic protocol. It defaults to Classic if not provided.
Nothing published for this version
References librdkafka.redist 2.11.1. Refer to the librdkafka v2.11.1 release notes for more information.
Nothing published for this version
References librdkafka.redist 2.11.0. Refer to the librdkafka v2.11.0 release notes for more information.
c56a3e6
This commit was created on GitHub.com and signed with GitHub’s verified signature .
GPG key ID: B5690EEEBB952194
Verified Learn about vigilant mode .
librdkafka v2.11.0 is a feature release:
KIP-1102 Enable clients to rebootstrap based on timeout or error code ( #4981 ).
KIP-1139 Add support for OAuth jwt-bearer grant type ( #4978 ).
Fix for poll ratio calculation in case the queues are forwarded ( #5017 ).
Fix data race when buffer queues are being reset instead of being initialized ( #4718 ).
Features BROKER_BALANCED_CONSUMER and SASL_GSSAPI don't depend on JoinGroup v0 anymore, missing in AK 4.0 and CP 8.0 ( #5131 ).
Improve HTTPS CA certificates configuration by probing several paths when OpenSSL is statically linked and providing a way to customize their location or value ( #5133 ).
Nothing published for this version
Raise an error if Protobuf deprecated format is specified
References librdkafka.redist 2.10.0. Refer to the librdkafka v2.10.0 release notes for more information.
Nothing published for this version
Add utilities to convert decimals from/to Protobuf
References librdkafka.redist 2.8.0. Refer to the librdkafka v2.8.0 release notes for more information.
Nothing published for this version
References librdkafka.redist 2.6.1. Refer to the librdkafka v2.6.1 release notes for more information.
$id (#2339).Nothing published for this version
References librdkafka.redist 2.6.0. Refer to the librdkafka v2.6.0 release notes for more information.
Release asset checksums:
v2.11.0.zip SHA256 9e76a408f0ed346f21be5e2df58b672d07ff9c561a5027f16780d1b26ef24683
v2.11.0.tar.gz SHA256 592a823dc7c09ad4ded1bc8f700da6d4e0c88ffaf267815c6f25e7450b9395ca
References librdkafka.redist 2.5.3. Refer to the librdkafka v2.5.3 release notes for more information.
Nothing published for this version
> [!WARNING] Versions 2.5.0, 2.5.1 and 2.5.2 have a regression in which an assert is triggered during PushTelemetry call. This happens when no metric
[!WARNING] Versions 2.5.0, 2.5.1 and 2.5.2 have 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.pushtofalse.- 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.3and above to not face this regression at all.
Upgrade Azure Identity library to 1.11.4 to address a vulnerability in previous versions.
References librdkafka.redist 2.5.0. Refer to the librdkafka v2.5.0 release notes for more information.
Nothing published for this version
Nothing published for this version
Nothing published for this version
References librdkafka.redist 2.4.0. Refer to the librdkafka v2.4.0 release notes for more information.
Nothing published for this version
References librdkafka.redist 2.3.0. Refer to the librdkafka v2.3.0 release notes for more information.
Rack to the Node type, so AdminAPI calls can expose racks for brokers (currently, all Describe
Responses) (#2021, @jainruchir).JsonSerializer and JsonDeserializer (#2042).DescribeCluster() and DescribeTopics() (#2021, @jainruchir).Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix IConsumer breaking change. (ttd2089, #2071)
Nothing published for this version
References librdkafka.redist 2.1.1. Refer to the librdkafka v2.1.1 release notes for more information.
Nothing published for this version
References librdkafka.redist 2.1.0. Refer to the librdkafka v2.1.0 release notes for more information.
_SCHEMA filed is accessed internally from reflecting the static field to accessing it from the instance (AlexeyRaga).OverflowException thrown intermittently when using the ListGroup method (#2003).Nothing published for this version
OpenSSL 3.0.x upgrade in librdkafka requires a major version bump, as some legacy ciphers need to be explicitly configured to continue working, but it
OpenSSL 3.0.x upgrade in librdkafka requires a major version bump, as some legacy ciphers need to be explicitly configured to continue working, but it is highly recommended NOT to use them. The rest of the API remains backward compatible.
NJsonSchema to v10.6.3LatestCompatibilityStrict configuration property to JsonSerializerConfig to check the compatibility with latest schema
when UseLatestVersion is set to true.DeleteGroups is already present).ListConsumerGroups Admin operation. Supports listing by state.DescribeConsumerGroups Admin operation. Supports multiple groups.ListConsumerGroupOffsets Admin operation. Currently, only supports
1 group with multiple partitions. Supports the requireStable option.AlterConsumerGroupOffsets Admin operation. Currently, only supports
1 group with multiple offsets.DependentAdminClientBuilder.Note: There were no 2.0.0 and 2.0.1 releases.
Nothing published for this version
Added NormalizeSchemas configuration property to the Avro, Json and Protobuf serdes.
NormalizeSchemas configuration property to the Avro, Json and Protobuf serdes.ErrorCode enum.Upgraded Newtonsoft.Json to 13.0.1 to address a security vulnerability in 9.0.1.
Upgraded Google.Protobuf dependency to 3.15.0 (CVE-2021-22570).
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →