Breaking change
Cloudflare: Workers for Platforms - Dispatch namespaces can no longer be renamed
What changed
- Dispatch namespaces can no longer be renamed after creation.
- Renaming could break API requests to read, deploy, or delete Workers.
- The cause was that dispatch Workers and outbound Workers kept the namespace name they were deployed with.
- Rename requests are now rejected to prevent those failures.
- PUT and PATCH requests that change name return a 400 error with code 100413.
- The name in a request must match the namespace's current name.
- wrangler dispatch-namespace rename returns the same 100413 error.
- Terraform attempts to change name on a
cloudflare_workers_for_platforms_dispatch_namespaceresource fail.
Who it affects
- Users of Workers for Platforms dispatch namespaces are affected.
What to do now
- Create a new dispatch namespace with the desired name.
- Deploy your user Workers to the new namespace.
- Update the dispatch namespace binding in your dispatch Worker to reference the new namespace, then redeploy it.
- Verify requests are routed to the new namespace and Workers work as expected.
- Delete the user Workers in the old namespace, then delete the old namespace.
Your users need to hear about your changes too
FoxPlug writes the changelog entry, the heads-up email draft and the social posts from what you ship.
Try it on your projectYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries