[wrangler] deploy rejects already-applied migration history: Cannot apply deleted_classes migration

## Observed symptom `wrangler deploy` rejects an already-applied migration history: "Cannot apply deleted_classes migration to non-existent class" (regression in 4.131.0) ### Which Cloudflare product(s) does this pertain to? Wrangler, Durable Objects ### What versions & operating system are you using? wrangler 4.135.0 fails (4.128.0 works). macOS (arm64), Node 26.9.0, npm 11.19.1. ### Describe the Bug Since the Durable Object-managed Containers work, `wrangler deploy` and `wrangler versions upload` replay the whole `[[migrations]]` array locally, from an empty state, before uploading. They do this even when the Worker has no `containers` configured. If the recorded history deletes a class that no earlier tag in the file creates, the deploy stops: ``` ✘ [ERROR] Cannot apply deleted_classes migration to non-existent class LegacyRoom ``` The API accepts that history. Wrangler only sends the migrations after the script's current `migration_tag` (`getMigr ## Literal error text ``` Cannot apply deleted_classes migration ``` ## Environment GitHub issue cloudflare/workers-sdk #15741; state=open ## Trigger / context ### Which Cloudflare product(s) does this pertain to? Wrangler, Durable Objects ### What versions & operating system are you using? wrangler 4.135.0 fails (4.128.0 works). macOS (arm64), Node 26.9.0, npm 11.19.1. ### Describe the Bug Since the Durable Object-managed Containers work, `wrangler deploy` and `wrangler versions upload` replay the whole `[[migrations]]` array locally, from an empty state, before uploading. They do this even when the Worker has no `containers` configured. If the recorded history deletes a class that no earlier tag in the file creates, the deploy stops: ``` ✘ [ERROR] Cannot apply deleted_classes migration to non-existent class LegacyRoom ``` The API accepts that history. Wrangler only sends the migrations after the script's current `migration_tag` (`getMigrationsToUpload` → `slice(foundIndex + 1)`), so tags that were already applied are never evaluated again on the server. Our production Worker has applied every tag in its file. One tag deletes a class that the server had but that no earlier tag in the file creates. The same config deploys with 4.128.0 and cannot deploy with 4.135.0. The history can't be "fixed" without adding a tag that was never applied. From the source: - `deployWorker` (`packages/deploy-helpers/src/deploy/deploy.ts`) calls `prepareDurableObjectContainerApplications` for every Worker. Only `--containers-rollout=none` skips it. - That calls `validateDurableObjectContainerApplications`, which calls `getDurableObjectClassNam ## Source evidence - https://github.com/cloudflare/workers-sdk/issues/15741 (2026-09-21T07:11:54Z) — GitHub issue #15741 ## Freshness - classification: FRESH_14D - retrieved_at: 2026-10-02T09:43:35.178343Z - scout_id: C1f727d2b95 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome.