NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #4709 most downloaded on npm
Command-line interface for all things Cloudflare Workers
Latest stable
4.164.0
Last release today
17 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
4978 releases · first in 2012
Drag across the ruler to compare, or tap a release to open it.
Before this change maybeStartOrUpdateRemoteProxySession could be called with either the path to a wrangler config file or the configuration of a worke
#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
Your coding agent can read these notes before it upgrades. Set up the MCP server →
currently the way wrangler dev prints logs is faulty, for example the following code
e82aa19 Thanks @Akshit222! - Add --json flag to r2 bucket info command for machine-readable output.#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]:
If there are no .dev.vars or .dev.vars. files, when running Wrangler or the Vite plugin in local development mode, they will now try to load additiona
#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:
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.wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.--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.#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]:
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
#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
#9897 755a249 Thanks @edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint
Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:
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
#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
#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]:
We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.
#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]:
### Minor Changes - #9835 `9f0c175` Thanks @thomasgauvin! - Added rename namespace command to Workers KV ### Patch Changes - #9934 `6cc24c0` Thanks @e
9f0c175 Thanks @thomasgauvin! - Added rename namespace command to Workers KV6cc24c0 Thanks @emily-shen! - Add more thorough validation to containers configurationUpdated dependencies [`ac08e68`, `3bb69fa`, `274a826`, `77d1cb2`, `5b0fc9e`, `bf4c9ab`, `14ce577`]:
#9905 4ba9f25 Thanks @dom96! - Support for Python packages in python_modules dir
#9886 17b1e5a Thanks @dom96! - Python packages are now read from cf-requirements.txt instead of requirements.txt by default
#9899 d6a1b9b Thanks @simonabadoiu! - Print local mode when running a browser binding in local mode
#9951 e2672c5 Thanks @penalosa! - Recommend remote bindings when wrangler dev --remote is used
#9875 a5d7b35 Thanks @gpanders! - Show expected format in error message for "containers images delete"
#9954 bf4c9ab Thanks @penalosa! - Support Images binding in getPlatformProxy()
#9974 f73da0d Thanks @penalosa! - Pass worker name & compliance region through correctly when starting a remote bindings session
Updated dependencies [ac08e68, 3bb69fa, 274a826, 77d1cb2, 5b0fc9e, bf4c9ab, 14ce577]:
currently container builds run during local development (via wrangler dev or startWorker) prevent the standard hotkeys not to be recognized (most noti
#9923 c01c4ee Thanks @gpanders! - Fix image name resolution when modifying a container application
#9833 3743896 Thanks @dario-piotrowicz! - fix: ensure that container builds don't disrupt dev hotkey handling
currently container builds run during local development (via wrangler dev or startWorker) prevent the standard hotkeys not to be recognized (most noticeably ctrl+c, preventing developers from existing the process), the changes here ensure that hotkeys are instead correctly handled as expected
Updated dependencies []:
### Patch Changes - #9917 `80cc834` Thanks @edmundhung! - fix: assets only versions upload should include tag and message
80cc834 Thanks @edmundhung! - fix: assets only versions upload should include tag and messageWhen we push the image to the managed registry, we first re-tag the image to include the user's account ID so that the image has the full resolved ima
#9765 05adc61 Thanks @hasip-timurtas! - Build container images without the user's account ID. This allows containers to be built and verified in dry run mode (where we do not necessarily have the user's account info).
When we push the image to the managed registry, we first re-tag the image to include the user's account ID so that the image has the full resolved image name.
Updated dependencies [bb09e50, 25dbe54, 3bdec6b]:
Configure connection limits to Hyperdrive via command line options:
#9796 ba69586 Thanks @simonabadoiu! - Browser Rendering local mode
#9825 49c85c5 Thanks @ReppCodes! - Add support for origin_connection_limit to Wrangler
Configure connection limits to Hyperdrive via command line options:
--origin-connection-limit: The (soft) maximum number of connections that Hyperdrive may establish to the origin database.#9064 a1181bf Thanks @sdnts! - Added an event-subscriptions subcommand
#9729 1b3a2b7 Thanks @404Wolf! - Set docker build context to the Dockerfile directory when image_build_context is not explicitly provided
#9845 dbfa4ef Thanks @jonboulle! - remove extraneous double spaces from Wrangler help output
#9811 fc29c31 Thanks @gpanders! - Fix unauthorized errors on "containers images delete".
#9813 45497ab Thanks @gpanders! - Support container image names without account ID
#9821 a447d67 Thanks @WillTaylorDev! - Preview Aliases: Force alias generation to meet stricter naming requirements.
For cases where CI is requesting Wrangler to generate the alias based on the branch name, we want a stricter check around the generated alias name in order to avoid version upload failures. If a valid alias name was not able to be generated, we warn and do not provide an alias (avoiding a version upload failure).
#9840 7c55f9e Thanks @dario-piotrowicz! - fix: make sure that the experimental remoteBindings flag is properly handled in getPlatformProxy
There are two issues related to how the experimental remoteBindings flag is handled in getPlatformProxy that are being fixed by this change:
experimental_remote configuration flag set on service bindings is incorrectly always taken into account, even if remoteBindings is set to falseexperimental_remote configuration flag of all the other bindings is never taken into account (effectively preventing the bindings to be used in remote mode) since the remoteBindings flag is not being properly propagated#9801 0bb619a Thanks @IRCody! - Containers: Fix issue where setting an image URI instead of dockerfile would incorrectly not update the image
#9872 a727db3 Thanks @emily-shen! - fix: resolve Dockerfile path relative to the Wrangler config path
This fixes a bug where Wrangler would not be able to find a Dockerfile if a Wrangler config path had been specified with the --config flag.
#9815 1358034 Thanks @gpanders! - Remove --json flag from containers and cloudchamber commands (except for "images list")
#9734 1a58bc3 Thanks @penalosa! - Make Wrangler warn more loudly if you're missing auth scopes
#9748 7e3aa1b Thanks @alsuren! - Internal-only WRANGLER_D1_EXTRA_LOCATION_CHOICES environment variable for enabling D1's testing location hints
Updated dependencies [ba69586, 1a75f85, 395f36d, 6f344bf]:
Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode
#9535 56dc5c4 Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.
Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.
#9810 8acaf43 Thanks @WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.
this change makes sure that that getPlatformProxy, when the input configuration file contains an assets field, correctly returns the appropriate asset
#7871 f2a8d4a Thanks @dario-piotrowicz! - add support for assets bindings to getPlatformProxy
this change makes sure that that getPlatformProxy, when the input configuration
file contains an assets field, correctly returns the appropriate asset binding proxy
example:
// wrangler.jsonc
{
"name": "my-worker",
"assets": {
"directory": "./public/",
"binding": "ASSETS"
}
}
import { getPlatformProxy } from "wrangler";
const { env, dispose } = await getPlatformProxy();
const text = await (await env.ASSETS.fetch("http://0.0.0.0/file.txt")).text();
console.log(text); // logs the content of file.txt
await dispose();
#9717 d2f2f72 Thanks @nikitassharma! - Containers should default to a "dev" instance type when no instance type is specified in the wrangler config
#9620 1b967ea Thanks @gpanders! - Simplify containers images list output format
#9684 94a340e Thanks @WillTaylorDev! - Select only successfully deployed deployments when tailing.
### Patch Changes - #9731 `75b75f3` Thanks @gabivlj! - containers: Check for container scopes before running a container command to give a better erro
#9731 75b75f3 Thanks @gabivlj! - containers: Check for container scopes before running a container command to give a better error
#9641 fdbc9f6 Thanks @IRCody! - Update container builds to use a more robust method for detecting if the currently built image already exists.
#9736 55c83a7 Thanks @gabivlj! - containers: Do not check scopes if not defined
#9667 406fba5 Thanks @IRCody! - Fail earlier in the deploy process when deploying a container worker if docker is not detected.
Deprecates containers.configuration in favour of top level fields. Makes top level image required. Deprecates instances and durable_objects. Makes nam…
#9626 9c938c2 Thanks @penalosa! - Support wrangler version upload for Python Workers
#9718 fb83341 Thanks @mhart! - fix error message when docker daemon is not running
#9689 b137a6f Thanks @emily-shen! - fix: correctly pass container engine config to miniflare
#9722 29e911a Thanks @emily-shen! - Update containers config schema.
Deprecates containers.configuration in favour of top level fields. Makes top level image required. Deprecates instances and durable_objects. Makes name optional.
#9666 f3c5791 Thanks @IRCody! - Add a reasonable default name for containers that have no defined name.
Updated dependencies [b137a6f]:
This should have no functional change, but allows us to conditionally render hotkeys based on config.
#9692 273952f Thanks @dom96! - Condenses Python vendored modules in output table
#9654 2a5988c Thanks @dom96! - Python Workers now automatically bundle .so files from vendored packages
#9695 0e64c35 Thanks @emily-shen! - Move hotkey registration later in dev start up
This should have no functional change, but allows us to conditionally render hotkeys based on config.
#9098 ef20754 Thanks @jseba! - Migrate Workers Containers commands to Containers API Endpoints
The Workers Containers API was built on top of Cloudchamber, but has now been moved to its own API with a reduced scoping and new token.
#9712 2a4c467 Thanks @emily-shen! - Make wrangler container commands print open-beta status
`json // wrangler.jsonc { "name": "get-platform-proxy-test", "services": [ { "binding": "MY_WORKER", "service": "my-worker", "experimental_remote": tr
#9688 086e29d Thanks @dario-piotrowicz! - add remote bindings support to getPlatformProxy
Example:
// wrangler.jsonc
{
"name": "get-platform-proxy-test",
"services": [
{
"binding": "MY_WORKER",
"service": "my-worker",
"experimental_remote": true
}
]
}
// index.mjs
import { getPlatformProxy } from "wrangler";
const { env } = await getPlatformProxy({
experimental: {
remoteBindings: true,
},
});
// env.MY_WORKER.fetch() fetches from the remote my-worker service
#9558 d5edf52 Thanks @ichernetsky-cf! - wrangler containers apply uses observability configuration.
#9678 24b2c66 Thanks @dario-piotrowicz! - remove warnings during config validations on experimental_remote fields
wrangler commands, run without the --x-remote-bindings flag, parsing config files containing experimental_remote fields currently show warnings stating that the field is not recognized. This is usually more cumbersome than helpful so here we're loosening up this validation and making wrangler always recognize the field even when no --x-remote-bindings flag is provided
#9633 3f478af Thanks @nikitassharma! - Add support for setting an instance type for containers in wrangler. This allows users to configure memory, disk, and vCPU by setting instance type when interacting with containers.
#9596 5162c51 Thanks @CarmenPopoviciu! - add ability to pull images for containers local dev
Updated dependencies [bfb791e, 5162c51]:
Updated dependencies [`17d23d8`]:
#9673 ffa742f Thanks @dario-piotrowicz! - fix: ensure that wrangler deploy and version upload don't override the remote-bindings flag
#9653 8a60fe7 Thanks @penalosa! - Rename WRANGLER_CONTAINERS_DOCKER_PATH to WRANGLER_DOCKER_BIN
#9664 c489a44 Thanks @IRCody! - Remove cloudchamber/container apply confirmation dialog when run non-interactively.
#9653 8a60fe7 Thanks @penalosa! - Add a warning banner to wrangler cloudchamber and wrangler containers commands
#9605 17d23d8 Thanks @emily-shen! - Add rebuild hotkey for containers local dev, and clean up containers at the end of a dev session.
Updated dependencies [17d23d8]:
Updated dependencies [`d1d34fe`]:
Updated dependencies [`828b7df`, `2671e77`]:
#9565 b1c9139 Thanks @IRCody! - Ensure that a container applications image configuration is not updated if there were not changes to the image.
#9628 92f12f4 Thanks @gpanders! - Remove "Cloudchamber" from user facing error messages
#9576 2671e77 Thanks @vicb! - Add core local dev functionality for containers.
Adds a new WRANGLER_DOCKER_HOST env var to customise what socket to connect to.
Updated dependencies [828b7df, 2671e77]:
add a warning suggesting users to specify their target environment (via -e or --env) when their wrangler config file contains some environments and th
#9536 3b61c41 Thanks @dario-piotrowicz! - expose Unstable_Binding type
#9564 1d3293f Thanks @skepticfx! - Switch container registry to registry.cloudflare.com from registry.cloudchamber.cfdata.org.
Also adds the env var CLOUDFLARE_CONTAINER_REGISTRY to override this
#9520 04f9164 Thanks @vicb! - fix the default value for keep_names (true)
#9506 36113c2 Thanks @penalosa! - Strip the CF-Connecting-IP header from outgoing fetches
#9592 49f5ac7 Thanks @petebacondarwin! - Point to the right location for docs on telemetry
#9593 cf33417 Thanks @vicb! - drop unused WRANGLER_UNENV_RESOLVE_PATHS env var
#9566 521eeb9 Thanks @vicb! - Bump @cloudflare/unenv-preset to 2.3.3
#9344 02e2c1e Thanks @dario-piotrowicz! - add warning about env not specified to potentially risky wrangler commands
add a warning suggesting users to specify their target environment (via -e or --env)
when their wrangler config file contains some environments and they are calling one
of the following commands:
this is a measure we're putting in place to try to prevent developers from accidentally applying changes to an incorrect (potentially even production) environment
#9344 02e2c1e Thanks @dario-piotrowicz! - allow passing an empty string to the -e|--env flag to target the top-level environment
#9536 3b61c41 Thanks @dario-piotrowicz! - performance improvement: restart a mixed mode session only if the worker's remote bindings have changed
#9550 c117904 Thanks @dario-piotrowicz! - allow startWorker to accept false as an inspector option (to disable the inspector server)
#9473 fae8c02 Thanks @dario-piotrowicz! - expose new experimental_maybeStartOrUpdateMixedModeSession utility
Updated dependencies [bd528d5, 2177fb4, 36113c2, e16fcc7]:
Implements the proposal noted here https://github.com/cloudflare/workers-sdk/discussions/9143.
#9509 0b2ba45 Thanks @emily-shen! - feat: add static routing options via 'run_worker_first' to Wrangler
Implements the proposal noted here https://github.com/cloudflare/workers-sdk/discussions/9143.
This is now usable in wrangler dev and in production - just specify the routes that should hit the worker first with run_worker_first in your Wrangler config. You can also omit certain paths with ! negative rules.
#9507 1914b87 Thanks @dario-piotrowicz! - slightly improve wrangler dev bindings loggings
improve the bindings loggings by:
[connected] suffix for remote bindings#9475 931f467 Thanks @edmundhung! - add hello world binding that serves as as an explanatory example.
#9443 95eb47d Thanks @dario-piotrowicz! - add workerName option to startMixedModeSession API
#9541 80b8bd9 Thanks @dario-piotrowicz! - make workers created with startWorker await the ready promise on dispose
#9443 95eb47d Thanks @dario-piotrowicz! - add mixed-mode support for mtls bindings
#9515 9e4cd16 Thanks @dario-piotrowicz! - make sure that remote binding errors are surfaced when using mixed (hybrid) mode
#9516 92305af Thanks @IRCody! - Reorder deploy output when deploying a container worker so the worker url is printed last and the worker triggers aren't deployed until the container has been built and deployed successfully.
Updated dependencies [931f467, 95eb47d, 0b2ba45]:
add an new experimentalMixedMode dev option to unstable_startWorker that allows developers to programmatically start a new mixed mode session using st
#9461 66edd2f Thanks @skepticfx! - Enforce disk limits on container builds
#9481 d1a1787 Thanks @WillTaylorDev! - Force autogenerated aliases to be fully lowercased.
#9480 1f84092 Thanks @dario-piotrowicz! - add experimentalMixedMode dev option to unstable_startWorker
add an new experimentalMixedMode dev option to unstable_startWorker
that allows developers to programmatically start a new mixed mode
session using startWorker.
Example usage:
// index.mjs
import { unstable_startWorker } from "wrangler";
await unstable_startWorker({
dev: {
experimentalMixedMode: true,
},
});
// wrangler.jsonc
{
"$schema": "node_modules/wrangler/config-schema.json",
"name": "programmatic-start-worker-example",
"main": "src/index.ts",
"compatibility_date": "2025-06-01",
"services": [
{ "binding": "REMOTE_WORKER", "service": "remote-worker", "remote": true }
]
}
Updated dependencies [4ab5a40, 485cd08, e3b3ef5, 3261957]:
### Patch Changes - #9456 `db2cdc6` Thanks @WillTaylorDev! - Fix bug causing preview alias to always be generated.
db2cdc6 Thanks @WillTaylorDev! - Fix bug causing preview alias to always be generated.Updated dependencies [`8c7ce77`, `80e75f4`, `80e75f4`, `fac2f9d`, `92719a5`]:
03b8c1c Thanks @WillTaylorDev! - Provide ability for Wrangler to upload preview aliases during version upload.#9390 80e75f4 Thanks @penalosa! - Support additional Mixed Mode resources in Wrangler:
#9395 b3be057 Thanks @Maximo-Guk! - Add WRANGLER_CI_OVERRIDE_NETWORK_MODE_HOST for Workers CI
#9410 87f3843 Thanks @dario-piotrowicz! - enable consumers of unstable_readConfig to silence remote warnings
Updated dependencies [8c7ce77, 80e75f4, 80e75f4, fac2f9d, 92719a5]:
Specifically the exports have been added:
34b6174 Thanks @jamesopstad! - Hard fail on Node.js < 20. Wrangler no longer supports Node.js 18.x as it reached end-of-life on 2025-04-30. See https://github.com/nodejs/release?tab=readme-ov-file#end-of-life-releases.#9308 d3a6eb3 Thanks @dario-piotrowicz! - expose new utilities and types to aid consumers of the programmatic mixed-mode API
Specifically the exports have been added:
Experimental_MixedModeSession: type representing a mixed-mode sessionExperimental_ConfigBindingsOptions: type representing config-bindingsexperimental_pickRemoteBindings: utility for picking only the remote bindings from a record of start-worker bindings.unstable_convertConfigBindingsToStartWorkerBindings: utility for converting config-bindings into start-worker bindings (that can be passed to startMixedModeSession)#9347 b8f058c Thanks @penalosa! - Improve binding display on narrower terminals
Updated dependencies [d9d937a, e39a45f, fdae3f7]:
Now it is possible to target Wrangler at the FedRAMP High compliance region. There are two ways to signal to Wrangler to run in this mode:
#9321 6c03bde Thanks @petebacondarwin! - Add support for FedRAMP High compliance region
Now it is possible to target Wrangler at the FedRAMP High compliance region. There are two ways to signal to Wrangler to run in this mode:
"compliance_region": "fedramp_high" in a Wrangler configurationCLOUDFLARE_COMPLIANCE_REGION=fedramp_high environment variable when running WranglerIf both are provided and the values do not match then Wrangler will exit with an error.
When in this mode OAuth authentication is not supported. It is necessary to authenticate using a Cloudflare API Token acquired from the Cloudflare FedRAMP High dashboard.
Most bindings and commands are supported in this mode.
Resolves DEVX-1921.
#9330 34c71ce Thanks @edmundhung! - Updated internal configuration to use Miniflare’s new defaultPersistRoot instead of per-plugin persist flags
#8973 cc7fae4 Thanks @Caio-Nogueira! - Show latest instance by default on workflows instances describe command
#9335 6479fc5 Thanks @penalosa! - Redesign wrangler dev to more clearly present information and have a bit of a glow up ✨
#9329 410d985 Thanks @penalosa! - Hide logs in the startMixedModeSession() API
#9325 c2678d1 Thanks @edmundhung! - refactor: fallbacks to local image binding from miniflare when local mode is enabled
Updated dependencies [34c71ce, f7c82a4, 7ddd865, 6479fc5, e5ae13a]:
### Patch Changes - #9268 `7344344` Thanks @gabivlj! - wrangler containers delete handles API errors correctly
Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment. Now specifyin
#9288 3b8f7f1 Thanks @petebacondarwin! - allow --name and --env args on wrangler deploy
Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
Now specifying --name is supported and will override any names set in the Wrangler config:
wrangler.json
{
"name": "config-worker"
"env": {
"staging": { "name": "config-worker-env" }
}
}
| Command | Previous (Worker name) | Proposed (Worker name) | Comment |
|---|---|---|---|
| wrangler deploy --name=args-worker | "args-worker" | "args-worker" | CLI arg used |
| wrangler deploy --name=args-worker --env=staging | Error | "args-worker" | CLI arg used |
| wrangler deploy --name=args-worker --env=prod | Error | "args-worker" | CLI arg used |
| wrangler deploy | "config-worker" | "config-worker" | Top-level config used |
| wrangler deploy --env=staging | "config-worker-env" | "config-worker-env" | Named env config used |
| wrangler deploy --env=prod | "config-worker-prod" | "config-worker-prod" | CLI arg and top-level config combined |
#9265 16de0d5 Thanks @edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file
#9234 2fe6219 Thanks @emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch
#9269 66d975e Thanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev
Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.
Also include the ai binding since the bindings is already remote by default anyways.
#9151 5ab035d Thanks @gabivlj! - wrangler containers can be configured with the kind of application rollout on apply
#9231 02d40ed Thanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev
Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.
Also include the ai binding since the bindings is already remote by default anyways.
#9277 db5ea8f Thanks @penalosa! - Support Mixed Mode for more binding types
#9266 f2a16f1 Thanks @petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules
#9245 b87b472 Thanks @penalosa! - Support Mixed Mode Dispatch Namespaces
Updated dependencies [db5ea8f, b87b472]:
Updated dependencies [`3b384e2`]:
#9257 33daa09 Thanks @penalosa! - Relax R2 bucket validation for pages dev commands
#9256 3b384e2 Thanks @penalosa! - Move the Analytics Engine simulator implementation from JSRPC to a Wrapped binding. This fixes a regression introduced in https://github.com/cloudflare/workers-sdk/pull/8935 that preventing Analytics Engine bindings working in local dev for Workers with a compatibility date prior to JSRPC being enabled.
Updated dependencies [3b384e2]:
In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug
#9246 d033a7d Thanks @edmundhung! - fix: strip CF-Connecting-IP header within fetch
In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.
Updated dependencies [f61a08e, ea71df3, d033a7d]:
`ts interface Env { SERVICE_BINDING: Fetcher; } `
#8794 02f0699 Thanks @eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:
interface Env {
SERVICE_BINDING: Fetcher;
}
This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:
interface Env {
SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}
#8716 63a6504 Thanks @ItsWendell! - add --metafile flag to generate esbuild metadata file during build
#9122 f17ee08 Thanks @avenceslau! - Unhide wrangler workflows delete command
#9168 6b42c28 Thanks @dario-piotrowicz! - remove experimental MixedModeConnectionString type
remove the experimental MixedModeConnectionString type which
is now exposed by Miniflare instead
#7914 37af035 Thanks @andyjessop! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests
#9161 53ba97d Thanks @lambrospetrou! - Fix d1 info command showing read_replication: [object Object]
#9183 f6f1a18 Thanks @dario-piotrowicz! - add remote option to initial bindings
add the remote option (initial implementation
gated behind --x-mixed-mode) for the following
bindings: service, kv, r2, d1, queue and workflow
#9149 415520e Thanks @penalosa! - Implement mixed mode proxy server & client
Updated dependencies [37af035, ceeb375, 349cffc, 362cb0b, 2cc8197, 6b42c28]:
make sure that unstable_startWorker can throw configuration related errors when:
#9124 d0d62e6 Thanks @dario-piotrowicz! - make that unstable_startWorker can correctly throw configuration errors
make sure that unstable_startWorker can throw configuration related errors when:
setConfig is called with the throwErrors argument set to trueadditionally when an error is thrown when unstable_startWorker is called make sure
that the worker is properly disposed (since, given the fact that it is not returned
by the utility the utility's caller wouldn't have any way to dispose it themselves)
Updated dependencies [`df5d1f6`, `4672bda`, `c6b3f10`]:
#9158 826c5e8 Thanks @petebacondarwin! - fix CallSite.toString() not to throw
#9159 c6b3f10 Thanks @petebacondarwin! - bump esbuild version to fix regression in 0.25.0
#8985 078c568 Thanks @gabivlj! - wrangler deploy is able to deploy new container versions
#9162 8c3cdc3 Thanks @petebacondarwin! - Do not report "d1 execute" command file missing error to Sentry
Updated dependencies [df5d1f6, 4672bda, c6b3f10]:
This experimental utility has no effect. More details will be shared as we roll out its functionality.
#9118 1cd30a5 Thanks @dario-piotrowicz! - fix: remove outdated js-doc comment for unstable_startDevWorker's entrypoint
#9120 11aa362 Thanks @dario-piotrowicz! - Add experimental_startMixedModeSession no-op utility
This experimental utility has no effect. More details will be shared as we roll out its functionality.
#7423 2be85d7 Thanks @penalosa! - Make sure custom build logging output is more clearly signposted, and make sure it doesn't interfere with the interactive dev session output.
#9112 3fe85d4 Thanks @penalosa! - Warn if the Node.js version is below Node.js 20
Previously, if you added modules rules such as /*.js or /*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root
#9085 cdc88d8 Thanks @petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules
Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.
#9095 508a1a3 Thanks @petebacondarwin! - wrangler login put custom callback host and port into the auth URL
#9113 82e220e Thanks @dario-piotrowicz! - Add x-mixed-mode flag
This experimental flag currently has no effect. More details will be shared as we roll out its functionality.
Updated dependencies [357d42a]:
Updated dependencies [`d2ecc76`, `137d2da`]:
#8981 3b60131 Thanks @Caio-Nogueira! - Adds support for waitForEvent step type
#9083 137d2da Thanks @penalosa! - Support Tail Workers in local dev
#8975 9bf55aa Thanks @Caio-Nogueira! - Adds missing waiting status on the wrangler workflow instances list command
#9048 0b4d22a Thanks @garvit-gupta! - fix: Validate input file for Vectorize inserts
Updated dependencies [d2ecc76, 137d2da]:
Updated dependencies [`2c50115`]:
2c50115]:
Updated dependencies [`fc47c79`, `0838f1b`]:
#8983 f5ebb33 Thanks @Caio-Nogueira! - Remove open-beta disclaimer from workflows commands
#8990 6291fa1 Thanks @emily-shen! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.
#8966 234afae Thanks @penalosa! - Internal refactor to use the createCommand utility
Updated dependencies [fc47c79, 0838f1b]:
In your configuration file, you can define a service binding with props:
#8640 5ce70bd Thanks @kentonv! - Add support for defining props on a Service binding.
In your configuration file, you can define a service binding with props:
{
"services": [
{
"binding": "MY_SERVICE",
"service": "some-worker",
"props": { "foo": 123, "bar": "value" }
}
]
}
These can then be accessed by the callee:
import { WorkerEntrypoint } from "cloudflare:workers";
export default class extends WorkerEntrypoint {
fetch() {
return new Response(JSON.stringify(this.ctx.props));
}
}
#8771 0cfcfe0 Thanks @dario-piotrowicz! - feat: add config.keep_names option
Adds a new option to Wrangler to allow developers to opt out of esbuild's keep_names option (https://esbuild.github.io/api/#keep-names). By default, Wrangler sets this to true
This is something developers should not usually need to care about, but sometimes
keep_names can create issues, and in such cases they will be now able to opt-out.
Example wrangler.jsonc:
{
"name": "my-worker",
"main": "src/worker.ts",
"keep_names": false
}
Updated dependencies [`62c40d7`]:
69864b4 Thanks @gnekich! - introduce callback-host and callback-port param for wrangler login command#8889 eab7ad9 Thanks @penalosa! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.
#8673 5de2b9a Thanks @IRCody! - Add containers {info, list, delete} subcommands.
Updated dependencies [62c40d7]:
Updated dependencies [`511be3d`]:
#8950 bab1724 Thanks @edmundhung! - fix: include telemetry-related environment variables in release builds
#8903 085a565 Thanks @emily-shen! - disable eslint in generated types file
Updated dependencies [511be3d]:
which asset files were read from the file system
#8890 c912b99 Thanks @edmundhung! - update esbuild version to 0.25
#8711 4cc036d Thanks @CarmenPopoviciu! - Add the Pages deployment id to the JSON output for wrangler pages deployment list
#8244 84ecfe9 Thanks @CarmenPopoviciu! - feat: Add debug logs to capture assets upload status, specifically:
#8885 f2802f9 Thanks @CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message
#8924 d2b44a2 Thanks @dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands
a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands
Updated dependencies [f5413c5]:
Updated dependencies [`b7ac367`, `5388447`]:
Updated dependencies [`d454ad9`]:
d454ad9]:
this change improves that validation error message that users see when a redirected config file contains environments, by:
#8809 09464a6 Thanks @dario-piotrowicz! - improve error message when redirected config contains environments
this change improves that validation error message that users see when a redirected config file contains environments, by:
#8829 62df08a Thanks @cmackenzie1! - Add option --cors-origin none to remove CORS settings on a pipeline
Updated dependencies [afd93b9, 930ebb2]:
Replace --enable-worker-binding and --enable-http with --source worker and --source http (or --source http worker for both)
93267cf Thanks @edmundhung! - Support Secrets Store Secret bindings#8780 4e69fb6 Thanks @cmackenzie1! - - Rename wrangler pipelines show to wrangler pipelines get
--enable-worker-binding and --enable-http with --source worker and --source http (or
--source http worker for both)--file-template and --partition-template flags from wrangler pipelines create|updatewrangler pipelines get <pipeline>. Existing output is available using --format=json.wrangler pipelines create commands.#8596 75b454c Thanks @dario-piotrowicz! - add validation to redirected configs in regards to environments
add the following validation behaviors to wrangler deploy commands, that relate
to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):
--env=my-env) when using redirected
configs is incorrect, so these environments should be ignored and a warning should be
presented to the user#8795 d4c1171 Thanks @GregBrimble! - feat: Unhide wrangler pages functions build command.
This is already documented for Pages Plugins and by officially documenting it, we can ease the transition to Workers Assets for users of Pages Functions.
Updated dependencies [93267cf, ec7e621]:
Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wr
#8763 2650fd3 Thanks @garrettgu10! - R2 data catalog URIs now separate account ID and warehouse name with a slash rather than an underscore
#8341 196f51d Thanks @kotkoroid! - Improve error message when request to obtain membership info fails
Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.
Updated dependencies [e0efb6f, 0a401d0]:
Add --shard-count option for wrangler pipelines for more control over Pipeline throughput or file size
#8746 7427004 Thanks @emily-shen! - Log whether a command is operating on a remote or local resource
#8757 199caa4 Thanks @emily-shen! - fix: return actual error on wrangler secret bulk
#8750 80ef13c Thanks @emily-shen! - fix: include documentation_url in API Errors if provided
#8759 55b336f Thanks @garvit-gupta! - fix: Minor refactor for the r2 data catalog commands
#8753 245cfbd Thanks @cmackenzie1! - - Hide --transform-worker flag on wrangler pipelines <create|update> during private beta.
--shard-count option for wrangler pipelines <create|update> for more control over Pipeline throughput or file
sizeUpdated dependencies [007f322]:
Internal DOs still do not work with getPlatformProxy, but warn instead of crashing.
#8720 8df60b5 Thanks @lukevalenta! - Fix logic to derive resource name from binding by replacing all underscores with dashes
#8697 ec1f813 Thanks @emily-shen! - fix: stop getPlatformProxy crashing when internal DOs are present
Internal DOs still do not work with getPlatformProxy, but warn instead of crashing.
#8737 624882e Thanks @garvit-gupta! - fix: General improvements for the R2 catalog commands
### Minor Changes - #8548 `24c2c8f` Thanks @garvit-gupta! - feat: Add wrangler commands for R2 Data Catalog ### Patch Changes - #8583 `ecbab5d` Thanks
Use the workerd native implementation of createSecureContext and checkServerIdentity from node:tls. The functions have been implemented in cloudflare/
#8435 8e3688f Thanks @emily-shen! - fix: include assets binding when printing summary of bindings
#8675 f043b74 Thanks @vicb! - Bump @cloudflare/unenv-preset to 2.3.1
Use the workerd native implementation of createSecureContext and checkServerIdentity from node:tls. The functions have been implemented in cloudflare/workerd#3754.
Updated dependencies [`7682675`, `9c844f7`, `29cb306`]:
#8655 7682675 Thanks @emily-shen! - fix bug where assets in directories starting with . would crash the dev server
#8604 d8c0495 Thanks @dario-piotrowicz! - Amend pages dev error message when an environment is requested
#8536 e4b76e8 Thanks @gabivlj! - wrangler cloudchamber create explicitly sets IPv6 predefined
Updated dependencies [7682675, 9c844f7, 29cb306]:
Enable the recently implemented native APIs from node:crypto
#8575 4a5f270 Thanks @LuisDuarte1! - Add workflows delete API endpoint
#8578 5f151fc Thanks @LuisDuarte1! - Add terminate-all command to workflows
#8382 0d1240b Thanks @jvaughan-cloudflare! - Add Secrets Store command support to Wrangler CLI
#8569 1c94eee Thanks @vicb! - Bump @cloudflare/unenv-preset to 2.3.0
Enable the recently implemented native APIs from node:crypto
#8556 b7d6b7d Thanks @GregBrimble! - Add support for assets_navigation_prefer_asset_serving in Vite (dev and preview)
#8597 5d78760 Thanks @CarmenPopoviciu! - feat: Graduate experimental RPC support for Workers with assets in local dev
Updated dependencies [d8f1c49, b7d6b7d, 5d78760, c0d0cd0]:
This new command can be used to delete all existing messages in a Queue
#8258 9adbd50 Thanks @knickish! - Enable the creation of MySQL Hypedrive configs via the Wrangler CLI.
#8353 c4fa349 Thanks @jbwcloudflare! - Add new command to purge a Queue
This new command can be used to delete all existing messages in a Queue
#8461 86ab0ca Thanks @GregBrimble! - Add a 'allowTrailingCommas: true' option to improve IDE experience of 'wrangler.jsonc?'
#8550 5ae12a9 Thanks @vicb! - Bump @cloudflare/unenv-preset to 2.2.0
Use the workerd native implementation for node:tls
#8501 383dc0a Thanks @GregBrimble! - Add support for assets_navigation_prefers_asset_serving compatibility flag in wrangler dev
#8562 8278db5 Thanks @IRCody! - Add initial containers subcommand to wrangler.
#8376 a25f060 Thanks @CarmenPopoviciu! - feat: Make local dev RPC behaviour on par with production for Workers with assets
#8534 62d5471 Thanks @petebacondarwin! - improve the error messaging when the user provides neither an entry point nor an asset directory
#8528 2a43cdc Thanks @cmackenzie1! - Support wrangler types for Pipelines
#8579 29015e5 Thanks @cmackenzie1! - Allow wrangler pipelines update <pipelineName> --transform-worker none to remove transformations from a Pipeline.
Updated dependencies [9adbd50, dae7bd4, a25f060, a7bd79b]:
Updated dependencies [`ff26dc2`, `4ad78ea`]:
fd9dff8 Thanks @gabivlj! - wrangler deploy includes container configuration when uploading the script#8220 14680b9 Thanks @IRCody! - Fix a bug in cloudchamber build where it would still attempt to push an image if the build failed.
#8186 05973bb Thanks @IRCody! - Add cloudchamber images {list,delete} commands to list and delete images stored in cloudchamber managed registry.
Updated dependencies [ff26dc2, 4ad78ea]:
hyperdrive create test123 ... --ca-certificate-uuid=CA_CERT_UUID --mtls-certificate-uuid=MTLS_CERT_UUID
#8337 1b2aa91 Thanks @Ltadrian! - Add mTLS configuration fields to Hyperdrive command
hyperdrive create test123 ... --ca-certificate-uuid=CA_CERT_UUID --mtls-certificate-uuid=MTLS_CERT_UUID
#8401 b8fd1b1 Thanks @petebacondarwin! - Support no_bundle config in Pages for both dev and deploy.
This was already supported via a command line arg (--no-bundle).
#8472 4978e5b Thanks @edmundhung! - fix: throw explicit error for unknown mimetype during wrangler check startup
#8478 931b53d Thanks @penalosa! - Add wrangler types support for importable env and process.env
#8503 edf169d Thanks @GregBrimble! - Fix Workers Assets metafiles (_headers and _redirects) resolution when running Wrangler from a different directory
Updated dependencies [5ae180e, 74b0c73]:
One column per quarter.