chore(deps): update dependency wrangler to v4.33.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	4.28.0 -> 4.33.1

---

Release Notes

cloudflare/workers-sdk (wrangler)

v4.33.1

Compare Source

Patch Changes

• #​10427 85be2b6 Thanks @​dario-piotrowicz! - Simplify ENOENT debug logs for .env files

• Updated dependencies [76d9aa2, 452ad0b, 7c339ae]:

  • @​cloudflare/unenv-preset@​2.7.0
  • miniflare@​4.20250823.1

v4.33.0

Compare Source

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
  • miniflare@​4.20250823.0

v4.32.0

Compare Source

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]

v4.31.0

Compare Source

Minor Changes

• #​10314 9b09751 Thanks @​dario-piotrowicz! - Show possible local vs. dashboard diff information on deploys

  When re-deploying a Worker using wrangler deploy, if the configuration has been modified in the Cloudflare dashboard, the local configuration will overwrite the remote one. This can lead to unexpected results for users. To address this, currently wrangler deploy warns users about potential configuration overrides (without presenting them) and prompts them to confirm whether they want to proceed.

  The changes here improve the above flow in the following way:

  • If the local changes only add new configurations (without modifying or removing existing ones), the deployment proceeds automatically without warnings or prompts, as these changes are non-destructive and safe.
  • If the local changes modify or remove existing configurations, wrangler deploy now displays a git-like diff showing the differences between the dashboard and local configurations. This allows users to review and understand the impact of their changes before confirming the deployment.

• #​10334 cadf19a Thanks @​jonesphillip! - Added queues subscription command to Wrangler including create, update, delete, get, list

Patch Changes

• #​10374 20520fa Thanks @​edmundhung! - Simplify debug package resolution with nodejs_compat

  A patched version of debug was previously introduced that resolved the package to a custom implementation. However, this caused issues due to CJS/ESM interop problems. We now resolve the debug package to use the Node.js implementation instead.

• #​10249 875197a Thanks @​penalosa! - Support JSRPC for remote bindings. This unlocks:

  • JSRPC over Service Bindings
  • JSRPC over Dispatch Namespace Bindings
  • Email
  • Pipelines

• Updated dependencies [565c3a3, ddadb93, 20520fa, 875197a]:

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

v4.30.0

Compare Source

Minor Changes

• #​10341 76a6701 Thanks @​garvit-gupta! - feat: Add Wrangler command for Vectorize list-vectors operation

Patch Changes

• #​10217 979984b Thanks @​veggiedefender! - Increase the maxBuffer size for capnp uploads

• #​10356 80e964c Thanks @​WillTaylorDev! - fix: Update regex for valid branch name to remove 61 char length requirement, allowing for longer branch names to be specified for preview aliases.

• #​10289 a5a1426 Thanks @​emily-shen! - Cleanup container images created during local dev if no changes have been made.

  We now untag old images that were created by Wrangler/Vite if we find that the image content and configuration is unchanged, so that we don't keep accumulating image tags.

• #​10315 0c04da9 Thanks @​emily-shen! - Add rollout_active_grace_period option to containers configuration.

  This allows users to configure how long an active container should keep running for during a rollout, before the upgrade is applied.

• #​10321 b524a6f Thanks @​emily-shen! - print prettier errors during container deployment

• #​10253 eb32a3a Thanks @​emily-shen! - fix redeploying container apps when previous deploy failed or container (but not image) was deleted.

  Previously this failed with No changes detected but no previous image found as we assumed there would be a previous deployment when an image exists in the registry.

• #​9990 4288a61 Thanks @​penalosa! - Fix startup profiling when sourcemaps are enabled

• Updated dependencies [d54d8b7, ae0c806]:

  • [email protected]

v4.29.1

Compare Source

Patch Changes

• Updated dependencies [5020694]:
  • [email protected]

v4.29.0

Compare Source

Minor Changes

• #​10283 80960b9 Thanks @​WillTaylorDev! - Support long branch names in generation of branch aliases in WCI.

• #​10312 bd8223d Thanks @​devin-ai-integration! - Added --domain flag to wrangler deploy command for deploying to custom domains. Use --domain example.com to deploy directly to a custom domain without manually configuring routes.

• #​8318 8cf47f9 Thanks @​gnekich! - Introduce json output flag for wrangler pages deployment list

Patch Changes

• #​10232 e7cae16 Thanks @​emily-shen! - fix: validate wrangler containers delete ID to ensure a valid ID has been provided. Previously if you provided the container name (or any non-ID shaped string) you would get an auth error instead of a 404.

• #​10139 3b6ab8a Thanks @​dom96! - Removes mention of cf-requirements when Python Workers are enabled

• #​10259 c58a05c Thanks @​dario-piotrowicz! - Ensure that maybeStartOrUpdateRemoteProxySession considers the potential account_id from the user's wrangler config

  Currently if the user has an account_id in their wrangler config file, such id won't be taken into consideration for the remote proxy session, the changes here make sure that it is (note that the auth option of maybeStartOrUpdateRemoteProxySession, if provided, takes precedence over this id value).

  The changes here also fix the same issue for wrangler dev and getPlatformProxy (since they use maybeStartOrUpdateRemoteProxySession under the hook).

• #​10288 42aafa3 Thanks @​tgarg-cf! - Do not attempt to update queue producer settings when deploying a Worker with a queue binding

  Previously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set different producer settings on a shared queue.

• #​10242 70bd966 Thanks @​devin-ai-integration! - Add experimental API to expose Wrangler command tree structure for documentation generation

• #​10258 d391076 Thanks @​nikitassharma! - Add the option to allow all tiers when creating a container

• #​10248 422ae22 Thanks @​emily-shen! - fix: re-push container images on deploy even if the only change was to the Dockerfile

• #​10179 5d5ecd5 Thanks @​pombosilva! - Prevent defining multiple workflows with the same "name" property in the same wrangler file

• #​10232 e7cae16 Thanks @​emily-shen! - include containers API calls in output of WRANGLER_LOG=debug

• #​10243 d481901 Thanks @​devin-ai-integration! - Remove async_hooks polyfill - now uses native workerd implementation

  The async_hooks module is now provided natively by workerd, making the polyfill unnecessary. This improves performance and ensures better compatibility with Node.js async_hooks APIs.

• #​10060 9aad334 Thanks @​edmundhung! - refactor: switch getPlatformProxy() to use Miniflare's dev registry implementation

  Updated getPlatformProxy() to use Miniflare's dev registry instead of Wrangler's implementation. Previously, you had to start a wrangler or vite dev session before accessing the proxy bindings to connect to those workers. Now the order doesn't matter.

• #​10219 28494f4 Thanks @​dario-piotrowicz! - fix NonRetryableError thrown with an empty error message not stopping workflow retries locally

• Updated dependencies [1479fd0, 05c5b28, e3d9703, d481901]:

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

v4.28.1

Compare Source

Patch Changes

• #​10130 773cca3 Thanks @​dario-piotrowicz! - update maybeStartOrUpdateRemoteProxySession config argument (to allow callers to specify an environment)

  Before this change maybeStartOrUpdateRemoteProxySession could be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so the maybeStartOrUpdateRemoteProxySession API has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.

  For example, before callers could invoke the function in the following way

  await maybeStartOrUpdateRemoteProxySession(configPath);

  note that there is no way to tell the function what environment to use when parsing the wrangle configuration.

  Now callers will instead call the function in the following way:

  await maybeStartOrUpdateRemoteProxySession({
  	path: configPath,
  	environment: targetEnvironment,
  });

  note that now a target environment can be specified.

• #​10130 773cca3 Thanks @​dario-piotrowicz! - fix getPlatformProxy not taking into account the potentially specified environment for remote bindings

• #​10122 2e8eb24 Thanks @​dario-piotrowicz! - fix startWorker not respecting auth options for remote bindings

  fix startWorker currently not taking into account the auth field
  that can be provided as part of the dev options when used in conjunction
  with remote bindings

  example:

  Given the following

  import { unstable_startWorker } from "wrangler";
  
  const worker = await unstable_startWorker({
  	entrypoint: "./worker.js",
  	bindings: {
  		AI: {
  			type: "ai",
  			experimental_remote: true,
  		},
  	},
  	dev: {
  		experimentalRemoteBindings: true,
  		auth: {
  			accountId: "<ACCOUNT_ID>",
  			apiToken: {
  				apiToken: "<API_TOKEN>",
  			},
  		},
  	},
  });
  
  await worker.ready;

  wrangler will now use the provided <ACCOUNT_ID> and <API_TOKEN> to integrate with
  the remote AI binding instead of requiring the user to authenticate.

• #​10209 93c4c26 Thanks @​devin-ai-integration! - fix: strip ANSI escape codes from log files to improve readability and parsing

• #​9774 48853a6 Thanks @​nikitassharma! - Validate container configuration against account limits in wrangler to give early feedback to the user

• #​10122 2e8eb24 Thanks @​dario-piotrowicz! - fix incorrect TypeScript type for AI binding in the startWorker API

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Package Changes Through 271f279

No changes.

Add a change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​wrangler@​4.28.0 ⏵ 4.33.1	+1		+1

View full report