+ |
+diff --git a/docs/getting-started/docker.md b/docs/getting-started/docker.md
+index 9fd766223b..d8b48be697 100644
+--- a/docs/getting-started/docker.md
++++ b/docs/getting-started/docker.md
+@@ -33,7 +33,7 @@ type: docs
+ Docker image can be pulled from Docker Hub using the following command:
+
+
+- $ docker pull apache/kafka:4.2.0
++ $ docker pull apache/kafka:4.2.0-stackable0.0.0-dev
+
+ If you want to fetch the latest version of the Docker image use following command:
+
+@@ -43,7 +43,7 @@ If you want to fetch the latest version of the Docker image use following comman
+ To start the Kafka container using this Docker image with default configs and on default port 9092:
+
+
+- $ docker run -p 9092:9092 apache/kafka:4.2.0
++ $ docker run -p 9092:9092 apache/kafka:4.2.0-stackable0.0.0-dev
+
+ ## GraalVM Based Native Apache Kafka Docker Image
+
+@@ -53,7 +53,7 @@ NOTE: This image is experimental and intended for local development and testing
+ Docker image can be pulled from Docker Hub using the following command:
+
+
+- $ docker pull apache/kafka-native:4.2.0
++ $ docker pull apache/kafka-native:4.2.0-stackable0.0.0-dev
+
+ If you want to fetch the latest version of the Docker image use following command:
+
+@@ -63,7 +63,7 @@ If you want to fetch the latest version of the Docker image use following comman
+ To start the Kafka container using this Docker image with default configs and on default port 9092:
+
+
+- $ docker run -p 9092:9092 apache/kafka-native:4.2.0
++ $ docker run -p 9092:9092 apache/kafka-native:4.2.0-stackable0.0.0-dev
+
+ ## Usage guide
+
+diff --git a/docs/getting-started/quickstart.md b/docs/getting-started/quickstart.md
+index 25061e31d1..10af2204ce 100644
+--- a/docs/getting-started/quickstart.md
++++ b/docs/getting-started/quickstart.md
+@@ -28,11 +28,11 @@ type: docs
+
+ ## Step 1: Get Kafka
+
+-[Download](https://www.apache.org/dyn/closer.cgi?path=/kafka/4.2.0/kafka_2.13-4.2.0.tgz) the latest Kafka release and extract it:
++[Download](https://www.apache.org/dyn/closer.cgi?path=/kafka/4.2.0-stackable0.0.0-dev/kafka_2.13-4.2.0-stackable0.0.0-dev.tgz) the latest Kafka release and extract it:
+
+
+- $ tar -xzf kafka_2.13-4.2.0.tgz
+- $ cd kafka_2.13-4.2.0
++ $ tar -xzf kafka_2.13-4.2.0-stackable0.0.0-dev.tgz
++ $ cd kafka_2.13-4.2.0-stackable0.0.0-dev
+
+ ## Step 2: Start the Kafka environment
+
+@@ -64,24 +64,24 @@ Once the Kafka server has successfully launched, you will have a basic Kafka env
+ Get the Docker image:
+
+
+- $ docker pull apache/kafka:4.2.0
++ $ docker pull apache/kafka:4.2.0-stackable0.0.0-dev
+
+ Start the Kafka Docker container:
+
+
+- $ docker run -p 9092:9092 apache/kafka:4.2.0
++ $ docker run -p 9092:9092 apache/kafka:4.2.0-stackable0.0.0-dev
+
+ ### Using GraalVM Based Native Apache Kafka Docker Image
+
+ Get the Docker image:
+
+
+- $ docker pull apache/kafka-native:4.2.0
++ $ docker pull apache/kafka-native:4.2.0-stackable0.0.0-dev
+
+ Start the Kafka Docker container:
+
+
+- $ docker run -p 9092:9092 apache/kafka-native:4.2.0
++ $ docker run -p 9092:9092 apache/kafka-native:4.2.0-stackable0.0.0-dev
+
+ ## Step 3: Create a topic to store your events
+
+@@ -135,12 +135,12 @@ You probably have lots of data in existing systems like relational databases or
+
+ In this quickstart we'll see how to run Kafka Connect with simple connectors that import data from a file to a Kafka topic and export data from a Kafka topic to a file.
+
+-First, make sure to add `connect-file-4.2.0.jar` to the `plugin.path` property in the Connect worker's configuration. For the purpose of this quickstart we'll use a relative path and consider the connectors' package as an uber jar, which works when the quickstart commands are run from the installation directory. However, it's worth noting that for production deployments using absolute paths is always preferable. See [plugin.path](../../configuration/kafka-connect-configs/#connectconfigs_plugin.path) for a detailed description of how to set this config.
++First, make sure to add `connect-file-4.2.0-stackable0.0.0-dev.jar` to the `plugin.path` property in the Connect worker's configuration. For the purpose of this quickstart we'll use a relative path and consider the connectors' package as an uber jar, which works when the quickstart commands are run from the installation directory. However, it's worth noting that for production deployments using absolute paths is always preferable. See [plugin.path](../../configuration/kafka-connect-configs/#connectconfigs_plugin.path) for a detailed description of how to set this config.
+
+ Edit the `config/connect-standalone.properties` file, add or change the `plugin.path` configuration property match the following, and save the file:
+
+
+- $ echo "plugin.path=libs/connect-file-4.2.0.jar" >> config/connect-standalone.properties
++ $ echo "plugin.path=libs/connect-file-4.2.0-stackable0.0.0-dev.jar" >> config/connect-standalone.properties
+
+ Then, start by creating some seed data to test with:
+
+diff --git a/docs/getting-started/upgrade.md b/docs/getting-started/upgrade.md
+index 5538114c41..db25264930 100644
+--- a/docs/getting-started/upgrade.md
++++ b/docs/getting-started/upgrade.md
+@@ -26,11 +26,11 @@ type: docs
+ -->
+
+
+-## Upgrading to 4.2.0
++## Upgrading to 4.2.0-stackable0.0.0-dev
+
+-### Upgrading Servers to 4.2.0 from any version 3.3.x through 4.1.x
++### Upgrading Servers to 4.2.0-stackable0.0.0-dev from any version 3.3.x through 4.1.x
+
+-### Notable changes in 4.2.0
++### Notable changes in 4.2.0-stackable0.0.0-dev
+
+ * The `--max-partition-memory-bytes` option in `kafka-console-producer` is deprecated and will be removed in Kafka 5.0. Please use `--batch-size` instead.
+ * Queues for Kafka ([KIP-932](https://cwiki.apache.org/confluence/x/4hA0Dw)) is production-ready in Apache Kafka 4.2. This feature introduces a new kind of group called share groups, as an alternative to consumer groups. Consumers in a share group cooperatively consume records from topics, without assigning each partition to just one consumer. Share groups also introduce per-record acknowledgement and counting of delivery attempts. Use share groups in cases where records are processed one at a time, rather than as part of an ordered stream.
+diff --git a/docs/kafka-connect/user-guide.md b/docs/kafka-connect/user-guide.md
+index 9a8f0e3afe..2c0556ef04 100644
+--- a/docs/kafka-connect/user-guide.md
++++ b/docs/kafka-connect/user-guide.md
+@@ -42,7 +42,7 @@ The first parameter is the configuration for the worker. This includes settings
+ * `bootstrap.servers` \- List of Kafka servers used to bootstrap connections to Kafka
+ * `key.converter` \- Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.
+ * `value.converter` \- Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the values in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.
+- * `plugin.path` (default `null`) - a list of paths that contain Connect plugins (connectors, converters, transformations). Before running quick starts, users must add the absolute path that contains the example FileStreamSourceConnector and FileStreamSinkConnector packaged in `connect-file-4.2.0.jar`, because these connectors are not included by default to the `CLASSPATH` or the `plugin.path` of the Connect worker (see plugin.path property for examples).
++ * `plugin.path` (default `null`) - a list of paths that contain Connect plugins (connectors, converters, transformations). Before running quick starts, users must add the absolute path that contains the example FileStreamSourceConnector and FileStreamSinkConnector packaged in `connect-file-4.2.0-stackable0.0.0-dev.jar`, because these connectors are not included by default to the `CLASSPATH` or the `plugin.path` of the Connect worker (see plugin.path property for examples).
+
+
+
+@@ -712,4 +712,4 @@ You should then verify that your manifests are correct by using the verification
+
+ ## Security
+
+-It's important to understand the security concerns inherent to Connect. First, Connect allows running custom plugins. These plugins can run arbitrary code, so you must trust them before installing them in your Connect clusters. By default, the REST API is unsecured and allows anyone that can access it to start and stop connectors. You should only directly expose the REST API to trusted users, otherwise it's easy to gain arbitrary code execution on Connect workers. By default, connectors can also override the configurations of the Kafka clients that Connect uses internally. Since Kafka 4.2.0, it's recommended to set `connector.client.config.override.policy` to `Allowlist`, this will be the default from Kafka 5.0.0, and explicitly only allow configurations that you need to override. Keep in mind that configurations that can load classes such as `sasl.jaas.config` or `sasl.login.class` should only be allowed if only trusted users can access the REST API as they, by design, enable executing code on the Connect worker.
++It's important to understand the security concerns inherent to Connect. First, Connect allows running custom plugins. These plugins can run arbitrary code, so you must trust them before installing them in your Connect clusters. By default, the REST API is unsecured and allows anyone that can access it to start and stop connectors. You should only directly expose the REST API to trusted users, otherwise it's easy to gain arbitrary code execution on Connect workers. By default, connectors can also override the configurations of the Kafka clients that Connect uses internally. Since Kafka 4.2.0-stackable0.0.0-dev, it's recommended to set `connector.client.config.override.policy` to `Allowlist`, this will be the default from Kafka 5.0.0, and explicitly only allow configurations that you need to override. Keep in mind that configurations that can load classes such as `sasl.jaas.config` or `sasl.login.class` should only be allowed if only trusted users can access the REST API as they, by design, enable executing code on the Connect worker.
+diff --git a/docs/operations/tiered-storage.md b/docs/operations/tiered-storage.md
+index 38dac7361b..f4117ca838 100644
+--- a/docs/operations/tiered-storage.md
++++ b/docs/operations/tiered-storage.md
+@@ -63,7 +63,7 @@ To adopt the `LocalTieredStorage`, the test library needs to be built locally
+
+
+ # please checkout to the specific version tag you're using before building it
+- # ex: `git checkout 4.2.0`
++ # ex: `git checkout 4.2.0-stackable0.0.0-dev`
+ $ ./gradlew clean :storage:testJar
+
+ After build successfully, there should be a `kafka-storage-x.x.x-test.jar` file under `storage/build/libs`. Next, setting configurations in the broker side to enable tiered storage feature.
+@@ -79,7 +79,7 @@ After build successfully, there should be a `kafka-storage-x.x.x-test.jar` file
+ # This is the mandatory configuration for tiered storage.
+ # Here, we use the `LocalTieredStorage` built above.
+ remote.log.storage.manager.class.name=org.apache.kafka.server.log.remote.storage.LocalTieredStorage
+- remote.log.storage.manager.class.path=/PATH/TO/kafka-storage-4.2.0-test.jar
++ remote.log.storage.manager.class.path=/PATH/TO/kafka-storage-4.2.0-stackable0.0.0-dev-test.jar
+
+ # These 2 prefix are default values, but customizable
+ remote.log.storage.manager.impl.prefix=rsm.config.
+diff --git a/docs/streams/developer-guide/datatypes.md b/docs/streams/developer-guide/datatypes.md
+index 6354d6d54c..163571d1bf 100644
+--- a/docs/streams/developer-guide/datatypes.md
++++ b/docs/streams/developer-guide/datatypes.md
+@@ -92,7 +92,7 @@ Apache Kafka includes several built-in serde implementations for Java primitives
+
+ org.apache.kafka
+ kafka-clients
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+
+ This artifact provides the following serde implementations under the package [org.apache.kafka.common.serialization](https://github.com/apache/kafka/blob/4.2/clients/src/main/java/org/apache/kafka/common/serialization), which you can leverage when e.g., defining default serializers in your Streams configuration.
+@@ -220,7 +220,7 @@ Apache Kafka Streams includes serde implementations for windowed types in its `k
+
+ org.apache.kafka
+ kafka-streams
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+
+ This artifact provides the following windowed serde implementations under the package [org.apache.kafka.streams.kstream](https://github.com/apache/kafka/blob/4.2/streams/src/main/java/org/apache/kafka/streams/kstream):
+diff --git a/docs/streams/developer-guide/dsl-api.md b/docs/streams/developer-guide/dsl-api.md
+index 71b5c2f043..d9a35197cc 100644
+--- a/docs/streams/developer-guide/dsl-api.md
++++ b/docs/streams/developer-guide/dsl-api.md
+@@ -5785,7 +5785,7 @@ The library is cross-built with Scala 2.12 and 2.13. To reference the library co
+
+ org.apache.kafka
+ kafka-streams-scala_2.13
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+
+ To use the library compiled against Scala 2.12 replace the `artifactId` with `kafka-streams-scala_2.12`.
+@@ -5793,7 +5793,7 @@ To use the library compiled against Scala 2.12 replace the `artifactId` with `ka
+ When using SBT then you can reference the correct library using the following:
+
+
+- libraryDependencies += "org.apache.kafka" %% "kafka-streams-scala" % "4.2.0"
++ libraryDependencies += "org.apache.kafka" %% "kafka-streams-scala" % "4.2.0-stackable0.0.0-dev"
+
+ ## Sample Usage
+
+diff --git a/docs/streams/developer-guide/testing.md b/docs/streams/developer-guide/testing.md
+index e95292aaee..76c2a49f00 100644
+--- a/docs/streams/developer-guide/testing.md
++++ b/docs/streams/developer-guide/testing.md
+@@ -39,7 +39,7 @@ To test a Kafka Streams application, Kafka provides a test-utils artifact that c
+
+ org.apache.kafka
+ kafka-streams-test-utils
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+ test
+
+
+diff --git a/docs/streams/developer-guide/write-streams-app.md b/docs/streams/developer-guide/write-streams-app.md
+index 14d7f647b4..5cca9db806 100644
+--- a/docs/streams/developer-guide/write-streams-app.md
++++ b/docs/streams/developer-guide/write-streams-app.md
+@@ -73,7 +73,7 @@ Description
+
+ |
+
+-`4.2.0`
++`4.2.0-stackable0.0.0-dev`
+ |
+
+
+@@ -90,7 +90,7 @@ Description
+ |
+
+
+-`4.2.0`
++`4.2.0-stackable0.0.0-dev`
+ |
+
+
+@@ -107,7 +107,7 @@ Description
+ |
+
+
+-`4.2.0`
++`4.2.0-stackable0.0.0-dev`
+ |
+
+
+@@ -124,17 +124,17 @@ Example `pom.xml` snippet when using Maven:
+
+ org.apache.kafka
+ kafka-streams
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+
+ org.apache.kafka
+ kafka-clients
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+
+ org.apache.kafka
+ kafka-streams-scala_2.13
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+
+ # Using Kafka Streams within your application code
+diff --git a/docs/streams/quickstart.md b/docs/streams/quickstart.md
+index c571bf553d..88558d0d0b 100644
+--- a/docs/streams/quickstart.md
++++ b/docs/streams/quickstart.md
+@@ -66,11 +66,11 @@ As the first step, we will start Kafka (unless you already have it started) and
+
+ ### Step 1: Download the code
+
+-[Download](https://www.apache.org/dyn/closer.cgi?path=/kafka/4.2.0/kafka_2.13-4.2.0.tgz "Kafka downloads") the 4.2.0 release and un-tar it. Note that there are multiple downloadable Scala versions and we choose to use the recommended version (2.13) here:
++[Download](https://www.apache.org/dyn/closer.cgi?path=/kafka/4.2.0-stackable0.0.0-dev/kafka_2.13-4.2.0-stackable0.0.0-dev.tgz "Kafka downloads") the 4.2.0-stackable0.0.0-dev release and un-tar it. Note that there are multiple downloadable Scala versions and we choose to use the recommended version (2.13) here:
+
+
+- $ tar -xzf kafka_2.13-4.2.0.tgz
+- $ cd kafka_2.13-4.2.0
++ $ tar -xzf kafka_2.13-4.2.0-stackable0.0.0-dev.tgz
++ $ cd kafka_2.13-4.2.0-stackable0.0.0-dev
+
+ ### Step 2: Start the Kafka server
+
+diff --git a/docs/streams/tutorial.md b/docs/streams/tutorial.md
+index 290144fd42..11fef66372 100644
+--- a/docs/streams/tutorial.md
++++ b/docs/streams/tutorial.md
+@@ -38,7 +38,7 @@ We are going to use a Kafka Streams Maven Archetype for creating a Streams proje
+ $ mvn archetype:generate \
+ -DarchetypeGroupId=org.apache.kafka \
+ -DarchetypeArtifactId=streams-quickstart-java \
+- -DarchetypeVersion=4.2.0 \
++ -DarchetypeVersion=4.2.0-stackable0.0.0-dev \
+ -DgroupId=streams.examples \
+ -DartifactId=streams-quickstart \
+ -Dversion=0.1 \
+diff --git a/docs/streams/upgrade-guide.md b/docs/streams/upgrade-guide.md
+index 2f948c6324..d4b75bfebd 100644
+--- a/docs/streams/upgrade-guide.md
++++ b/docs/streams/upgrade-guide.md
+@@ -28,20 +28,20 @@ type: docs
+
+ # Upgrade Guide and API Changes
+
+-Upgrading from any older version to 4.2.0 is possible: if upgrading from 3.4 or below, you will need to do two rolling bounces, where during the first rolling bounce phase you set the config `upgrade.from="older version"` (possible values are `"2.4" - "3.4"`) and during the second you remove it. This is required to safely handle 2 changes. The first is a change in foreign-key join serialization format. The second is a change in the serialization format for an internal repartition topic. For more details, please refer to [KIP-904](https://cwiki.apache.org/confluence/x/P5VbDg):
++Upgrading from any older version to 4.2.0-stackable0.0.0-dev is possible: if upgrading from 3.4 or below, you will need to do two rolling bounces, where during the first rolling bounce phase you set the config `upgrade.from="older version"` (possible values are `"2.4" - "3.4"`) and during the second you remove it. This is required to safely handle 2 changes. The first is a change in foreign-key join serialization format. The second is a change in the serialization format for an internal repartition topic. For more details, please refer to [KIP-904](https://cwiki.apache.org/confluence/x/P5VbDg):
+
+ * prepare your application instances for a rolling bounce and make sure that config `upgrade.from` is set to the version from which it is being upgrade.
+ * bounce each instance of your application once
+- * prepare your newly deployed 4.2.0 application instances for a second round of rolling bounces; make sure to remove the value for config `upgrade.from`
++ * prepare your newly deployed 4.2.0-stackable0.0.0-dev application instances for a second round of rolling bounces; make sure to remove the value for config `upgrade.from`
+ * bounce each instance of your application once more to complete the upgrade
+
+
+
+-As an alternative, an offline upgrade is also possible. Upgrading from any versions as old as 0.11.0.x to 4.2.0 in offline mode require the following steps:
++As an alternative, an offline upgrade is also possible. Upgrading from any versions as old as 0.11.0.x to 4.2.0-stackable0.0.0-dev in offline mode require the following steps:
+
+ * stop all old (e.g., 0.11.0.x) application instances
+ * update your code and swap old code and jar file with new code and new jar file
+- * restart all new (4.2.0) application instances
++ * restart all new (4.2.0-stackable0.0.0-dev) application instances
+
+
+
+@@ -63,7 +63,7 @@ Starting in Kafka Streams 2.6.x, a new processing mode is available, named EOS v
+
+ Since 2.6.0 release, Kafka Streams depends on a RocksDB version that requires MacOS 10.14 or higher.
+
+-## Streams API changes in 4.2.0
++## Streams API changes in 4.2.0-stackable0.0.0-dev
+
+ ### General Availability for a core feature set of the Streams Rebalance Protocol (KIP-1071)
+
+@@ -295,7 +295,7 @@ Kafka Streams does not send a "leave group" request when an instance is closed.
+ * `KStream KStream.process(ProcessorSupplier, ...)`
+ * `KStream KStream.processValues(FixedKeyProcessorSupplier, ...)`
+
+-Both new methods have multiple overloads and return a `KStream` instead of `void` as the deprecated `process()` methods did. In addition, `FixedKeyProcessor`, `FixedKeyRecord`, `FixedKeyProcessorContext`, and `ContextualFixedKeyProcessor` are introduced to guard against disallowed key modification inside `processValues()`. Furthermore, `ProcessingContext` is added for a better interface hierarchy. **CAUTION:** The newly added `KStream.processValues()` method introduced a regression bug ([KAFKA-19668](https://issues.apache.org/jira/browse/KAFKA-19668)). If you have "merge repartition topics" optimization enabled, it is not safe to migrate from `transformValues()` to `processValues()` in 3.3.0 release. The bug is only fixed with Kafka Streams 4.0.1, 4.1.1, and 4.2.0. For more details, please refer to the [migration guide](/42/streams/developer-guide/dsl-api/#transformers-removal-and-migration-to-processors).
++Both new methods have multiple overloads and return a `KStream` instead of `void` as the deprecated `process()` methods did. In addition, `FixedKeyProcessor`, `FixedKeyRecord`, `FixedKeyProcessorContext`, and `ContextualFixedKeyProcessor` are introduced to guard against disallowed key modification inside `processValues()`. Furthermore, `ProcessingContext` is added for a better interface hierarchy. **CAUTION:** The newly added `KStream.processValues()` method introduced a regression bug ([KAFKA-19668](https://issues.apache.org/jira/browse/KAFKA-19668)). If you have "merge repartition topics" optimization enabled, it is not safe to migrate from `transformValues()` to `processValues()` in 3.3.0 release. The bug is only fixed with Kafka Streams 4.0.1, 4.1.1, and 4.2.0-stackable0.0.0-dev. For more details, please refer to the [migration guide](/42/streams/developer-guide/dsl-api/#transformers-removal-and-migration-to-processors).
+
+ Emitting a windowed aggregation result only after a window is closed is currently supported via the `suppress()` operator. However, `suppress()` uses an in-memory implementation and does not support RocksDB. To close this gap, [KIP-825](https://cwiki.apache.org/confluence/x/n7fkCw) introduces "emit strategies", which are built into the aggregation operator directly to use the already existing RocksDB store. `TimeWindowedKStream.emitStrategy(EmitStrategy)` and `SessionWindowedKStream.emitStrategy(EmitStrategy)` allow picking between "emit on window update" (default) and "emit on window close" strategies. Additionally, a few new emit metrics are added, as well as a necessary new method, `SessionStore.findSessions(long, long)`.
+
+diff --git a/gradle.properties b/gradle.properties
+index 7d294bfc15..b2d6fa66f9 100644
+--- a/gradle.properties
++++ b/gradle.properties
+@@ -22,7 +22,7 @@ group=org.apache.kafka
+ # - streams/quickstart/pom.xml
+ # - streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
+ # - streams/quickstart/java/pom.xml
+-version=4.2.0
++version=4.2.0-stackable0.0.0-dev
+ scalaVersion=2.13.17
+ # Adding swaggerVersion in gradle.properties to have a single version in place for swagger
+ swaggerVersion=2.2.39
+diff --git a/streams/quickstart/java/pom.xml b/streams/quickstart/java/pom.xml
+index 1162e1a180..6448eb9fe9 100644
+--- a/streams/quickstart/java/pom.xml
++++ b/streams/quickstart/java/pom.xml
+@@ -26,7 +26,7 @@
+
+ org.apache.kafka
+ streams-quickstart
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+ ..
+
+
+diff --git a/streams/quickstart/java/src/main/resources/archetype-resources/pom.xml b/streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
+index 027f4830bf..d4e3a0a4bd 100644
+--- a/streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
++++ b/streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
+@@ -29,7 +29,7 @@
+
+
+ UTF-8
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+ 2.0.16
+
+
+diff --git a/streams/quickstart/pom.xml b/streams/quickstart/pom.xml
+index b7e51c15c5..5ce42abd98 100644
+--- a/streams/quickstart/pom.xml
++++ b/streams/quickstart/pom.xml
+@@ -22,7 +22,7 @@
+ org.apache.kafka
+ streams-quickstart
+ pom
+- 4.2.0
++ 4.2.0-stackable0.0.0-dev
+
+ Kafka Streams :: Quickstart
+
+diff --git a/tests/kafkatest/__init__.py b/tests/kafkatest/__init__.py
+index b192f8f528..0c0d0414c6 100644
+--- a/tests/kafkatest/__init__.py
++++ b/tests/kafkatest/__init__.py
+@@ -22,4 +22,4 @@
+ # Instead, in development branches, the version should have a suffix of the form ".devN"
+ #
+ # For example, when Kafka is at version 1.0.0-SNAPSHOT, this should be something like "1.0.0.dev0"
+-__version__ = '4.2.0'
++__version__ = '4.2.0-stackable0.0.0-dev'
+diff --git a/tests/kafkatest/version.py b/tests/kafkatest/version.py
+index 86d74eee12..3a782bb830 100644
+--- a/tests/kafkatest/version.py
++++ b/tests/kafkatest/version.py
+@@ -100,21 +100,21 @@ class KafkaVersion(LooseVersion):
+ def supports_command_config(self):
+ # According to KIP-1147, --producer.config and --consumer.config have been deprecated and will be removed in future versions
+ # For backward compatibility, we select the configuration based on node version:
+- # - For versions 4.2.0 and above, use --command-config
++ # - For versions 4.2.0-stackable0.0.0-dev and above, use --command-config
+ # - For older versions, continue using --producer.config or --consumer.config
+ return self >= V_4_2_0
+
+ def supports_command_property(self):
+ # According to KIP-1147, --producer-property and --consumer-property have been deprecated and will be removed in future versions
+ # For backward compatibility, we select the configuration based on node version:
+- # - For versions 4.2.0 and above, use --command-property
++ # - For versions 4.2.0-stackable0.0.0-dev and above, use --command-property
+ # - For older versions, continue using --producer-property or --consumer-property
+ return self >= V_4_2_0
+
+ def supports_formatter_property(self):
+ # According to KIP-1147, --property has been deprecated and will be removed in future versions
+ # For backward compatibility, we select the configuration based on node version:
+- # - For versions 4.2.0 and above, use --formatter-property
++ # - For versions 4.2.0-stackable0.0.0-dev and above, use --formatter-property
+ # - For older versions, continue using --property
+ return self >= V_4_2_0
+
+@@ -128,7 +128,7 @@ def get_version(node=None):
+ return DEV_BRANCH
+
+ DEV_BRANCH = KafkaVersion("dev")
+-DEV_VERSION = KafkaVersion("4.2.0-SNAPSHOT")
++DEV_VERSION = KafkaVersion("4.2.0-stackable0.0.0-dev-SNAPSHOT")
+
+ LATEST_STABLE_TRANSACTION_VERSION = 2
+ # This should match the LATEST_PRODUCTION version defined in MetadataVersion.java
+@@ -247,5 +247,5 @@ V_4_1_1 = KafkaVersion("4.1.1")
+ LATEST_4_1 = V_4_1_1
+
+ # 4.2.x version
+-V_4_2_0 = KafkaVersion("4.2.0")
++V_4_2_0 = KafkaVersion("4.2.0-stackable0.0.0-dev")
+ LATEST_4_2 = V_4_2_0
diff --git a/kafka/stackable/patches/4.2.0/0004-Include-jackson-dataformat-xml-dependency.patch b/kafka/stackable/patches/4.2.0/0004-Include-jackson-dataformat-xml-dependency.patch
new file mode 100644
index 000000000..2b1bb9767
--- /dev/null
+++ b/kafka/stackable/patches/4.2.0/0004-Include-jackson-dataformat-xml-dependency.patch
@@ -0,0 +1,131 @@
+From f77fdcc430c86388d9c575b8351488691915876b Mon Sep 17 00:00:00 2001
+From: Razvan-Daniel Mihai <84674+razvan@users.noreply.github.com>
+Date: Wed, 13 May 2026 17:25:07 +0300
+Subject: Include jackson dataformat xml dependency
+
+---
+ build.gradle | 15 ++++++++++++++-
+ gradle/dependencies.gradle | 1 +
+ 2 files changed, 15 insertions(+), 1 deletion(-)
+
+diff --git a/build.gradle b/build.gradle
+index 2bdfb80d85..0ed19d18bb 100644
+--- a/build.gradle
++++ b/build.gradle
+@@ -185,13 +185,15 @@ ext {
+ libs.slf4jLog4j2,
+ libs.junitPlatformLanucher,
+ libs.jacksonDatabindYaml,
++ libs.jacksonDatabindXml,
+ project(":test-common:test-common-util")
+ ]
+
+ log4jReleaseLibs = [
+ libs.slf4jLog4j2,
+ libs.log4j1Bridge2Api,
+- libs.jacksonDatabindYaml
++ libs.jacksonDatabindYaml,
++ libs.jacksonDatabindXml
+ ]
+
+ log4j2Libs = [
+@@ -1120,6 +1122,7 @@ project(':core') {
+ implementation libs.jacksonDataformatCsv
+ implementation libs.jacksonJDK8Datatypes
+ implementation libs.jacksonDatabindYaml
++ implementation libs.jacksonDatabindXml
+ implementation libs.joptSimple
+ implementation libs.jose4j
+ implementation libs.metrics
+@@ -1534,6 +1537,7 @@ project(':group-coordinator') {
+ testImplementation project(':server-common').sourceSets.test.output
+ testImplementation project(':coordinator-common').sourceSets.test.output
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoCore
+ testImplementation testLog4j2Libs
+@@ -1656,6 +1660,7 @@ project(':test-common:test-common-runtime') {
+ implementation libs.junitPlatformLanucher
+ implementation libs.junitJupiter
+ implementation libs.jacksonDatabindYaml
++ implementation libs.jacksonDatabindXml
+ implementation libs.slf4jApi
+
+ testImplementation libs.junitJupiter
+@@ -2130,6 +2135,7 @@ project(':raft') {
+ testImplementation project(':clients')
+ testImplementation project(':clients').sourceSets.test.output
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoCore
+ testImplementation libs.jqwik
+@@ -2227,6 +2233,7 @@ project(':server-common') {
+ testImplementation project(':clients')
+ testImplementation project(':clients').sourceSets.test.output
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoCore
+ testImplementation testLog4j2Libs
+@@ -2368,6 +2375,7 @@ project(':storage') {
+ testImplementation project(':transaction-coordinator')
+ testImplementation libs.hamcrest
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoCore
+ testImplementation libs.bcpkix
+@@ -2685,6 +2693,7 @@ project(':shell') {
+ testImplementation project(':server-common')
+ testImplementation project(':server-common').sourceSets.test.output
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation testLog4j2Libs
+
+@@ -2734,6 +2743,7 @@ project(':streams') {
+
+ testImplementation project(':clients').sourceSets.test.output
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.bcpkix
+ testImplementation libs.hamcrest
+@@ -2879,6 +2889,7 @@ project(':streams:streams-scala') {
+ testImplementation project(':streams:test-utils')
+
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoJunitJupiter // supports MockitoExtension
+ testImplementation testLog4j2Libs
+@@ -2983,6 +2994,7 @@ project(':streams:test-utils') {
+
+ testImplementation project(':clients').sourceSets.test.output
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoCore
+ testImplementation libs.hamcrest
+@@ -3678,6 +3690,7 @@ project(':connect:runtime') {
+ testImplementation project(':server-common').sourceSets.test.output
+
+ testImplementation libs.jacksonDatabindYaml
++ testImplementation libs.jacksonDatabindXml
+ testImplementation libs.junitJupiter
+ testImplementation libs.mockitoCore
+ testImplementation libs.mockitoJunitJupiter
+diff --git a/gradle/dependencies.gradle b/gradle/dependencies.gradle
+index fb0465b66e..094d4545be 100644
+--- a/gradle/dependencies.gradle
++++ b/gradle/dependencies.gradle
+@@ -157,6 +157,7 @@ libs += [
+ jacksonAnnotations: "com.fasterxml.jackson.core:jackson-annotations:$versions.jackson",
+ jacksonDatabind: "com.fasterxml.jackson.core:jackson-databind:$versions.jackson",
+ jacksonDatabindYaml: "com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:$versions.jackson",
++ jacksonDatabindXml: "com.fasterxml.jackson.dataformat:jackson-dataformat-xml:$versions.jackson",
+ jacksonDataformatCsv: "com.fasterxml.jackson.dataformat:jackson-dataformat-csv:$versions.jackson",
+ jacksonJDK8Datatypes: "com.fasterxml.jackson.datatype:jackson-datatype-jdk8:$versions.jackson",
+ jacksonBlackbird: "com.fasterxml.jackson.module:jackson-module-blackbird:$versions.jackson",
diff --git a/kafka/stackable/patches/4.2.0/patchable.toml b/kafka/stackable/patches/4.2.0/patchable.toml
new file mode 100644
index 000000000..ced9a66f7
--- /dev/null
+++ b/kafka/stackable/patches/4.2.0/patchable.toml
@@ -0,0 +1 @@
+base = "a18251bae0b825c69794a50dffd4c3100cf5ca5b"
|