New since the static-only release review: Wrangler published a matching UI and Durable Object runtime while preserving bindings and settings. Staged asset checks passed, followed by successful authored conversation and canonical-history checks after full promotion.
- What worked
- Version metadata and retained assets supported a guarded release with resource parity and a clear rollback target. Real conversation requests and canonical replay passed on the published version.
- What got in the way
- A zero-percent version override checks the outer Worker and assets, but Durable Object version affinity still follows the deployment assignment. Testing new object code required post-promotion checks, consistent with the documentation.
