You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by ch...@apache.org on 2026/10/19 18:17:37 UTC

(kafka) 04/04: MINOR: Update documentation version references to 4.4 (#23869)

This is an automated email from the ASF dual-hosted git repository.

chia7712 pushed a commit to branch 4.4
in repository https://gitbox.apache.org/repos/asf/kafka.git

commit bc98159707e7a1ce55553a9f77ace34506a7ea40
Author: majialong <ma...@gmail.com>
AuthorDate: Tue Oct 20 02:11:49 2026 +0800

    MINOR: Update documentation version references to 4.4 (#23869)
    
    Update outdated documentation version references to 4.4. Adjust the
    tiered storage example to use the test fixtures JAR, as
    `LocalTieredStorage` has moved to `src/testFixtures`.
    
    Reviewers: Chia-Ping Tsai <ch...@gmail.com>
---
 docs/_index.md                                     |  4 ++--
 docs/apis/_index.md                                | 24 +++++++++++-----------
 docs/documentation/legacy-redirect.md              |  2 +-
 docs/getting-started/quickstart.md                 | 18 ++++++++--------
 docs/kafka-connect/user-guide.md                   |  2 +-
 docs/operations/tiered-storage.md                  | 10 ++++-----
 docs/streams/developer-guide/datatypes.md          | 18 ++++++++--------
 docs/streams/developer-guide/dsl-api.md            |  4 ++--
 .../streams/developer-guide/interactive-queries.md |  8 ++++----
 docs/streams/developer-guide/testing.md            |  2 +-
 docs/streams/developer-guide/write-streams-app.md  | 12 +++++------
 docs/streams/quickstart.md                         |  8 ++++----
 docs/streams/tutorial.md                           |  2 +-
 docs/streams/upgrade-guide.md                      |  4 ++--
 14 files changed, 59 insertions(+), 59 deletions(-)

diff --git a/docs/_index.md b/docs/_index.md
index e63c72bfd30..20347adfa22 100644
--- a/docs/_index.md
+++ b/docs/_index.md
@@ -1,6 +1,6 @@
 ---
-title: AK 4.3.X
-description: Apache Kafka documentation for version 4.3.x.
+title: AK 4.4.X
+description: Apache Kafka documentation for version 4.4.x.
 weight: 
 tags: ['kafka', 'docs']
 aliases: 
diff --git a/docs/apis/_index.md b/docs/apis/_index.md
index df3ac0bed23..a0c191e68c9 100644
--- a/docs/apis/_index.md
+++ b/docs/apis/_index.md
@@ -40,7 +40,7 @@ Kafka exposes all its functionality over a language-independent protocol which h
 
 The Producer API allows applications to send streams of data to topics in the Kafka cluster. 
 
-Examples of using the producer are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/clients/producer/KafkaProducer.html "Kafka 4.3 Javadoc"). 
+Examples of using the producer are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/clients/producer/KafkaProducer.html "Kafka 4.4 Javadoc"). 
 
 To use the producer, add the following Maven dependency to your project: 
 
@@ -48,7 +48,7 @@ To use the producer, add the following Maven dependency to your project:
 <dependency>
 	<groupId>org.apache.kafka</groupId>
 	<artifactId>kafka-clients</artifactId>
-	<version>4.3.1</version>
+	<version>4.4.0</version>
 </dependency>
 ```
 
@@ -56,7 +56,7 @@ To use the producer, add the following Maven dependency to your project:
 
 The Consumer API allows applications to read streams of data from topics in the Kafka cluster. 
 
-Examples of using the consumer are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.html "Kafka 4.3 Javadoc"). 
+Examples of using the consumer are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.html "Kafka 4.4 Javadoc"). 
 
 To use the consumer, add the following Maven dependency to your project: 
 
@@ -64,7 +64,7 @@ To use the consumer, add the following Maven dependency to your project:
 <dependency>
 	<groupId>org.apache.kafka</groupId>
 	<artifactId>kafka-clients</artifactId>
-	<version>4.3.1</version>
+	<version>4.4.0</version>
 </dependency>
 ```
 
