diff --git a/.changeset/fix-webui-pin-detection.md b/.changeset/fix-webui-pin-detection.md
deleted file mode 100644
index 9d30c99..0000000
--- a/.changeset/fix-webui-pin-detection.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@1001/ipfs-server": patch
----
-
-Fix WebUI pinning broken by the Kubo 0.41 upgrade
-
-Since Kubo 0.41, `/webui` no longer redirects straight to `/ipfs/<cid>` but to `/webui/`, which returns a 503 when the WebUI content is not local (we run with `Gateway.NoFetch=true`). The init script's wget-based redirect parsing therefore found no CID and the WebUI was never pinned, leaving `admin.ipfs.1001.digital/webui` broken after deploys. The script now issues a raw request via `nc`, extracting the CID from the redirect headers or the 503 error body, whichever is present.
diff --git a/.changeset/upgrade-kubo-0-41-0.md b/.changeset/upgrade-kubo-0-41-0.md
deleted file mode 100644
index fc57f48..0000000
--- a/.changeset/upgrade-kubo-0-41-0.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@1001/ipfs-server": minor
----
-
-Upgrade Kubo to v0.41.0
-
-Bumps the base image from `ipfs/kubo:v0.40.0` to `v0.41.0`. Notable upstream changes: the provider keystore moves to a dedicated datastore under `$IPFS_PATH/provider-keystore/` (migrated automatically on first startup), a fixed DHT data race that previously caused random daemon crashes, faster imports for selective `Provide.Strategy` users, and WebUI v4.12.0. No changes to our config or init scripts are required.
diff --git a/.changeset/upgrade-kubo-0-42-0.md b/.changeset/upgrade-kubo-0-42-0.md
deleted file mode 100644
index 955d93c..0000000
--- a/.changeset/upgrade-kubo-0-42-0.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-"@1001/ipfs-server": minor
----
-
-Upgrade Kubo from v0.41.0 to v0.42.0
-
-This picks up the upstream fix for pin operations hanging during reprovide
-cycles under selective `Provide.Strategy` modes, bounded daemon shutdowns, and
-the stronger `ipfs diag healthy` container health check. The deployment keeps
-Kubo's new anonymous telemetry disabled by default and pins Kamal 2.10.1 for
-compatibility with the production proxy.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7eaa54b..f2fafcf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,27 @@
 # @1001/ipfs-server
 
+## 1.5.0
+
+### Minor Changes
+
+- [`45e930f`](https://github.com/1001-digital/ipfs.server/commit/45e930f3198ed408ea542a5c548bbccb9cadbf84) Thanks [@jwahdatehagh](https://github.com/jwahdatehagh)! - Upgrade Kubo to v0.41.0
+
+  Bumps the base image from `ipfs/kubo:v0.40.0` to `v0.41.0`. Notable upstream changes: the provider keystore moves to a dedicated datastore under `$IPFS_PATH/provider-keystore/` (migrated automatically on first startup), a fixed DHT data race that previously caused random daemon crashes, faster imports for selective `Provide.Strategy` users, and WebUI v4.12.0. No changes to our config or init scripts are required.
+
+- [`8e96079`](https://github.com/1001-digital/ipfs.server/commit/8e96079b0c5a9927e1c0456dc99b9bd89e745649) Thanks [@jwahdatehagh](https://github.com/jwahdatehagh)! - Upgrade Kubo from v0.41.0 to v0.42.0
+
+  This picks up the upstream fix for pin operations hanging during reprovide
+  cycles under selective `Provide.Strategy` modes, bounded daemon shutdowns, and
+  the stronger `ipfs diag healthy` container health check. The deployment keeps
+  Kubo's new anonymous telemetry disabled by default and pins Kamal 2.10.1 for
+  compatibility with the production proxy.
+
+### Patch Changes
+
+- [`7ea621c`](https://github.com/1001-digital/ipfs.server/commit/7ea621ca22ca0f61f3b64466b7b7543f55a6b9fd) Thanks [@jwahdatehagh](https://github.com/jwahdatehagh)! - Fix WebUI pinning broken by the Kubo 0.41 upgrade
+
+  Since Kubo 0.41, `/webui` no longer redirects straight to `/ipfs/<cid>` but to `/webui/`, which returns a 503 when the WebUI content is not local (we run with `Gateway.NoFetch=true`). The init script's wget-based redirect parsing therefore found no CID and the WebUI was never pinned, leaving `admin.ipfs.1001.digital/webui` broken after deploys. The script now issues a raw request via `nc`, extracting the CID from the redirect headers or the 503 error body, whichever is present.
+
 ## 1.4.1
 
 ### Patch Changes
diff --git a/package.json b/package.json
index eb64a51..f936429 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@1001/ipfs-server",
-  "version": "1.4.1",
+  "version": "1.5.0",
   "private": true,
   "type": "module",
   "scripts": {