From ff001f3d8be175e938c39c57b533d93c50fd8514 Mon Sep 17 00:00:00 2001
From: zmstone <zmstone@gmail.com>
Date: Wed, 6 Nov 2024 14:22:33 +0100
Subject: [PATCH] Upgrade kafka_protocol from 4.1.9 to 4.1.10

take the greater value of `connect_timeout` from connection config
and `timeout` from request options when trying to discover the connect
partition-leader, group-coordinator or cluster-controller

https://github.com/kafka4beam/brod/discussions/602
---
 CHANGELOG.md | 3 +++
 rebar.config | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 69ece89b..0c732390 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,8 @@
 # Changelog
 
+- 4.3.2
+   - Upgrade kafka_protocol from 4.1.9 to 4.1.10 for partition leader discover/connect timeout fix.
+
 - 4.3.1
   - Fixed `brod_client:stop_consumer` so that it doesn't crash the client process if an unknown consumer is given as argument.
   - Previously, `brod_group_subscriber_v2` could leave `brod_consumer` processes lingering even after its shutdown.  Now, those processes are terminated.
diff --git a/rebar.config b/rebar.config
index 84821067..7cf282c1 100644
--- a/rebar.config
+++ b/rebar.config
@@ -1,4 +1,4 @@
-{deps, [{kafka_protocol, "4.1.9"}]}.
+{deps, [{kafka_protocol, "4.1.10"}]}.
 {project_plugins, [{rebar3_lint, "~> 3.2.5"}]}.
 {edoc_opts, [{preprocess, true}]}.
 {erl_opts, [warnings_as_errors, warn_unused_vars,warn_shadow_vars,warn_obsolete_guard,debug_info]}.