diff --git a/src/content/docs/workers/versions-and-deployments/gradual-deployments/index.mdx b/src/content/docs/workers/versions-and-deployments/gradual-deployments/index.mdx index 6b0cad7a70b..d48e64a91e9 100644 --- a/src/content/docs/workers/versions-and-deployments/gradual-deployments/index.mdx +++ b/src/content/docs/workers/versions-and-deployments/gradual-deployments/index.mdx @@ -109,6 +109,8 @@ You can use [version overrides](/workers/versions-and-deployments/version-overri Gradual deployments work differently for [Durable Objects](/durable-objects/) because only one version of each Durable Object can run at a time. Refer to [Gradual Deployments with Durable Objects](/workers/versions-and-deployments/gradual-deployments/with-durable-objects/) for details on version assignment, guarantees, and migrations. +A version upload that includes a Durable Object class lifecycle change is rejected with error 10211. Apply the migration with a non-versioned deploy. Refer to [With Durable Objects](/workers/versions-and-deployments/gradual-deployments/with-durable-objects/#durable-object-class-lifecycle-changes) for details. + ## Observability When using gradual deployments, you may want to attribute Workers invocations to a specific version in order to get visibility into the impact of deploying new versions. diff --git a/src/content/docs/workers/versions-and-deployments/gradual-deployments/with-durable-objects.mdx b/src/content/docs/workers/versions-and-deployments/gradual-deployments/with-durable-objects.mdx index e168d2489fa..0f20f502b4d 100644 --- a/src/content/docs/workers/versions-and-deployments/gradual-deployments/with-durable-objects.mdx +++ b/src/content/docs/workers/versions-and-deployments/gradual-deployments/with-durable-objects.mdx @@ -45,7 +45,7 @@ You should ensure that API changes between your Durable Object and its Worker ar Versions of Worker bundles that change Durable Object class lifecycle cannot be uploaded. This applies to both the declarative [`exports`](/durable-objects/reference/durable-objects-migrations/) field and the legacy [`migrations`](/durable-objects/reference/durable-object-class-migrations-legacy/) array. This is because Durable Object lifecycle changes are atomic operations. Once a lifecycle change is deployed, rollbacks cannot take place to any version prior to the one that included the change. -Durable Object lifecycle changes can be deployed with the following command: +A `wrangler versions upload` that includes a Durable Object class lifecycle change is rejected with error 10211. Apply the migration with a non-versioned deploy: