diff --git a/.changeset/graphql-delete-userdetails-migration.md b/.changeset/graphql-delete-userdetails-migration.md
deleted file mode 100644
index 906441ee..00000000
--- a/.changeset/graphql-delete-userdetails-migration.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-'graphql-mcp-server': patch
----
-
-Add a `deleted_classes: ["UserDetails"]` Durable Object migration to the graphql server.
-
-\#384 removed the `UserDetails` Durable Object (and its bindings) from every server, and added the
-required delete-class migration to the two servers that *own* the class (`workers-observability`,
-`workers-builds`). The graphql worker's already-deployed version still depends on `UserDetails`, so
-`wrangler deploy` rejected the new version with `code: 10064` ("New version of script does not export
-class 'UserDetails' which is depended on by existing Durable Objects"), which aborted the staging and
-production deploys. Adding the delete-class migration lets graphql deploy and releases the binding that
-was blocking `workers-observability` from applying its own `deleted_classes` migration (`code: 10061`).
-
-Validated on staging: graphql + observability deploy cleanly and the staging `UserDetails` namespace is
-removed.
diff --git a/apps/graphql/CHANGELOG.md b/apps/graphql/CHANGELOG.md
index eaad3917..27a31b11 100644
--- a/apps/graphql/CHANGELOG.md
+++ b/apps/graphql/CHANGELOG.md
@@ -1,5 +1,22 @@
 # graphql-mcp-server
 
+## 0.2.1
+
+### Patch Changes
+
+- af70c87: Add a `deleted_classes: ["UserDetails"]` Durable Object migration to the graphql server.
+
+  \#384 removed the `UserDetails` Durable Object (and its bindings) from every server, and added the
+  required delete-class migration to the two servers that _own_ the class (`workers-observability`,
+  `workers-builds`). The graphql worker's already-deployed version still depends on `UserDetails`, so
+  `wrangler deploy` rejected the new version with `code: 10064` ("New version of script does not export
+  class 'UserDetails' which is depended on by existing Durable Objects"), which aborted the staging and
+  production deploys. Adding the delete-class migration lets graphql deploy and releases the binding that
+  was blocking `workers-observability` from applying its own `deleted_classes` migration (`code: 10061`).
+
+  Validated on staging: graphql + observability deploy cleanly and the staging `UserDetails` namespace is
+  removed.
+
 ## 0.2.0
 
 ### Minor Changes
diff --git a/apps/graphql/package.json b/apps/graphql/package.json
index 245cb84f..c2a3effb 100644
--- a/apps/graphql/package.json
+++ b/apps/graphql/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "graphql-mcp-server",
-	"version": "0.2.0",
+	"version": "0.2.1",
 	"private": true,
 	"scripts": {
 		"check:lint": "run-eslint-workers",