diff --git a/.changesets/exp_geal_entity_cache_documentation.md b/.changesets/exp_geal_entity_cache_documentation.md
deleted file mode 100644
index 546cc6cd40..0000000000
--- a/.changesets/exp_geal_entity_cache_documentation.md
+++ /dev/null
@@ -1,27 +0,0 @@
-### Entity cache preview ([PR #5574](https://github.com/apollographql/router/pull/5574))
-
-#### Support private information caching
-
-The router supports a new `private_id` option that enables separate, private cache entries to be allocated per user for authenticated requests.
-
-When a subgraph returns a `Cache-Control: private` header, the response data shouldn't be cached and shared among users. However, since the router supports request authentication, it can use it to allocate separate cache entries per users. 
-
-To enable this, configure the `private_id` to be the name of a key in the request context that contains the data that's used to differentiate users. This option must be paired with a coprocessor or Rhai script to set the value in context.
-
-Example configuration:
-
-```yaml title="router.yaml"
-# Enable entity caching globally
-preview_entity_cache:
-  enabled: true
-  subgraph:
-    all:
-      enabled: true
-      accounts:
-        private_id: "user_id"
-```
-
-
-To learn more about configuring and customizing private information caching, go to [Private information caching](https://www.apollographql.com/docs/router/configuration/entity-caching/#private-information-caching) docs.
- 
-By [@Geal](https://github.com/Geal) in https://github.com/apollographql/router/pull/5574
\ No newline at end of file
diff --git a/.changesets/feat_geal_return_response_with_errors.md b/.changesets/feat_geal_return_response_with_errors.md
deleted file mode 100644
index 0697a0ced8..0000000000
--- a/.changesets/feat_geal_return_response_with_errors.md
+++ /dev/null
@@ -1,5 +0,0 @@
-### Entity cache returns cached entities with errors ([PR #5776](https://github.com/apollographql/router/pull/5776))
-
-When requesting entities from a subgraph where some entities are cached but the subgraph is unavailable (for example, due to a network issue), the router now returns a response with the cached entities retrieved, the unavailable entities nullified, and an error pointing at the paths of the unavailable entities.
-
-By [@Geal](https://github.com/Geal) in https://github.com/apollographql/router/pull/5776
\ No newline at end of file
diff --git a/.changesets/fix_geal_test_private_info_caching.md b/.changesets/fix_geal_test_private_info_caching.md
deleted file mode 100644
index 94c394758c..0000000000
--- a/.changesets/fix_geal_test_private_info_caching.md
+++ /dev/null
@@ -1,5 +0,0 @@
-### Fix private information caching in entity cache ([PR #5599](https://github.com/apollographql/router/pull/5599))
-
-The router previously had an issue where private data could be stored at the wrong key, resulting in the data not appearing to be cached. This has been fixed by updating the cache key with the private data. 
-
-By [@Geal](https://github.com/Geal) in https://github.com/apollographql/router/pull/5599
\ No newline at end of file