@@ -72,7 +72,7 @@ To use the consumer, add the following Maven dependency to your project:
 
 The Share Consumer API enables applications in a share group to cooperatively consume and process data from Kafka topics. 
 
-Examples of using the share consumer are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaShareConsumer.html "Kafka 4.3 Javadoc"). 
+Examples of using the share consumer are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaShareConsumer.html "Kafka 4.4 Javadoc"). 
 
 To use the share consumer, add the following Maven dependency to your project: 
 
@@ -80,7 +80,7 @@ To use the share consumer, add the following Maven dependency to your project:
 <dependency>
 	<groupId>org.apache.kafka</groupId>
 	<artifactId>kafka-clients</artifactId>
-	<version>4.3.1</version>
+	<version>4.4.0</version>
 </dependency>
 ```
 
@@ -88,7 +88,7 @@ To use the share consumer, add the following Maven dependency to your project:
 
 The [Streams](/{version}/streams/) API allows transforming streams of data from input topics to output topics. 
 
-Examples of using this library are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/streams/KafkaStreams.html "Kafka 4.3 Javadoc"). 
+Examples of using this library are shown in the [javadocs](/{version}/javadoc/index.html?org/apache/kafka/streams/KafkaStreams.html "Kafka 4.4 Javadoc"). 
 
 Additional documentation on using the Streams API is available [here](/{version}/streams/). 
 
@@ -98,7 +98,7 @@ To use Kafka Streams, add the following Maven dependency to your project:
 <dependency>
 	<groupId>org.apache.kafka</groupId>
 	<artifactId>kafka-streams</artifactId>
-	<version>4.3.1</version>
+	<version>4.4.0</version>
 </dependency>
 ```
 
@@ -114,7 +114,7 @@ To use Kafka Streams DSL for Scala 2.13, add the following Maven dependency to y
 <dependency>
 	<groupId>org.apache.kafka</groupId>
 	<artifactId>kafka-streams-scala_2.13</artifactId>
-	<version>4.3.1</version>
+	<version>4.4.0</version>
 </dependency>
 ```
 
@@ -124,7 +124,7 @@ The Connect API allows implementing connectors that continually pull from some s
 
 Many users of Connect won't need to use this API directly, though, they can use pre-built connectors without needing to write any code. Additional information on using Connect is available [here](/documentation.html#connect). 
 
-Those who want to implement custom connectors can see the [javadoc](/{version}/javadoc/index.html?org/apache/kafka/connect "Kafka 4.3 Javadoc"). 
+Those who want to implement custom connectors can see the [javadoc](/{version}/javadoc/index.html?org/apache/kafka/connect "Kafka 4.4 Javadoc"). 
 
 # Admin API
 
@@ -136,8 +136,8 @@ To use the Admin API, add the following Maven dependency to your project:
 <dependency>
 	<groupId>org.apache.kafka</groupId>
 	<artifactId>kafka-clients</artifactId>
-	<version>4.3.1</version>
+	<version>4.4.0</version>
 </dependency>
 ```
 
-For more information about the Admin APIs, see the [javadoc](/{version}/javadoc/index.html?org/apache/kafka/clients/admin/Admin.html "Kafka 4.3 Javadoc"). 
+For more information about the Admin APIs, see the [javadoc](/{version}/javadoc/index.html?org/apache/kafka/clients/admin/Admin.html "Kafka 4.4 Javadoc"). 
diff --git a/docs/documentation/legacy-redirect.md b/docs/documentation/legacy-redirect.md
index 4a8115c60e9..7ca9052edfd 100644
--- a/docs/documentation/legacy-redirect.md
+++ b/docs/documentation/legacy-redirect.md
@@ -1,6 +1,6 @@
 ---
 title: "Documentation Redirect Legacy"
-url: "/43/documentation.html"
+url: "/44/documentation.html"
 robots: "noindex"
 _build:
   list: false
diff --git a/docs/getting-started/quickstart.md b/docs/getting-started/quickstart.md
index 22f614986af..afff38db639 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.3.0/kafka_2.13-4.3.0.tgz) the latest Kafka release and extract it: 
+[Download](https://www.apache.org/dyn/closer.cgi?path=/kafka/4.4.0/kafka_2.13-4.4.0.tgz) the latest Kafka release and extract it: 
 
 ```bash
-tar -xzf kafka_2.13-4.3.0.tgz
-cd kafka_2.13-4.3.0
+tar -xzf kafka_2.13-4.4.0.tgz
+cd kafka_2.13-4.4.0
 ```
 
 ## Step 2: Start the Kafka environment
@@ -68,13 +68,13 @@ Once the Kafka server has successfully launched, you will have a basic Kafka env
 Get the Docker image:
 
 ```bash
-docker pull apache/kafka:4.3.0
+docker pull apache/kafka:4.4.0
 ```
 
 Start the Kafka Docker container: 
 
 ```bash
-docker run -p 9092:9092 apache/kafka:4.3.0
+docker run -p 9092:9092 apache/kafka:4.4.0
 ```
 
 ### Using GraalVM Based Native Apache Kafka Docker Image
@@ -82,13 +82,13 @@ docker run -p 9092:9092 apache/kafka:4.3.0
 Get the Docker image:
 
 ```bash
-docker pull apache/kafka-native:4.3.0
+docker pull apache/kafka-native:4.4.0
 ```
 
 Start the Kafka Docker container:
 
 ```bash
-docker run -p 9092:9092 apache/kafka-native:4.3.0
+docker run -p 9092:9092 apache/kafka-native:4.4.0
 ```
 
 ## Step 3: Create a topic to store your events
@@ -162,12 +162,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.3.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](/{version}/configuration/kafka-connect-configs/#connectcon [...]
+First, make sure to add `connect-file-4.4.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](/{version}/configuration/kafka-connect-configs/#connectcon [...]
 
 Edit the `config/connect-standalone.properties` file, add or change the `plugin.path` configuration property match the following, and save the file: 
 
 ```bash
-echo "plugin.path=libs/connect-file-4.3.0.jar" >> config/connect-standalone.properties
+echo "plugin.path=libs/connect-file-4.4.0.jar" >> config/connect-standalone.properties
 ```
 
 Then, start by creating some seed data to test with: 
diff --git a/docs/kafka-connect/user-guide.md b/docs/kafka-connect/user-guide.md
index 1f48f8c63e0..e4b05e7cbbe 100644
--- a/docs/kafka-connect/user-guide.md
+++ b/docs/kafka-connect/user-guide.md
@@ -43,7 +43,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.3.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.4.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).
 
 
 
diff --git a/docs/operations/tiered-storage.md b/docs/operations/tiered-storage.md
index 7d1559c692a..021dddea8fc 100644
--- a/docs/operations/tiered-storage.md
+++ b/docs/operations/tiered-storage.md
@@ -57,17 +57,17 @@ The configuration prefixed with `local` are to specify the time/size the "local"
 
 ## Quick Start Example
 
-Apache Kafka doesn't provide an out-of-the-box RemoteStorageManager implementation. To have a preview of the tiered storage feature, the [LocalTieredStorage](https://github.com/apache/kafka/blob/trunk/storage/src/test/java/org/apache/kafka/server/log/remote/storage/LocalTieredStorage.java) implemented for integration test can be used, which will create a temporary directory in local storage to simulate the remote storage. 
+Apache Kafka doesn't provide an out-of-the-box RemoteStorageManager implementation. To have a preview of the tiered storage feature, the [LocalTieredStorage](https://github.com/apache/kafka/blob/trunk/storage/src/testFixtures/java/org/apache/kafka/server/log/remote/storage/LocalTieredStorage.java) implemented for integration test can be used, which will create a temporary directory in local storage to simulate the remote storage. 
 
 To adopt the `LocalTieredStorage`, the test library needs to be built locally:
 
 ```bash
 # please checkout to the specific version tag you're using before building it
-# ex: `git checkout 4.3.0`
-$ ./gradlew clean :storage:testJar
+# ex: `git checkout 4.4.0`
+$ ./gradlew clean :storage:testFixturesJar
 ```
 
-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.
+After build successfully, there should be a `kafka-storage-x.x.x-test-fixtures.jar` file under `storage/build/libs`. Next, setting configurations in the broker side to enable tiered storage feature.
 
 ```properties
 # Sample KRaft broker server.properties listening on PLAINTEXT://:9092
@@ -80,7 +80,7 @@ remote.log.metadata.manager.listener.name=PLAINTEXT
 # 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.3.0-test.jar
+remote.log.storage.manager.class.path=/PATH/TO/kafka-storage-4.4.0-test-fixtures.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 dd25b1c697d..f11149f73cd 100644
--- a/docs/streams/developer-guide/datatypes.md
+++ b/docs/streams/developer-guide/datatypes.md
@@ -92,10 +92,10 @@ Apache Kafka includes several built-in serde implementations for Java primitives
     <dependency>
         <groupId>org.apache.kafka</groupId>
         <artifactId>kafka-clients</artifactId>
-        <version>4.3.0</version>
+        <version>4.4.0</version>
     </dependency>
 
-This artifact provides the following serde implementations under the package [org.apache.kafka.common.serialization](https://github.com/apache/kafka/blob/4.3/clients/src/main/java/org/apache/kafka/common/serialization), which you can leverage when e.g., defining default serializers in your Streams configuration.  
+This artifact provides the following serde implementations under the package [org.apache.kafka.common.serialization](https://github.com/apache/kafka/blob/4.4/clients/src/main/java/org/apache/kafka/common/serialization), which you can leverage when e.g., defining default serializers in your Streams configuration.  
   
 <table>  
 <tr>  
@@ -200,13 +200,13 @@ Boolean
 
 **Tip**
 
-[Bytes](https://github.com/apache/kafka/blob/4.3/clients/src/main/java/org/apache/kafka/common/utils/Bytes.java) is a wrapper for Java's `byte[]` (byte array) that supports proper equality and ordering semantics. You may want to consider using `Bytes` instead of `byte[]` in your applications.
+[Bytes](https://github.com/apache/kafka/blob/4.4/clients/src/main/java/org/apache/kafka/common/utils/Bytes.java) is a wrapper for Java's `byte[]` (byte array) that supports proper equality and ordering semantics. You may want to consider using `Bytes` instead of `byte[]` in your applications.
 
 ## JSON
 
 The Kafka Streams code examples also include a basic serde implementation for JSON:
 
-  * [PageViewTypedDemo](https://github.com/apache/kafka/blob/4.3/streams/examples/src/main/java/org/apache/kafka/streams/examples/pageview/PageViewTypedDemo.java#L83)
+  * [PageViewTypedDemo](https://github.com/apache/kafka/blob/4.4/streams/examples/src/main/java/org/apache/kafka/streams/examples/pageview/PageViewTypedDemo.java#L83)
 
 
 
@@ -220,10 +220,10 @@ Apache Kafka Streams includes serde implementations for windowed types in its `k
     <dependency>
         <groupId>org.apache.kafka</groupId>
         <artifactId>kafka-streams</artifactId>
-        <version>4.3.0</version>
+        <version>4.4.0</version>
     </dependency>
 
-This artifact provides the following windowed serde implementations under the package [org.apache.kafka.streams.kstream](https://github.com/apache/kafka/blob/4.3/streams/src/main/java/org/apache/kafka/streams/kstream):
+This artifact provides the following windowed serde implementations under the package [org.apache.kafka.streams.kstream](https://github.com/apache/kafka/blob/4.4/streams/src/main/java/org/apache/kafka/streams/kstream):
 
 **Serdes:**
 
@@ -300,9 +300,9 @@ The following `StreamsConfig` parameters are deprecated in favor of passing para
 
 If you need to implement custom Serdes, your best starting point is to take a look at the source code references of existing Serdes (see previous section). Typically, your workflow will be similar to:
 
-  1. Write a _serializer_ for your data type `T` by implementing [org.apache.kafka.common.serialization.Serializer](https://github.com/apache/kafka/blob/4.3/clients/src/main/java/org/apache/kafka/common/serialization/Serializer.java).
-  2. Write a _deserializer_ for `T` by implementing [org.apache.kafka.common.serialization.Deserializer](https://github.com/apache/kafka/blob/4.3/clients/src/main/java/org/apache/kafka/common/serialization/Deserializer.java).
-  3. Write a _serde_ for `T` by implementing [org.apache.kafka.common.serialization.Serde](https://github.com/apache/kafka/blob/4.3/clients/src/main/java/org/apache/kafka/common/serialization/Serde.java), which you either do manually (see existing Serdes in the previous section) or by leveraging helper functions in [Serdes](https://github.com/apache/kafka/blob/4.3/clients/src/main/java/org/apache/kafka/common/serialization/Serdes.java) such as `Serdes.serdeFrom(Serializer<T>, Deserialize [...]
+  1. Write a _serializer_ for your data type `T` by implementing [org.apache.kafka.common.serialization.Serializer](https://github.com/apache/kafka/blob/4.4/clients/src/main/java/org/apache/kafka/common/serialization/Serializer.java).
+  2. Write a _deserializer_ for `T` by implementing [org.apache.kafka.common.serialization.Deserializer](https://github.com/apache/kafka/blob/4.4/clients/src/main/java/org/apache/kafka/common/serialization/Deserializer.java).
+  3. Write a _serde_ for `T` by implementing [org.apache.kafka.common.serialization.Serde](https://github.com/apache/kafka/blob/4.4/clients/src/main/java/org/apache/kafka/common/serialization/Serde.java), which you either do manually (see existing Serdes in the previous section) or by leveraging helper functions in [Serdes](https://github.com/apache/kafka/blob/4.4/clients/src/main/java/org/apache/kafka/common/serialization/Serdes.java) such as `Serdes.serdeFrom(Serializer<T>, Deserialize [...]
 
 
 
diff --git a/docs/streams/developer-guide/dsl-api.md b/docs/streams/developer-guide/dsl-api.md
index 3685c76309f..6c2f33a57b1 100644
--- a/docs/streams/developer-guide/dsl-api.md
+++ b/docs/streams/developer-guide/dsl-api.md
@@ -5805,7 +5805,7 @@ The library is cross-built with Scala 2.12 and 2.13. To reference the library co
     <dependency>
       <groupId>org.apache.kafka</groupId>
       <artifactId>kafka-streams-scala_2.13</artifactId>
-      <version>4.3.0</version>
+      <version>4.4.0</version>
     </dependency>
 
 To use the library compiled against Scala 2.12 replace the `artifactId` with `kafka-streams-scala_2.12`.
@@ -5813,7 +5813,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.3.0"
+    libraryDependencies += "org.apache.kafka" %% "kafka-streams-scala" % "4.4.0"
 
 ## Sample Usage
 
diff --git a/docs/streams/developer-guide/interactive-queries.md b/docs/streams/developer-guide/interactive-queries.md
index 49266d8bd43..1b9dca12330 100644
--- a/docs/streams/developer-guide/interactive-queries.md
+++ b/docs/streams/developer-guide/interactive-queries.md
@@ -177,7 +177,7 @@ Note: These examples use `QueryableStoreTypes.keyValueStore()` and `ReadOnlyKeyV
     KafkaStreams streams = new KafkaStreams(builder, props);
     streams.start();
 
-After the application has started, you can get access to "CountsKeyValueStore" and then query it via the [ReadOnlyKeyValueStore](https://github.com/apache/kafka/blob/4.3/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyKeyValueStore.java) API:
+After the application has started, you can get access to "CountsKeyValueStore" and then query it via the [ReadOnlyKeyValueStore](https://github.com/apache/kafka/blob/4.4/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyKeyValueStore.java) API:
     
     
     // Get the key-value store CountsKeyValueStore
@@ -238,7 +238,7 @@ Note: These examples use `QueryableStoreTypes.windowStore()` and `ReadOnlyWindow
     groupedByWord.windowedBy(TimeWindows.ofSizeWithNoGrace(Duration.ofSeconds(60)))
       .count(Materialized.<String, Long, WindowStore<Bytes, byte[]>as("CountsWindowStore"));
 
-After the application has started, you can get access to "CountsWindowStore" and then query it via the [ReadOnlyWindowStore](https://github.com/apache/kafka/blob/4.3/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyWindowStore.java) API:
+After the application has started, you can get access to "CountsWindowStore" and then query it via the [ReadOnlyWindowStore](https://github.com/apache/kafka/blob/4.4/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyWindowStore.java) API:
     
     
     // Get the window store named "CountsWindowStore"
@@ -526,7 +526,7 @@ The class/interface hierarchy for your custom store might look something like:
 
 To make this store queryable you must:
 
-  * Provide an implementation of [QueryableStoreType](https://github.com/apache/kafka/blob/4.3/streams/src/main/java/org/apache/kafka/streams/state/QueryableStoreType.java).
+  * Provide an implementation of [QueryableStoreType](https://github.com/apache/kafka/blob/4.4/streams/src/main/java/org/apache/kafka/streams/state/QueryableStoreType.java).
   * Provide a wrapper class that has access to all of the underlying instances of the store and is used for querying.
 
 
@@ -549,7 +549,7 @@ Here is how to implement `QueryableStoreType`:
 
 A wrapper class is required because each instance of a Kafka Streams application may run multiple stream tasks and manage multiple local instances of a particular state store. The wrapper class hides this complexity and lets you query a "logical" state store by name without having to know about all of the underlying local instances of that state store.
 
-When implementing your wrapper class you must use the [StateStoreProvider](https://github.com/apache/kafka/blob/4.3/streams/src/main/java/org/apache/kafka/streams/state/internals/StateStoreProvider.java) interface to get access to the underlying instances of your store. `StateStoreProvider#stores(String storeName, QueryableStoreType<T> queryableStoreType)` returns a `List` of state stores with the given storeName and of the type as defined by `queryableStoreType`.
+When implementing your wrapper class you must use the [StateStoreProvider](https://github.com/apache/kafka/blob/4.4/streams/src/main/java/org/apache/kafka/streams/state/internals/StateStoreProvider.java) interface to get access to the underlying instances of your store. `StateStoreProvider#stores(String storeName, QueryableStoreType<T> queryableStoreType)` returns a `List` of state stores with the given storeName and of the type as defined by `queryableStoreType`.
 
 Here is an example implementation of the wrapper:
     
diff --git a/docs/streams/developer-guide/testing.md b/docs/streams/developer-guide/testing.md
index 4de4efa0422..6a6ab795242 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
     <dependency>
         <groupId>org.apache.kafka</groupId>
         <artifactId>kafka-streams-test-utils</artifactId>
-        <version>4.3.0</version>
+        <version>4.4.0</version>
         <scope>test</scope>
     </dependency>
 
diff --git a/docs/streams/developer-guide/write-streams-app.md b/docs/streams/developer-guide/write-streams-app.md
index bb43c47cd0d..6120835a5eb 100644
--- a/docs/streams/developer-guide/write-streams-app.md
+++ b/docs/streams/developer-guide/write-streams-app.md
@@ -73,7 +73,7 @@ Description
 </td>  
 <td>
 
-`4.3.0`
+`4.4.0`
 </td>  
 <td>
 
@@ -90,7 +90,7 @@ Description
 </td>  
 <td>
 
-`4.3.0`
+`4.4.0`
 </td>  
 <td>
 
@@ -107,7 +107,7 @@ Description
 </td>  
 <td>
 
-`4.3.0`
+`4.4.0`
 </td>  
 <td>
 
@@ -124,17 +124,17 @@ Example `pom.xml` snippet when using Maven:
     <dependency>
         <groupId>org.apache.kafka</groupId>
         <artifactId>kafka-streams</artifactId>
-        <version>4.3.0</version>
+        <version>4.4.0</version>
     </dependency>
     <dependency>
         <groupId>org.apache.kafka</groupId>
         <artifactId>kafka-clients</artifactId>
-        <version>4.3.0</version>
+        <version>4.4.0</version>
     </dependency>
         <dependency>
         <groupId>org.apache.kafka</groupId>
         <artifactId>kafka-streams-scala_2.13</artifactId>
-        <version>4.3.0</version>
+        <version>4.4.0</version>
     </dependency>
 
 # Using Kafka Streams within your application code
diff --git a/docs/streams/quickstart.md b/docs/streams/quickstart.md
index 4010867e886..dfb136f27c9 100644
--- a/docs/streams/quickstart.md
+++ b/docs/streams/quickstart.md
@@ -32,7 +32,7 @@ This tutorial assumes you are starting fresh and have no existing Kafka data. Ho
 
 Kafka Streams is a client library for building mission-critical real-time applications and microservices, where the input and/or output data is stored in Kafka clusters. Kafka Streams combines the simplicity of writing and deploying standard Java and Scala applications on the client side with the benefits of Kafka's server-side cluster technology to make these applications highly scalable, elastic, fault-tolerant, distributed, and much more. 
 
-This quickstart example will demonstrate how to run a streaming application coded in this library. Here is the gist of the `[WordCountDemo](https://github.com/apache/kafka/blob/4.3/streams/examples/src/main/java/org/apache/kafka/streams/examples/wordcount/WordCountDemo.java)` example code. 
+This quickstart example will demonstrate how to run a streaming application coded in this library. Here is the gist of the `[WordCountDemo](https://github.com/apache/kafka/blob/4.4/streams/examples/src/main/java/org/apache/kafka/streams/examples/wordcount/WordCountDemo.java)` example code. 
     
     
     // Serializers/deserializers (serde) for String and Long types
@@ -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.3.0/kafka_2.13-4.3.0.tgz "Kafka downloads") the 4.3.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.4.0/kafka_2.13-4.4.0.tgz "Kafka downloads") the 4.4.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: 
     
     
-    $ tar -xzf kafka_2.13-4.3.0.tgz
-    $ cd kafka_2.13-4.3.0
+    $ tar -xzf kafka_2.13-4.4.0.tgz
+    $ cd kafka_2.13-4.4.0
 
 ### Step 2: Start the Kafka server
 
diff --git a/docs/streams/tutorial.md b/docs/streams/tutorial.md
index 067aaae896f..2ef0082ad73 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.3.0 \
+    -DarchetypeVersion=4.4.0 \
     -DgroupId=streams.examples \
     -DartifactId=streams-quickstart \
     -Dversion=0.1 \
diff --git a/docs/streams/upgrade-guide.md b/docs/streams/upgrade-guide.md
index 4db53a7f570..80f92f9d835 100644
--- a/docs/streams/upgrade-guide.md
+++ b/docs/streams/upgrade-guide.md
@@ -599,7 +599,7 @@ The following table shows which versions of the Kafka Streams API are compatible
 <tr>
 <th>Kafka Streams API (rows)</th>
 <th>2.4.x - 4.0.x</th>
-<th>4.1.x - 4.3.x</th>
+<th>4.1.x - 4.4.x</th>
 </tr>
 <tr>
 <th>2.4.x - 2.5.x</th>
@@ -607,7 +607,7 @@ The following table shows which versions of the Kafka Streams API are compatible
 <td>compatible</td>
 </tr>
 <tr>
-<th>2.6.x - 4.3.x</th>
+<th>2.6.x - 4.4.x</th>
 <td>compatible; enabling exactly-once v2 requires broker version 2.5.x or higher</td>
 <td>compatible</td>
 </tr>