chore(deps,flink): update confluent-kafka requirement from <3,>=2.15.0 to >=2.15.1,<3 in /src/agentflow_runtime/processing/flink_jobs

[dependabot]

Updates the requirements on confluent-kafka to permit the latest version.

Release notes

Sourced from confluent-kafka's releases.

v2.15.1

Fixes

• DeserializingConsumer and DeserializingShareConsumer now deserialize the message key before the value, matching SerializingProducer and the Java client. When both key and value fail to deserialize, the key error is now surfaced instead of the value error.
• Minor fix for subjectPrefix parameter in subjects API (#2311)
• Fix race conditions (#2315)
• Fix segmentation fault after calling AdminClient.delete_records() followed by another Admin API call (e.g. list_topics()) on Python 3.14.
• Use asyncio.get_running_loop() instead of asyncio.get_event_loop() to avoid creating a new event loop and raise an error in case a loop isn't available (@​AlexCai26, #2339).

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

Changelog

Sourced from confluent-kafka's changelog.

v2.15.1

Fixes

• DeserializingConsumer and DeserializingShareConsumer now deserialize the message key before the value, matching SerializingProducer and the Java client. When both key and value fail to deserialize, the key error is now surfaced instead of the value error.
• Minor fix for subjectPrefix parameter in subjects API (#2311)
• Fix race conditions (#2315)
• Fix segmentation fault after calling AdminClient.delete_records() followed by another Admin API call (e.g. list_topics()) on Python 3.14.
• Use asyncio.get_running_loop() instead of asyncio.get_event_loop() to avoid creating a new event loop and raise an error in case a loop isn't available (@​AlexCai26, #2339).

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

v2.15.0

KIP-932 Queues for Kafka – Now in Preview

confluent-kafka-python 2.15.0 adds a Preview implementation of the KIP-932 share consumer (Queues for Kafka). Members of a share group cooperatively consume from the same partitions with per-record acquire/acknowledge semantics and redelivery, providing queue-like consumption on top of Kafka.

• New ShareConsumer and DeserializingShareConsumer clients: subscribe, batch poll (poll() returns a Messages batch), and close (with context-manager support).
• Implicit (default) and explicit acknowledgement modes (share.acknowledgement.mode), with AcknowledgeType ACCEPT / RELEASE / REJECT and Message.delivery_count().
• Synchronous and asynchronous commit (commit_sync / commit_async) and an acknowledgement-commit callback.
• Runtime SASL credential updates (set_sasl_credentials) and new IllegalStateException / ConcurrentModificationException exceptions.
• (#2217, #2239, #2241, #2252, #2253, #2265, #2273, #2277, #2279)

See the Share Consumer guide and the Share consumers section of librdkafka's INTRODUCTION.md.

Note: The share consumer is currently in Preview and should not be used in production environments. Its public interfaces may change before General Availability, and known limitations apply (see the guide). The share consumer is single-threaded and not thread-safe. It requires a broker with share groups enabled (generally available in Apache Kafka 4.2.0).

Features

• New optional install confluent-kafka[oauthbearer-aws] provides AWS IAM-based OAUTHBEARER authentication via AWS STS GetWebIdentityToken. Activate by setting sasl.oauthbearer.method=oidc, sasl.oauthbearer.metadata.authentication.type=aws_iam, and sasl.oauthbearer.config="region=...,audience=...". See the AWS IAM OAUTHBEARER guide for full configuration, and https://github.com/confluentinc/confluent-kafka-python/blob/master/examples/oauth_oidc_ccloud_aws_iam.py for a worked example.

Enhancements

• Add support for union-of-pools and auto pool mapping for Schema Registry (#2182)

... (truncated)

Commits

• 1a6f60f 2.15.1 (#2355)
• e4d47f7 2.15.1rc2: make validation pass on setup_all_versions.py (#2354)
• a67b660 2.15.1rc1 (#2353)
• 5cd8358 Fix thread-unsafe decimal context in protobuf_to_decimal (#2349)
• 80a730c Invoke isort as a binary, not via python -m, to support isort>=9.0.0 (#2344)
• 14286ea fix(aio): use get_running_loop() instead of get_event_loop() in AIOConsumer (...
• eea3931 DGS-24222 Add support for inline validation rules (#2326)
• 253e0c6 Fix reference counting in delete_records Admin API (#2328)
• 8905a07 Fix consume() breaking out of chunked loop on first result (#2235)
• aa1d54e Use tink[gcpkms] extra to fix missing GCP KMS dependencies (#2327)
• 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 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]

Labels

The following labels could not be found: flink, python. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

DORA Metrics

• Window: last 30 days
• Branch: main
• Deployment frequency: 23 total / 5.37 per week
• Lead time for changes: avg 4.74h / median 0.0h
• Change failure rate: 73.91% (17/23)
• MTTR: 79.52h across 11 incident(s)