Skip to content
This repository was archived by the owner on Aug 28, 2025. It is now read-only.

chore(deps): update dependency wrangler to v4.33.0 #73

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency wrangler to v4.33.0 #73

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 16, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 4.24.3 -> 4.33.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.33.0

Compare Source

Minor Changes
Patch Changes

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

    • miniflare@4.20250816.1

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

v4.30.0

Compare Source

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

    • miniflare@4.20250813.1

v4.29.1

Compare Source

Patch Changes
  • Updated dependencies [5020694]:
    • miniflare@4.20250813.0

v4.29.0

Compare Source

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

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

v4.28.0

Compare Source

Minor Changes
Patch Changes

  • #​10004 b4d1373 Thanks @​dario-piotrowicz! - fix wrangler dev logs being logged on the incorrect level in some cases

    currently the way wrangler dev prints logs is faulty, for example the following code

    console.error("this is an error");
console.warn("this is a warning");
console.debug("this is a debug");

    inside a worker would cause the following logs:

    ✘ [ERROR] this is an error

✘ [ERROR] this is a warning

this is a debug

    (note that the warning is printed as an error and the debug log is printed even if by default it should not)

    the changes here make sure that the logs are instead logged to their correct level, so for the code about the following will be logged instead:

    ✘ [ERROR] this is an error

▲ [WARNING] this is a warning

    (running wrangler dev with the --log-level=debug flag will also cause the debug log to be included as well)

  • #​10099 360004d Thanks @​emily-shen! - fix: move local dev container cleanup to process exit hook. This should ensure containers are cleaned up even when Wrangler is shut down programatically.

  • #​10186 dae1377 Thanks @​matthewdavidrodgers! - Deleting when Pages project binds to worker requires confirmation

  • #​10169 1655bec Thanks @​devin-ai-integration! - fix: report startup errors before workerd profiling

  • #​10136 354a001 Thanks @​nikitassharma! - Update wrangler containers images list to make fewer API calls to improve command runtime

  • #​10157 5c3b83f Thanks @​devin-ai-integration! - Enforce 64-character limit for Workflow binding names locally to match production validation

  • #​10154 502a8e0 Thanks @​devin-ai-integration! - Fix UTF BOM handling in config files - remove UTF-8 BOM and error on other BOMs

  • #​10176 07c8611 Thanks @​devin-ai-integration! - Add macOS version validation to prevent EPIPE errors on unsupported macOS versions (below 13.5). Miniflare and C3 fail hard while Wrangler shows warnings but continues execution.

  • Updated dependencies [6b9cd5b, 631f26d, d6ecd05, b4d1373, 8ba7736, 07c8611, 7e204a9, 3f83ac1]:

v4.27.0

Compare Source

Minor Changes

  • #​9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

    If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode,
    they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

    These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
    Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

    Further details:

    • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
    • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
    • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
    • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
    • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.
Patch Changes

  • #​10051 0f7820e Thanks @​nikitassharma! - Add support for custom instance limits for containers. For example, instead of
    having to use the preconfigured dev/standard/basic instance types, you can now
    set:

    instance_type: {
  vcpu: 1,
  memory_mib: 1024,
  disk_mb: 4000
}

    This feature is currently only available to customers on an enterprise plan.

  • #​10149 e9bb8d3 Thanks @​vicb! - fix require("debug") in nodejs_compat mode

  • Updated dependencies [9b61f44]:

    • miniflare@4.20250730.0

v4.26.1

Compare Source

Patch Changes

  • #​10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

    Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

    In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

  • #​10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

  • #​10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

  • #​9897 755a249 Thanks @​edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint

  • Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

v4.26.0

Compare Source

Minor Changes

  • #​10016 c5b291d Thanks @​emily-shen! - Interactively handle wrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.

    For example:

    npx wrangler deploy ./public will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    npx wrangler deploy --assets=./public will now ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    In non-interactive contexts, Wrangler will error as it currently does.

  • #​9971 19794bf Thanks @​edmundhung! - Improved script source display on the pretty error screen

Patch Changes

  • #​9800 3d4f946 Thanks @​helloimalastair! - remove banner from r2 getobject in pipe mode

  • #​9910 7245101 Thanks @​dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is ready

    fix the fact that when starting a local (or remote) dev session the log saying Ready on http://localhost:xxxx could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)

  • #​10031 823cba8 Thanks @​vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

  • #​10032 154acf7 Thanks @​dario-piotrowicz! - add support for containers in wrangler multiworker dev

    currently when running wrangler dev with different workers (meaning that the -c|--config flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.

  • #​9988 7fb0bfd Thanks @​penalosa! - Correctly label mtls remote bindings warning

  • Updated dependencies [823cba8, 19794bf, 059a39e]:

v4.25.1

Compare Source

Patch Changes

  • #​10000 c02b067 Thanks @​emily-shen! - Include more (sanitised) user errors in telemetry.

    We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.

  • #​9996 b0217f9 Thanks @​nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry

  • #​10009 e87198a Thanks @​gpanders! - Fix containers diff output when using JSONC config files

  • #​9976 ad02ad3 Thanks @​dario-piotrowicz! - add warning for when users run wrangler dev --remote with (enabled) containers

  • #​9819 0c4008c Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite dev

    Adds support for Cloudflare Containers in vite dev. Please note that at the time of this PR a container image can only specify the path to a Dockerfile. Support for registry links will be added in a later version, as will containers support in vite preview.

  • Updated dependencies [189fe23, 7e5585d]:

v4.25.0

Compare Source

Minor Changes
Patch Changes

v4.24.4

Compare Source

Patch Changes

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.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jul 16, 2025 •
edited
Loading

Deploying simulation with  Cloudflare Pages  Cloudflare Pages

Latest commit: fe57744
Status: ✅  Deploy successful!
Preview URL: https://c0afa963.simulation-8ty.pages.dev
Branch Preview URL: https://renovate-wrangler-4-x-lockfi.simulation-8ty.pages.dev

View logs

@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 78cf42b to b980007 Compare July 17, 2025 10:59
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.24.4 chore(deps): update dependency wrangler to v4.25.0 Jul 17, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from b980007 to d5c63db Compare July 22, 2025 12:58
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.25.0 chore(deps): update dependency wrangler to v4.25.1 Jul 22, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from d5c63db to 6a2b64d Compare July 24, 2025 17:05
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.25.1 chore(deps): update dependency wrangler to v4.26.0 Jul 24, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 6a2b64d to dd52dfd Compare August 4, 2025 13:33
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.26.0 chore(deps): update dependency wrangler to v4.27.0 Aug 4, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from dd52dfd to 71478fe Compare August 5, 2025 10:11
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.27.0 chore(deps): update dependency wrangler to v4.28.0 Aug 5, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 71478fe to 805ab45 Compare August 7, 2025 13:52
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.28.0 chore(deps): update dependency wrangler to v4.28.1 Aug 7, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 805ab45 to 765550f Compare August 12, 2025 19:08
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.28.1 chore(deps): update dependency wrangler to v4.29.0 Aug 12, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 765550f to 35dfb9d Compare August 13, 2025 15:07
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.29.0 chore(deps): update dependency wrangler to v4.29.1 Aug 13, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 35dfb9d to c8a95f2 Compare August 14, 2025 18:40
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.29.1 chore(deps): update dependency wrangler to v4.30.0 Aug 14, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from c8a95f2 to d82be04 Compare August 18, 2025 22:50
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.30.0 chore(deps): update dependency wrangler to v4.31.0 Aug 18, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from d82be04 to fe57744 Compare August 21, 2025 19:49
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.31.0 chore(deps): update dependency wrangler to v4.32.0 Aug 21, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from fe57744 to 070b820 Compare August 26, 2025 18:07
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.32.0 chore(deps): update dependency wrangler to v4.33.0 Aug 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant