Wrangler
Patch Changes
#8783
7bcf352
Thanks @petebacondarwin! - Improve error message when request to obtain membership info failsWrangler 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.
#8866
db673d6
Thanks @edmundhung! - improve error message when redirected config contains environmentsthis change improves that validation error message that users see when a redirected config file contains environments, by:
- cleaning the message formatting and displaying the offending environments in a list
- prompting the user to report the issue to the author of the tool which has generated the config
#8600
91cf028
Thanks @workers-devprod! - add validation to redirected configs in regards to environmentsadd the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by
.wrangler/deploy/config.json
files):- redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
- given the point above, specifying an environment (
--env=my-env
) when using redirected configs is incorrect, so these environments should be ignored and a warning should be presented to the user
Minor Changes
- #8807
dcce2ec
Thanks @LuisDuarte1! - Promote workflows commands to stable
Patch Changes
Patch Changes
- Updated dependencies [
d454ad9
]:
Minor Changes
Patch Changes
#8809
09464a6
Thanks @dario-piotrowicz! - improve error message when redirected config contains environmentsthis change improves that validation error message that users see when a redirected config file contains environments, by:
- cleaning the message formatting and displaying the offending environments in a list
- prompting the user to report the issue to the author of the tool which has generated the config
#8829
62df08a
Thanks @cmackenzie1! - Add option--cors-origin none
to remove CORS settings on a pipeline
Minor Changes
- #8394
93267cf
Thanks @edmundhung! - Support Secrets Store Secret bindings
Patch Changes
#8780
4e69fb6
Thanks @cmackenzie1! - - Renamewrangler pipelines show
towrangler pipelines get
- Replace
--enable-worker-binding
and--enable-http
with--source worker
and--source http
(or--source http worker
for both) - Remove
--file-template
and--partition-template
flags fromwrangler pipelines create|update
- Add pretty output for
wrangler pipelines get <pipeline>
. Existing output is available using--format=json
. - Clarify the minimums, maximums, and defaults (if unset) for
wrangler pipelines create
commands.
- Replace
#8596
75b454c
Thanks @dario-piotrowicz! - add validation to redirected configs in regards to environmentsadd the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by
.wrangler/deploy/config.json
files):- redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
- given the point above, specifying an environment (
--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: Unhidewrangler 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.
Patch Changes
#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 failsWrangler 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.
Patch Changes
#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 onwrangler 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 onwrangler pipelines <create|update>
during private beta.- Add
--shard-count
option forwrangler pipelines <create|update>
for more control over Pipeline throughput or file size
- Add
Updated dependencies [
007f322
]:
Patch Changes
#8758
04ba075
Thanks @emily-shen! - fix: return actual error onwrangler secret bulk
#8703
ef89e6b
Thanks @CarmenPopoviciu! - Improve formatting of cache options for hyperdrive list command#8751
e1ef298
Thanks @emily-shen! - fix: include documentation_url in API Errors if provided#8713
47bf369
Thanks @CarmenPopoviciu! - fix: stop getPlatformProxy crashing when internal DOs are presentInternal DOs still do not work with getPlatformProxy, but warn instead of crashing.
#8683
90d93c9
Thanks @CarmenPopoviciu! - RemoveNodeJSCompatModule
. This was never fully supported, and never worked for deploying Workers from Wrangler.Updated dependencies [
90d93c9
]:
Minor Changes
Patch Changes
#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 presentInternal 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
Patch Changes
#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.1Use the workerd native implementation of
createSecureContext
andcheckServerIdentity
fromnode:tls
. The functions have been implemented incloudflare/workerd#3754
.
Patch Changes
#8655
7682675
Thanks @emily-shen! - fix bug where assets in directories starting with . would crash the dev server#8604
d8c0495
Thanks @dario-piotrowicz! - Amendpages dev
error message when an environment is requested#8536
e4b76e8
Thanks @gabivlj! - wrangler cloudchamber create explicitly sets IPv6 predefinedUpdated dependencies [
7682675
,9c844f7
,29cb306
]:- miniflare@4.20250321.0
- @cloudflare/unenv-preset@2.3.1
Patch Changes
#8662
5e57717
Thanks @workers-devprod! - Amendpages dev
error message when an environment is requested#8535
6f8e892
Thanks @workers-devprod! - improve the error messaging when the user provides neither an entry point nor an asset directory
Minor Changes
#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.0Enable the recently implemented native APIs from
node:crypto
Patch Changes
#8556
b7d6b7d
Thanks @GregBrimble! - Add support forassets_navigation_prefer_asset_serving
in Vite (dev
andpreview
)#8597
5d78760
Thanks @CarmenPopoviciu! - feat: Graduate experimental RPC support for Workers with assets in local dev
Minor Changes
#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 QueueThis 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.0Use the workerd native implementation for
node:tls
Patch Changes
#8501
383dc0a
Thanks @GregBrimble! - Add support forassets_navigation_prefers_asset_serving
compatibility flag inwrangler 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! - Allowwrangler pipelines update <pipelineName> --transform-worker none
to remove transformations from a Pipeline.Updated dependencies [
9adbd50
,dae7bd4
,a25f060
,a7bd79b
]:- miniflare@4.20250319.0
- @cloudflare/unenv-preset@2.3.0
Minor Changes
- #8477
fd9dff8
Thanks @gabivlj! - wrangler deploy includes container configuration when uploading the script
Patch Changes
#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
]:- miniflare@4.20250317.1
- @cloudflare/unenv-preset@2.2.0
Minor Changes
#8337
1b2aa91
Thanks @Ltadrian! - Add mTLS configuration fields to Hyperdrive commandhyperdrive create test123 ... --ca-certificate-uuid=CA_CERT_UUID --mtls-certificate-uuid=MTLS_CERT_UUID
Patch Changes
#8401
b8fd1b1
Thanks @petebacondarwin! - Supportno_bundle
config in Pages for bothdev
anddeploy
.This was already supported via a command line arg (
--no-bundle
).#8472
4978e5b
Thanks @edmundhung! - fix: throw explicit error for unknown mimetype duringwrangler check startup
#8478
931b53d
Thanks @penalosa! - Addwrangler types
support for importable env andprocess.env
#8503
edf169d
Thanks @GregBrimble! - Fix Workers Assets metafiles (_headers
and_redirects
) resolution when running Wrangler from a different directory
Patch Changes
#8453
f90a669
Thanks @workers-devprod! - trigger dummy v3 maintenance release for testing#8500
80bbee3
Thanks @workers-devprod! - Supportno_bundle
config in Pages for bothdev
anddeploy
.This was already supported via a command line arg (
--no-bundle
).#8521
5cd32b1
Thanks @emily-shen! - fix: throw explicit error for unknown mimetype duringwrangler check startup
#8504
0192aae
Thanks @workers-devprod! - Fix Workers Assets metafiles (_headers
and_redirects
) resolution when running Wrangler from a different directoryUpdated dependencies [
f90a669
]:
We've released the next major version of Wrangler — wrangler@4.0.0. Wrangler v4 is a major release focused on updates to underlying systems and dependencies, along with improvements to keep Wrangler commands consistent and clear.
You can run the following command to install it in your projects:
Unlike previous major versions of Wrangler, which were foundational rewrites and rearchitectures — Version 4 of Wrangler includes a much smaller set of changes. If you use Wrangler today, your workflow is very unlikely to change.
A detailed migration guide is available and if you find a bug or hit a roadblock when upgrading to Wrangler v4, open an issue on the cloudflare/workers-sdk repository on GitHub.
Going forward, we'll continue supporting Wrangler v3 with bug fixes and security updates until Q1 2026, and with critical security updates until Q1 2027, at which point it will be out of support.
The full changelog is available at https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md#400
Patch Changes
#8393
c4653081c
Thanks @penalosa! - Deprecate Wrangler v2. Since the release of Wrangler v3 in 2023, we’ve seen great adoption, and today over 95% of active Wrangler usage is with v3.As such, Wrangler v2 is now deprecated, and no new features or bug fixes are being published for v2. We strongly recommend you upgrade to the latest version of Wrangler to receive continued support. We have a migration guide to make this process easy! If you encounter any difficulties, please let us know by filing an issue.