diff --git a/CHANGELOG.md b/CHANGELOG.md
index 71543f97..91c90b82 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added 
 
+### Changed
+
+### Deprecated
+
+### Removed
+
+### Fixed
+
+### Security
+
+## v0.0.28
+
+### Added 
+
 - [#576](https://github.com/spegel-org/spegel/pull/576) Add support for range requests for blobs.
 - [#621](https://github.com/spegel-org/spegel/pull/621) Added Mermaid diagrams documentation to help explain Spegel's inner workings.
 - [#629](https://github.com/spegel-org/spegel/pull/629) Document how to use multiple Spegel deployments in the same cluster.
@@ -18,17 +32,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - [#608](https://github.com/spegel-org/spegel/pull/608) Use custom proxy transport and increase idle connections per host.
 
-### Deprecated
-
-### Removed
-
 ### Fixed
 
 - [#651](https://github.com/spegel-org/spegel/pull/651) Fix Containerd CRI config verification.
 - [#660](https://github.com/spegel-org/spegel/pull/660) Add accept ranges header to blob HEAD request.
 
-### Security
-
 ## v0.0.27
 
 ### Fixed
diff --git a/README.md b/README.md
index 4e74e768..fbc1b5c6 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ This has the benefit of reducing workload startup times and egress traffic as im
 Before installing Spegel check the [compatibility guide](./docs/COMPATIBILITY.md) to make sure that it will work with your specific Kubernetes flavor. If everything checks out, the easiest method to deploy Spegel is with Helm.
 
 ```shell
-helm upgrade --create-namespace --namespace spegel --install --version v0.0.27 spegel oci://ghcr.io/spegel-org/helm-charts/spegel
+helm upgrade --create-namespace --namespace spegel --install --version v0.0.28 spegel oci://ghcr.io/spegel-org/helm-charts/spegel
 ```
 
 Refer to the [Helm Chart](./charts/spegel) for detailed configuration documentation.
diff --git a/charts/spegel/README.md b/charts/spegel/README.md
index 73ffb745..b7e56249 100644
--- a/charts/spegel/README.md
+++ b/charts/spegel/README.md
@@ -11,7 +11,7 @@ Make sure that you have read the [compatibility guide](../../docs/COMPATIBILITY.
 Delpoy Spegel with the Helm CLI.
 
 ```sh
-helm upgrade --create-namespace --namespace spegel --install --version v0.0.27 spegel oci://ghcr.io/spegel-org/helm-charts/spegel
+helm upgrade --create-namespace --namespace spegel --install --version v0.0.28 spegel oci://ghcr.io/spegel-org/helm-charts/spegel
 ```
 
 ### Flux
@@ -44,7 +44,7 @@ spec:
   chart:
     spec:
       chart: spegel
-      version: "v0.0.27"
+      version: "v0.0.28"
       interval: 5m
       sourceRef:
         kind: HelmRepository
diff --git a/charts/spegel/README.md.gotmpl b/charts/spegel/README.md.gotmpl
index c745cb22..90c11e4a 100644
--- a/charts/spegel/README.md.gotmpl
+++ b/charts/spegel/README.md.gotmpl
@@ -12,7 +12,7 @@ Make sure that you have read the [compatibility guide](../../docs/COMPATIBILITY.
 Delpoy Spegel with the Helm CLI.
 
 ```sh
-helm upgrade --create-namespace --namespace spegel --install --version v0.0.27 spegel oci://ghcr.io/spegel-org/helm-charts/spegel
+helm upgrade --create-namespace --namespace spegel --install --version v0.0.28 spegel oci://ghcr.io/spegel-org/helm-charts/spegel
 ```
 
 ### Flux
@@ -45,7 +45,7 @@ spec:
   chart:
     spec:
       chart: spegel
-      version: "v0.0.27"
+      version: "v0.0.28"
       interval: 5m
       sourceRef:
         kind: HelmRepository
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 01ee9491..0a169f5b 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -140,6 +140,6 @@ The best solution to address this problem currently is to use [nidhogg](https://
 In certain situations deploying multiple separate Spegel clusters is beneficial. For example when a Kubernetes cluster spans multiple regions, it may be beneficial to limit nodes too only pull images from within the same region. Spegel can be deployed multiple times by simply using different names for each Helm deployment and setting a unique node selector. It is important to note that the node port service needs a unique port per deployment. Spegel will then only deploy on nodes with the matching labels and elect a unique leader for each deployment of Spegel. As the two Spegel clusters will never communicate they will not be able to discover layers outside of their own region, limiting requests to their specific region.
 
 ```bash
-helm upgrade --create-namespace --namespace spegel --install --version v0.0.27 spegel-one oci://ghcr.io/spegel-org/helm-charts/spegel --set "nodeSelector.group=one" --set "service.registry.nodePort=30021"
-helm upgrade --create-namespace --namespace spegel --install --version v0.0.27 spegel-two oci://ghcr.io/spegel-org/helm-charts/spegel --set "nodeSelector.group=two" --set "service.registry.nodePort=30022"
+helm upgrade --create-namespace --namespace spegel --install --version ${SPEGEL_VERSION} spegel-one oci://ghcr.io/spegel-org/helm-charts/spegel --set "nodeSelector.group=one" --set "service.registry.nodePort=30021"
+helm upgrade --create-namespace --namespace spegel --install --version ${SPEGEL_VERSION} spegel-two oci://ghcr.io/spegel-org/helm-charts/spegel --set "nodeSelector.group=two" --set "service.registry.nodePort=30022"
 ```