Bump wrangler from 4.31.0 to 4.32.0 in the general group

[dependabot]

Bumps the general group with 1 update: wrangler.

Updates wrangler from 4.31.0 to 4.32.0

Release notes

Sourced from wrangler's releases.

wrangler@4.32.0

Minor Changes

• #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

Patch Changes

• #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

Changelog

Sourced from wrangler's changelog.

4.32.0

Minor Changes

• #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

Patch Changes

• #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

Commits

• e329195 Version Packages (#10406)
• 0a96e69 Fix debugging logs not including headers for CF API requests and responses (#...
• 2fd888f increase start-worker-auth-opts timeouts to reduce wrangler e2e ci flakes (#1...
• f9f7519 let rollout_step_percentage also accept an array of numbers (#10337)
• da40571 feat: enable cross-process communication for wrangler dev with multiple confi...
• 3a65e11 hide and mark service.environments as deprecated (#10396)
• 4728c68 Basic support for worker loader bindings (#10012)
• f534c0d set default for rollout_active_grace_period (#10407)
• d304055 refactor: migrate wrangler dev to use Miniflare dev registry (#10245)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions