Skip to content

Commit 7adb5d7

Browse files
Apply suggestions from code review
Co-authored-by: Brendan Irvine-Broque <[email protected]>
1 parent d1c0fba commit 7adb5d7

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

src/content/changelog/workers/2025-09-03-new-workers-api.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ resource "cloudflare_worker" "my_worker" {
105105
# resource "cloudflare_workers_deployment" "my_worker_deployment" {}
106106
```
107107

108-
### Predictable settings
108+
### No more confusing `/settings` API endpoints
109109
Configuration now has an obvious home. Worker settings persist across all versions of the Worker, and Version settings are specific to a code snapshot.
110110

111111
```sh
@@ -128,7 +128,7 @@ POST /workers/workers/{id}/versions
128128
}
129129
```
130130

131-
### Dual addressing for stability and convenience
131+
### `/workers` API endpoints now support UUIDs (in addition to names)
132132

133133
The `/workers/workers/` path now supports addressing a Worker by both its immutable UUID and its mutable name.
134134

@@ -139,7 +139,7 @@ GET /workers/workers/payment-service # Name (convenient for hum
139139
```
140140
This dual approach means:
141141
- Developers can use readable names for debugging.
142-
- Automation can rely on stable UUIDs to prevent errors.
142+
- Automation can rely on stable UUIDs to prevent errors when Workers are renamed
143143
- Terraform can rename Workers without destroying and recreating them.
144144

145145

@@ -150,5 +150,5 @@ This dual approach means:
150150

151151
## Technical notes
152152

153-
- Current APIs remain operational during beta, and any deprecation notice will come with a defined support period.
153+
- You can still use the preexisting Workers REST API, and it remains fully supported.
154154
- Legacy Terraform resources and SDK methods will be supported until the next major version.

src/content/docs/workers/configuration/multipart-upload-metadata.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ import { Type, MetaInfo } from "~/components";
77

88
:::note
99

10-
There is a new API for uploading Workers. See [here](/workers/platform/infrastructure-as-code#cloudflare-rest-api) for more information.
10+
There is a new API for uploading Workers. Refer to [these docs](/workers/platform/infrastructure-as-code#cloudflare-rest-api) for more information.
1111
:::
1212

1313
If you're using the [Workers Script Upload API](/api/resources/workers/subresources/scripts/methods/update/) or [Version Upload API](/api/resources/workers/subresources/scripts/subresources/versions/methods/create/) directly, `multipart/form-data` uploads require you to specify a `metadata` part. This metadata defines the Worker's configuration in JSON format, analogue to the [wrangler.toml file](/workers/wrangler/configuration/).

0 commit comments

Comments
 (0)