Skip to content

Conversation

@hindessm
Copy link
Collaborator

Missed from 76ca69a which added more versions

@hindessm hindessm changed the title fix: metadata_responce valid version range fix: metadata_response valid version range Sep 25, 2025
Missed from 76ca69a which added more versions

Signed-off-by: beanz <[email protected]>
@hindessm hindessm force-pushed the fix-metadata-response-valid-versions branch from 803f034 to ba67340 Compare September 25, 2025 09:09
Copy link
Collaborator

@dnwe dnwe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! We actually have a unittest that should have caught this, but we only run it up to Kafka 2.1.0.0 protocol versions, I'll take a look to see how much we can extend that now, at least for a selection of apikeys

@dnwe dnwe merged commit 1c7f473 into IBM:main Sep 25, 2025
16 checks passed
@dnwe dnwe added the fix label Sep 25, 2025
@hindessm hindessm deleted the fix-metadata-response-valid-versions branch September 25, 2025 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants