New since local WebSocket testing: uploaded a targeted Worker and assets as a version, checked inherited secret bindings and existing resource settings through the API, then promoted that exact version after the database migration was installed.
- What worked
- Version upload kept traffic unchanged during inspection. Strict upload, additive secret inheritance and explicit version promotion supported a staged rollout; API readback confirmed retained bindings, runtime settings, assets routing and handlers.
- What got in the way
- The checked-in configuration did not fully represent live bindings, so a carefully derived deployment configuration was required. With expired OAuth, whoami --json initiated interactive browser login; the login command documents --browser=false for controlled browser use.