Skip to content

fix(deps): update module github.com/confluentinc/confluent-kafka-go/v2 to v2.13.3#114

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/github.com-confluentinc-confluent-kafka-go-v2-2.x
Open

fix(deps): update module github.com/confluentinc/confluent-kafka-go/v2 to v2.13.3#114
renovate[bot] wants to merge 2 commits intomainfrom
renovate/github.com-confluentinc-confluent-kafka-go-v2-2.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 19, 2026

This PR contains the following updates:

Package Change Age Confidence
github.com/confluentinc/confluent-kafka-go/v2 v2.11.1v2.13.3 age confidence

Release Notes

confluentinc/confluent-kafka-go (github.com/confluentinc/confluent-kafka-go/v2)

v2.13.3

This is a maintenance release:

Fixes
  • Allow compatibility with librdkafka 2.13.0+ (#​1524)

v2.13.2

This is a maintenance release:

Fixes
  • Allow Azure KMS key version to be optional (#​1503)
  • schemaregistry/rules/encryption: fix dropped errors (#​1512)
  • Update frozen semantics for associations in mock SR client (#​1514)

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

v2.13.0

This is a feature release:

Enhancements
  • Add support for forwarding librdkafka log events to a Go channel in AdminClient (#​1448)
  • Add support for FIPS 140-3 on Schema Registry operations (#​1486)
  • Add Schema Registry Associations support with mock client implementation (#​1485)
  • Add associations example (#​1498)
  • Handle evolution during field transformation (#​1490)
  • Add Accept-Version header to Schema Registry requests (#​1487)
Fixes
  • Fix support for wrapped Avro unions (#​1493)
  • Fix Avro bytes serialization (#​1487)

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

v2.12.0

This is a feature release:

KIP-848 – General Availability

Starting with confluent-kafka-go 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. group.protocol configuration property dictates whether to use the new consumer protocol or older classic protocol. It defaults to classic if not provided.

Enhancements
  • OAuth OIDC method example for Kafka metadata based authentication with
    an Azure IMDS endpoint using an attached managed identity as principal (#​1477).

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/github.com-confluentinc-confluent-kafka-go-v2-2.x branch from a7e362c to 68b0f9e Compare March 19, 2026 15:35
@renovate renovate bot force-pushed the renovate/github.com-confluentinc-confluent-kafka-go-v2-2.x branch from 68b0f9e to 6d87a4c Compare March 19, 2026 16:12
@renovate
Copy link
Contributor Author

renovate bot commented Mar 19, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant