chore: bump Confluent.Kafka from 2.4.0 to 2.6.1

[dependabot]

Bumps Confluent.Kafka from 2.4.0 to 2.6.1.

Release notes

Sourced from Confluent.Kafka's releases.

v2.6.1 is a maintenance release with the following features, fixes and enhancements:

Enhancements

• References librdkafka.redist 2.6.1. Refer to the librdkafka v2.6.1 release notes for more information.

Fixes

• Fix to continue supporting .NET Framework 4.6.2+ in core client library (#2342).
• Fix JSON Schema handling to not require use of $id (#2339).
• Update Caching.Memory to 8.0.1 to address CVE (#23440.
• Added Qualified and Custom reference name strategy approaches for protobuf references (#2345).
• Fix validate of SSL CA certs in Schema Registry client (#2346).
• Skip SSL certs validation when configured in Schema Registry client (#2347).
• Allow proxy to be specified in Schema Registry client (#2348).

v2.6.0 is a feature release with the following features, fixes and enhancements:

Enhancements

• KIP-848 EA: Admin API for listing consumer groups now has an optional filter to return only groups of given types (#2323).
• KIP-460 Admin Leader Election RPC (#2320)
• .NET 8 support with NJsonSchema 11 (#2314)

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

v2.5.3 is a maintenance release with the following fixes and enhancements:

Fixes

• Properly handle messages with well-known types in Protobuf serializer
• Use AES128_GCM in the Local KMS client, for consistency with Java/go
• Include deleted schemas when getting schemas by subject and version
• Handle signed ints when transforming Protobuf payloads
• Allow null SchemaRegistryClient in AsyncSerde constructor

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

v2.5.2

[!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.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.

... (truncated)

Changelog

Sourced from Confluent.Kafka's changelog.

2.6.1

Enhancements

• References librdkafka.redist 2.6.1. Refer to the librdkafka v2.6.1 release notes for more information.

Fixes

• Fix to continue supporting .NET Framework 4.6.2+ in core client library (#2342).
• Fix JSON Schema handling to not require use of $id (#2339).
• Update Caching.Memory to 8.0.1 to address CVE (#23440.
• Added Qualified and Custom reference name strategy approaches for protobuf references (#2345).
• Fix validate of SSL CA certs in Schema Registry client (#2346).
• Skip SSL certs validation when configured in Schema Registry client (#2347).
• Allow proxy to be specified in Schema Registry client (#2348).

2.6.0

Enhancements

• References librdkafka.redist 2.6.0. Refer to the librdkafka v2.6.0 release notes for more information.
• KIP-848 EA: Admin API for listing consumer groups now has an optional filter to return only groups of given types (#2323).
• KIP-460 Admin Leader Election RPC (#2320)
• .NET 8 support with NJsonSchema 11 (#2314)

2.5.3

Enhancements

• References librdkafka.redist 2.5.3. Refer to the librdkafka v2.5.3 release notes for more information.

Fixes

• Properly handle messages with well-known types in Protobuf serializer
• Use AES128_GCM in the Local KMS client, for consistency with Java/go
• Include deleted schemas when getting schemas by subject and version
• Handle signed ints when transforming Protobuf payloads
• Allow null SchemaRegistryClient in AsyncSerde constructor

2.5.2

[!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.push to false.

... (truncated)

Commits

• 843d68f 2.6.1 (#2352)
• fbe9288 2.6.1-RC2 (#2351)
• 1c0c935 Continue supporting .NET Framework. (#2342)
• ea8856b Allow proxy to be specified (#2127) (#2128)
• bfd88b3 (fix #1897) : skip server SSL certs verification when configured (#2347)
• 7e670af updated Apache.Avro from v1.11.3 to v1.12.0 (#2330)
• 4f12737 Fixing the validation of the SSL CA Certificate (#2346)
• 74da56d Feature: Added Qualified and Custom reference name strategy approaches for pr...
• c8aa462 Upgrade Caching.Memory to 8.0.1 (#2344)
• 9ced66c Pass tags as list for consistency with Java implementation (#2343)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Superseded by #242.