Bump confluent-kafka from 1.7.0 to 2.6.0 in /docker/confluent-kafka

[dependabot]

Bumps confluent-kafka from 1.7.0 to 2.6.0.

Release notes

Sourced from confluent-kafka's releases.

v2.6.0

confluent-kafka-python v2.6.0

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

• Added Python 3.13 wheels (#1828).
• KIP-848 EA: Admin API for listing consumer groups now has an optional filter to return only groups of given types (#1830).
• KIP-460 Admin Leader Election RPC (#1818)
• Added Transactional id resource type for ACL operations (@​JohnPreston, #1834).

confluent-kafka-python 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

confluent-kafka-python v2.5.3

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

Fixes

• Fix an assert being triggered during push telemetry call when no metrics matched on the client side.
• Minor enhancement to JSONDeserializer to retrieve schema from Schema Registry if not provided

confluent-kafka-python 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.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.

confluent-kafka-python v2.5.0

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

• KIP-107 Added delete_records API. (#1710)
• Added an example to show the usage of the custom logger with AdminClient. (#1758)
• Improve caching on Schema Registry client. (#1744)

... (truncated)

Changelog

Sourced from confluent-kafka's changelog.

v2.6.0

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

• Added Python 3.13 wheels (#1828).
• KIP-848 EA: Admin API for listing consumer groups now has an optional filter to return only groups of given types (#1830).
• KIP-460 Admin Leader Election RPC (#1818)
• Added Transactional id resource type for ACL operations (@​JohnPreston, #1834).

confluent-kafka-python 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

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

Fixes

• Fix an assert being triggered during push telemetry call when no metrics matched on the client side.
• Minor enhancement to JSONDeserializer to retrieve schema from Schema Registry if not provided

confluent-kafka-python 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.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.

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

• KIP-107 Added delete_records API. (#1710)
• Added an example to show the usage of the custom logger with AdminClient. (#1758)
• Improve caching on Schema Registry client. (#1744)
• Removed usage of strcpy to enhance security of the client. (#1745)
• Removed support for centos6 and centos7. (#1776)

... (truncated)

Commits

• f354a7a Changes for v2.6.0 release (#1836)
• 3469bb6 Changelog changes and version bump to v2.6.0rc2 (#1835)
• e3e96ff Added Transactional ID Resource Type for ACL operations (#1834)
• b5c82b9 Added changes for Python 3.13 wheel generation (#1828)
• 645b0d5 [KIP-848 EA] Admin API for listing consumer groups now has (#1830)
• 979343a [KIP-460] ElectLeaders implementation public API changes and documentation im...
• 7085708 Added v2.6.0-RC2 to semaphore builds (#1832)
• 6642180 ElectLeaders api(KIP-460) implemented (#1818)
• a356f2a Fixed style check (#1829)
• c83d3da fix: update schema registry cache after deleting subject (#1825)
• 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 #5189.