Version Packages (#447)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: workers-frameworks

.changeset/spicy-seas-appear.md

@@ -1,5 +1,26 @@
 # @opennextjs/cloudflare
 
+## 0.5.10
+
+### Patch Changes
+
+- [#445](https://github.com/opennextjs/opennextjs-cloudflare/pull/445) [`6a389fe`](https://github.com/opennextjs/opennextjs-cloudflare/commit/6a389fe54b360e542e4db0266e29f0e818176651) Thanks [@james-elicx](https://github.com/james-elicx)! - fix: deployed worker unable to invoke itself in memory queue
+
+  In deployments, Cloudflare Workers are unable to invoke workers on the same account via fetch, and the recommended way to call a worker is to use a service binding. This change switches to use service bindings for the memory queue to avoid issues with worker-to-worker subrequests.
+
+  To continue using the memory queue, add a service binding to your wrangler config for the binding `NEXT_CACHE_REVALIDATION_WORKER`.
+
+  ```json
+  {
+    "services": [
+      {
+        "binding": "NEXT_CACHE_REVALIDATION_WORKER",
+        "service": "<WORKER_NAME>"
+      }
+    ]
+  }
+  ```
+
 ## 0.5.9
 
 ### Patch Changes

packages/cloudflare/CHANGELOG.md

@@ -1,7 +1,7 @@
 {
   "name": "@opennextjs/cloudflare",
   "description": "Cloudflare builder for next apps",
-  "version": "0.5.9",
+  "version": "0.5.10",
   "type": "module",
   "scripts": {
     "clean": "rimraf dist",