Update _posts/2024-12-17-release-0_9_0.md

Co-authored-by: Keith Wall <[email protected]>
Signed-off-by: Sam Barker <[email protected]>
Signed-off-by: Sam Barker <[email protected]>

Author: SamBarker

_posts/2024-12-17-release-0_9_0.md

@@ -10,7 +10,7 @@ tags: releases kroxylicious kafka3.9
 
 The Kroxylicious project is very pleased to announce the release of [Kroxylicious 0.9.0](https://github.com/kroxylicious/kroxylicious/releases/tag/v0.9.0). This release introduces support for Apache Kafka 3.9. 
 
-We generally expect Kroxylicious to be both forwards- and backwards-compatible across Kafka versions just like the Apache Kafka client and broker. While we tested with pre-release versions of Apache Kafka 3.9 we discovered after it was released that we had missed a case in the protocol version negotiation. When the `APIVersionsRequest` version was updated we were unable to decode the response. In the 0.9.0 release we adopt the same behaviour as the Kafka broker and respond with API version 0 if we do not support the protocol version requested by the client - we have also expanded our test coverage to get earlier warnings of similar issues in the future. 
+We generally expect Kroxylicious to be both forwards- and backwards-compatible across Kafka versions just like the Apache Kafka client and broker. While we tested with pre-release versions of Apache Kafka 3.9 we discovered after it was released that we had missed a case in the protocol version negotiation. When the version of the `ApiVersions` RPC was updated we were unable to decode the response. In the 0.9.0 release we adopt the same behaviour as the Kafka broker and respond with API version 0 if we do not support the protocol version requested by the client - we have also expanded our test coverage to get earlier warnings of similar issues in the future. 
 
 This release also marks the introduction of our new state machine for handling connections. We have evolved the state machine at the core of the proxy to separate out the state carried at various stages of the connection lifecycle and provide stronger rules around transitions between states. This is still a work in progress due to the wide-ranging implications it has, however we think it gives us a stronger core to base everything else around. This does, for the moment, limit our ability to offer authentication offload support, we do intend to restore this eventually (please do get in touch if this use case is important to you via [Slack](https://kroxylicious.slack.com) or [GitHub](https://github.com/kroxylicious/kroxylicious/issues) or even [bsky](https://bsky.app/profile/kroxylicious.io)).