diff --git a/vuepress/docs/docs/README.md b/vuepress/docs/docs/README.md
index a9797f3..1afe410 100644
--- a/vuepress/docs/docs/README.md
+++ b/vuepress/docs/docs/README.md
@@ -79,8 +79,8 @@ The first thing we need to do is starting the Shard Manager. This component is a
 To make it simpler and run our example without 3rd parties, we're going to run a simple `PodsHealth` implementation that just pings a pod to see if it's alive, and in-memory `Storage`.
 We need a proper messaging protocol to communicate with pods, so we're going to use `shardcake-protocol-grpc`.
 ```
-libraryDependencies += "com.devsisters" %% "shardcake-manager"       % "2.4.1"
-libraryDependencies += "com.devsisters" %% "shardcake-protocol-grpc" % "2.4.1"
+libraryDependencies += "com.devsisters" %% "shardcake-manager"       % "2.4.2"
+libraryDependencies += "com.devsisters" %% "shardcake-protocol-grpc" % "2.4.2"
 ```
 The Shard Manager exposes a small GraphQL API, which means we need to start a small webserver. This can be done by calling `Server.run` and providing all the required dependencies.
 ```scala
@@ -107,8 +107,8 @@ We now need to define our **entity behavior**: what kind of messages can our ent
 
 First, we need the following dependencies:
 ```
-libraryDependencies += "com.devsisters" %% "shardcake-entities"      % "2.4.1"
-libraryDependencies += "com.devsisters" %% "shardcake-protocol-grpc" % "2.4.1"
+libraryDependencies += "com.devsisters" %% "shardcake-entities"      % "2.4.2"
+libraryDependencies += "com.devsisters" %% "shardcake-protocol-grpc" % "2.4.2"
 ```
 
 Let's start with defining the messages our entities can receive. We will have 2: one for joining a guild and one for leaving.
diff --git a/vuepress/docs/docs/customization.md b/vuepress/docs/docs/customization.md
index a7fc598..a628670 100644
--- a/vuepress/docs/docs/customization.md
+++ b/vuepress/docs/docs/customization.md
@@ -28,7 +28,7 @@ For testing, you can use the `Storage.memory` layer that keeps data in memory.
 
 Shardcake provides an implementation of `Storage` using Redis with the Redis4cats library (there's also an alternative using Redisson). To use it, add the following dependency:
 ```scala
-libraryDependencies += "com.devsisters" %% "shardcake-storage-redis" % "2.4.1"
+libraryDependencies += "com.devsisters" %% "shardcake-storage-redis" % "2.4.2"
 ```
 You can then simply use the `StorageRedis.live` layer.
 
@@ -85,7 +85,7 @@ For testing, you can use the `Pods.noop` layer that does nothing.
 
 Shardcake provides an implementation of `Pods` using the gRPC protocol. To use it, add the following dependency:
 ```scala
-libraryDependencies += "com.devsisters" %% "shardcake-protocol-grpc" % "2.4.1"
+libraryDependencies += "com.devsisters" %% "shardcake-protocol-grpc" % "2.4.2"
 ```
 You can then simply use the `GrpcPods.live` layer.
 
@@ -106,7 +106,7 @@ For testing, you can use the `Serialization.javaSerialization` layer that uses J
 
 Shardcake provides an implementation of `Serialization` using the [Kryo](https://github.com/EsotericSoftware/kryo) binary serialization library. To use it, add the following dependency:
 ```scala
-libraryDependencies += "com.devsisters" %% "shardcake-serialization-kryo" % "2.4.1"
+libraryDependencies += "com.devsisters" %% "shardcake-serialization-kryo" % "2.4.2"
 ```
 You can then simply use the `KryoSerialization.live` layer.
 
@@ -131,7 +131,7 @@ For testing, you can use the `PodsHealth.noop` layer that always returns true, o
 
 Shardcake provides an implementation of `PodsHealth` using the [Kubernetes](https://kubernetes.io) API. To use it, add the following dependency:
 ```scala
-libraryDependencies += "com.devsisters" %% "shardcake-health-k8s" % "2.4.1"
+libraryDependencies += "com.devsisters" %% "shardcake-health-k8s" % "2.4.2"
 ```
 You can then simply use the `K8sPodsHealth.live` layer. This is requiring a `Pods` layer that comes from [zio-k8s](https://coralogix.github.io/zio-k8s/docs/overview/overview_gettingstarted).