{{ message }}
Repository navigation
Clarify Workers version upload preservation semantics for omitted metadata #34188
Description
Existing documentation URL(s)
- https://developers.cloudflare.com/api/resources/workers/subresources/scripts/subresources/versions/methods/create/
- https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/
- https://developers.cloudflare.com/workers/versions-and-deployments/
What changes are you suggesting?
Please clarify the documented server behavior of POST /accounts/{id}/workers/scripts/{name}/versions when the following metadata is omitted:
- migrations / migration_tag
- limits.cpu_ms
- tail_consumers
Are existing settings preserved, reset, or resolved from another version? If inherited, is the source the latest uploaded version or the currently deployed version?
The multipart metadata documentation excludes migrations and tail_consumers from version uploads, while Wrangler may serialize configured tail consumers. Please clarify the authoritative behavior.
Also, is a version upload safe to retry after a network timeout or lost response? Is there a documented idempotency guarantee?
We request documentation clarification only. No production testing is proposed.
Additional information
No response
Activity