[Docs Site] Bump wrangler from 4.31.0 to 4.33.0

[dependabot]

Bumps wrangler from 4.31.0 to 4.33.0.

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #10414 e81c2cf Thanks @​penalosa! - Support automatically updating the user's config file with newly created resources

Patch Changes

• #10424 c4fd176 Thanks @​penalosa! - Remove the --experimental-json-config/-j flag, which is no longer required.

• #10432 19e2aab Thanks @​anonrig! - Remove "node:tls" polyfill

• #10424 c4fd176 Thanks @​penalosa! - Expose global flags from experimental_getWranglerCommands()

• Updated dependencies [19e2aab]:

  • @​cloudflare/unenv-preset@​2.6.3
  • [email protected]

[email protected]

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]:

  • [email protected]

Changelog

Sourced from wrangler's changelog.

4.33.0

Minor Changes

• #10414 e81c2cf Thanks @​penalosa! - Support automatically updating the user's config file with newly created resources

Patch Changes

• #10424 c4fd176 Thanks @​penalosa! - Remove the --experimental-json-config/-j flag, which is no longer required.

• #10432 19e2aab Thanks @​anonrig! - Remove "node:tls" polyfill

• #10424 c4fd176 Thanks @​penalosa! - Expose global flags from experimental_getWranglerCommands()

• Updated dependencies [19e2aab]:

  • @​cloudflare/unenv-preset@​2.6.3
  • [email protected]

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]:

  • [email protected]

Commits

• c4fde06 Version Packages (#10428)
• d696e0b Use explicit workerd dependency in Miniflare and Wrangler (#10464)
• 92ae391 make dns test more robust (#10461)
• 19e2aab remove node:tls polyfills (#10432)
• c4fd176 Expose global flags from experimental_getWranglerCommands() (#10424)
• e81c2cf Update config after creation commands (#10414)
• 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)
• Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.