cloudflare/workers-sdk wrangler@4.32.0 on GitHub

#10354 da40571 Thanks @edmundhung! - Enable cross-process communication for wrangler dev with multiple config files
Workers running in separate wrangler dev sessions can now communicate with each other regardless of whether you are running with single or multiple config files.
Check out the Developing with multiple Workers guide to learn more about the different approaches and when to use each one.
#10012 4728c68 Thanks @penalosa! - Support unsafe dynamic worker loading bindings

#10245 d304055 Thanks @edmundhung! - Migrate wrangler dev to use Miniflare dev registry implementation
Updated wrangler dev to use a shared dev registry implementation that now powers both the Cloudflare Vite plugin and Wrangler. This internal refactoring has no user-facing changes but consolidates registry logic for better consistency across tools.
#10407 f534c0d Thanks @emily-shen! - default containers.rollout_active_grace_period to 0
#10425 0a96e69 Thanks @dario-piotrowicz! - Fix debugging logs not including headers for CF API requests and responses
Fix the fact that wrangler, when run with the WRANGLER_LOG=DEBUG and WRANGLER_LOG_SANITIZE=false environment variables, displays {} instead of the actual headers for requests and responses for CF API fetches
#10337 f9f7519 Thanks @emily-shen! - containers: rollout_step_percentage now also accepts an array of numbers. Previously it accepted a single number, and each rollout step would target the same percentage of instances. Now users can customise percentages for each step.
rollout_step_percentage also now defaults to [10,100] (previously 25), which should make rollouts progress slightly faster.
You can also use wrangler deploy --containers-rollout=immediate to override rollout settings in Wrangler configuration and update all instances in one step. Note this doesn't override rollout_active_grace_period if configured.
Updated dependencies [4728c68]:
- miniflare@4.20250816.1