Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.20250801.0->4.20251118.04.27.0->4.49.0Release Notes
cloudflare/workerd (@cloudflare/workers-types)
v4.20251118.0Compare Source
v4.20251117.0Compare Source
v4.20251115.0Compare Source
v4.20251113.0Compare Source
v4.20251111.0Compare Source
v4.20251109.0Compare Source
v4.20251107.0Compare Source
v4.20251106.1Compare Source
v4.20251014.0Compare Source
v4.20251011.0Compare Source
v4.20251008.0Compare Source
v4.20251004.0Compare Source
v4.20251003.0Compare Source
v4.20251001.0Compare Source
v4.20250927.0Compare Source
v4.20250926.0Compare Source
v4.20250924.0Compare Source
v4.20250923.0Compare Source
v4.20250922.0Compare Source
v4.20250921.0Compare Source
v4.20250920.0Compare Source
v4.20250919.0Compare Source
v4.20250918.0Compare Source
v4.20250917.0Compare Source
v4.20250913.0Compare Source
v4.20250912.0Compare Source
v4.20250911.0Compare Source
v4.20250910.0Compare Source
v4.20250909.0Compare Source
v4.20250906.0Compare Source
v4.20250905.0Compare Source
v4.20250904.0Compare Source
v4.20250903.0Compare Source
v4.20250902.0Compare Source
v4.20250831.0Compare Source
v4.20250830.0Compare Source
v4.20250829.0Compare Source
v4.20250828.1Compare Source
v4.20250828.0Compare Source
v4.20250826.0Compare Source
v4.20250823.0Compare Source
v4.20250822.0Compare Source
v4.20250821.0Compare Source
v4.20250820.0Compare Source
v4.20250819.0Compare Source
v4.20250816.0Compare Source
v4.20250813.0Compare Source
v4.20250812.0Compare Source
v4.20250810.0Compare Source
v4.20250809.0Compare Source
v4.20250807.0Compare Source
v4.20250806.0Compare Source
v4.20250805.0Compare Source
v4.20250803.0Compare Source
v4.20250802.0Compare Source
cloudflare/workers-sdk (wrangler)
v4.49.0Compare Source
Minor Changes
#10703
c5c4ee5Thanks @danlapid! - Add support for streaming tail consumers in local dev. This is an experimental new feature that allows you to register atailStream()handler (compared to the existingtail()handler), which will receive streamed tail events from your Worker (compared to thetail()handler, which only receives batched events after your Worker has finished processing).#11251
7035804Thanks @penalosa! - When theWRANGLER_HIDE_BANNERenvironment variable is provided, Wrangler will no longer display a version banner. This applies to all commands.For instance, previously running
wrangler docswould give the following output:With
WRANGLER_HIDE_BANNER, this is now:#11285
d014fa7Thanks @vicb! - Implement thewrangler r2 bulk put bucket-name --filename list.jsoncommand.The command uploads multiple objects to an R2 bucket.
The list of object is provided as a JSON encoded file via
--filename. It is a list of key and file (respectively the name and the content for the object).Uploads are executed concurrently and the level of concurrency can be set via
--concurrency.The command supports the same options as
wrangler r2 object put, minus--file, and--pipeand plus--concurrency#11268
15b8460Thanks @penalosa! - Support SvelteKit projects in autoconfig#11258
2011b6aThanks @dario-piotrowicz! - Add--dry-runflag towrangler setupand also adryRunoption torunAutoConfigPatch Changes
#11261
a352c7fThanks @petebacondarwin! - Avoid using object lookup for OAuth Error classes#11286
8e99766Thanks @dario-piotrowicz! - fix: make sure thatexperimental_patchConfigdoesn't throw if it encounters anullvalue#11279
d0d3fe6Thanks @vicb! - bump p-queue to ^9.0.0#11278
92afbbaThanks @ascorbic! - Fixes a bug that caused.dev.varsto be ignored in OpenNext#11244
65b4afeThanks @petebacondarwin! - Internal refactoring to improve error traceability in wrangler dev#11238
da8442fThanks @jamesopstad! - Addunstable_getDurableObjectClassNameToUseSQLiteMapexport. This is an internal function for use in the Vite plugin.#11266
09cb720Thanks @penalosa! - Use the smol-toml library for parsing TOML instead of @iarna/toml#11236
793e2b4Thanks @ascorbic! - Refresh expired preview tokens when running in remote dev mode#11286
8e99766Thanks @dario-piotrowicz! - fix:wrangler deployfailing to patch localwrangler.jsoncfiles if the remotetail_consumersvalue isnull#11275
9cbf126Thanks @dario-piotrowicz! - Ensure thatwrangler deployrun with a positional argument or with--assetsdoes not trigger the autoconfig process (even with--experimental-autoconfig)#11242
dd1e560Thanks @dario-piotrowicz! - Fix: make sure that remote proxy sessions's debug logs are enabled when the wrangler log level is set to "debug"Updated dependencies [
c5c4ee5,d0041e2,827d017]:v4.48.0Compare Source
Minor Changes
#11212
3908162Thanks @dario-piotrowicz! - Add autoconfig changes summary forwrangler deploy --x-autoconfigwith the option for users to cancel the operation#11229
14d79f2Thanks @dario-piotrowicz! - Enablesexperimental-deploy-remote-diff-checkflag by default (the flag is still present for now so that users can turn it off if needed) and improves the remote config diffing logic (to include less noise in the diff presented to the user)#11245
dfc6513Thanks @vicb! - Change how Wrangler selects default ports for dev sessions.If no port is specified, Wrangler now probes the default port and the 10 consecutive ports after it before falling back to a random port.
This will help getting a stable port number across dev sessions.
Both the http server and inspector ports are affected.
Patch Changes
#11177
43fe9f3Thanks @MattieTK! - Added bun detection to package manager analyticsUpdated dependencies [
305ffb3,46ccf0e]:v4.47.0Compare Source
Minor Changes
#11201
5286309Thanks @avenceslau! - Add wrangler workflows instances restart command#11214
5cf8a39Thanks @penalosa! - Add the experimentalwrangler setupcommand to run autoconfig outside of the deploy flow.#11187
8abc789Thanks @dario-piotrowicz! - Add possibility for users to edit their project settings during autoconfigWhen running
wrangler deploy --experimental-autoconfig, after the automatic project settings detection Wrangler will now present users the opportunity to customize the auto-detected project's settingsPatch Changes
#11143
2d16610Thanks @FlorentCollin! - Improve the formatting of the D1 execute command to always show the duration in milliseconds with two decimal places.#11178
63defa2Thanks @ascorbic! - Log a more helpful error when attempting to "r2 object put" a non-existent file#11199
70d3d4aThanks @penalosa! - Add telemetry to autoconfig#11186
38396edThanks @hoodmane! - Removed warning when deploying a Python worker#11024
cdcecfcThanks @devin-ai-integration! - Use the nativenode:trace_eventsmodule when availableIt is enabled when the
enable_nodejs_trace_events_modulecompatibility flag is set.#11195
e85f965Thanks @ascorbic! - Ignores.dev.varsif--env-filehas been explicitly passedPreviously,
.dev.varswould always be read first, and then any file passed with--env-filewould override variables in.dev.vars. This meant there was no way to ignore.dev.varsif you wanted to use a different env file. Now, if--env-fileis passed,.dev.varswill be ignored entirely.#11181
88aa707Thanks @petebacondarwin! - add more logging around Wrangler authentication to help diagnose issuesUpdated dependencies [
dd7d584,4259256,cdcecfc]:v4.46.0Compare Source
Minor Changes
#11183
240ebebThanks @dario-piotrowicz! - exposeexperimental_getDetailsForAutoConfigandexperimental_runAutoConfigAPIs that provide respectively the autoconfig detection and execution functionalities#11180
53b0fceThanks @penalosa! - Detect non-framework static sites#11162
c3ed531Thanks @dario-piotrowicz! - add aremoteBindingsoption togetPlatformProxyto allow the disabling of remote bindings#11164
305d7bfThanks @penalosa! - Implement experimental autoconfig flow for static sites#10605
b55a3c7Thanks @emily-shen! - Add command to configure credentials for non-Cloudflare container registriesNote this is a closed/experimental command that will not work without the appropriate account-level capabilities.
#11078
5d7c4c2Thanks @simonha9! - Add jurisdiction support to d1 db creation via command-line argumentPatch Changes
#11160
05440a1Thanks @dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when runningwrangler deploy --env <TARGET_ENV>When running
wrangler deploy, with--x-remote-diff-checkand after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the--env|-eflag). Now this will also apply when an environment is targeted.#11162
c3ed531Thanks @dario-piotrowicz! - Update the description of the--localflag for thewrangler devcommand to clarify that it disables remote bindings, also un-deprecate and un-hide it#11162
c3ed531Thanks @dario-piotrowicz! - Fix bindings withremote: truebeing logged asremotewhen run viawrangler dev --localUpdated dependencies [
1ae020d]:v4.45.4Compare Source
Patch Changes
#11133
8ffbd17Thanks @petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.Now the argument values that are captured come from an allow list,
and can be marked as ALLOW (capture the real value) or REDACT (capture as "").
#11033
77ed7e2Thanks @dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when runningwrangler deployWhen running
wrangler deploy, with--x-remote-diff-check, Wrangler will display the difference between local and remote configuration.If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment.
In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.
#11139
bb00f9dThanks @devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally#11135
ed666a1Thanks @penalosa! - Implement tail-based logging forwrangler devremote mode, behind the--x-tail-tagsflag. This will become the default in the future.#11149
22f25fdThanks @penalosa! - Add no-op autoconfig logic behind an experimental flagUpdated dependencies [
90a2566,14f60e8]:v4.45.3Patch Changes
#11117
6822aafThanks @emily-shen! - fix: show local/remote status before D1 command confirmationsD1 commands (
execute,export,migrations apply,migrations list,delete,time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.#11077
bce8142Thanks @petebacondarwin! - Ensure that process.env is case-insensitive on WindowsThe object that holds the environment variables in
process.envdoes not care about the case of its keysin Windows. For example,
process.env.SystemRootandprocess.env.SYSTEMROOTwill refer to the same value.Previously, when merging fields from
.envfiles we were replacing this native object with a vanillaJavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
when in reality they just had different casing.
v4.45.2Patch Changes
#11097
55657ebThanks @penalosa! - Extract internal APIs into a new@cloudflare/workers-utilspackage#11118
d47f166Thanks @zebp! - Fix validation of thepersistfield of observabilitylogsandtracesconfigurationv4.45.1Compare Source
Patch Changes
#10959
d0208feThanks @devin-ai-integration! - Fixed conflict between--envand--expiresflags inwrangler r2 object put.--enow aliases--envonly, and NOT--expires.#10915
dbe51c1Thanks @devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.#10913
d4f2dafThanks @devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occurv4.45.0Compare Source
Minor Changes
#11030
1a8088aThanks @penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the--no-x-provisionflag. It currently works for R2, D1, and KV bindings.To use this feature, add a binding to your config file without a resource ID:
{ "kv_namespaces": [{ "binding": "MY_KV" }], "d1_databases": [{ "binding": "MY_DB" }], "r2_buckets": [{ "binding": "MY_R2" }], }wrangler devwill automatically create these resources for you locally, and when you next runwrangler deployWrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.Patch Changes
#11037
4bd4c29Thanks @danielrs! - Better Wrangler subdomain defaults warning.Improves the warnings that we show users when either
worker_devorpreview_urlsare missing.#10927
31e1330Thanks @dom96! - Implementspython_modules.excludeswrangler config field#10741
2f57345Thanks @penalosa! - Remove obsolete--x-remote-bindingsflagUpdated dependencies [
ca6c010]:v4.44.0Compare Source
Minor Changes
#10939
d4b4c90Thanks @danielrs! - Configpreview_urlsdefaults toworkers_devvalue.Originally, we were defaulting config.preview_urls to
true, but wewere accidentally enabling Preview URLs for users that only had
config.workers_dev=false.
Then, we set the default value of config.preview_urls to
false, but wewere accidentally disabling Preview URLs for users that only had
config.workers_dev=true.
Rather than defaulting config.preview_urls to
trueorfalse, wedefault to the resolved value of config.workers_dev. Should result in a
clearer user experience.
#11027
1a2bbf8Thanks @jamesopstad! - Statically replace the value ofprocess.env.NODE_ENVwithdevelopmentfor development builds andproductionfor production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based onprocess.env.NODE_ENVcan be properly tree shaken.#9705
0ee1a68Thanks @hiendv! - Add params type to Workflow type generation. E.g.#10867
dd5f769Thanks @austin-mc! - Add media binding supportPatch Changes
#11018
5124818Thanks @dario-piotrowicz! - Improve potential errors thrown bystartRemoteProxySessionby including more information#11019
6643bd4Thanks @dario-piotrowicz! - Fixobservability.logs.persistbeing flagged as an unexpected field during the wrangler config file validation#10768
8211bc9Thanks @dario-piotrowicz! - Update logs handling to use the newhandleStructuredLogsminiflare option#10997
3bb034fThanks @nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are setin the environment, then command failures will append a line to the output file
encoding the error code and message, if present.
#10986
43503c7Thanks @emily-shen! - fix: cleanup any running containers again on wrangler dev exit#11000
a6de9dbThanks @jonboulle! - always load container image into local store during buildBuildKit supports different build drivers. When using the more modern
docker-containerdriver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when callinggetImageRepoTags), it will thus fail, e.g.:Explicitly setting the
--loadflag (equivalent to-o type=docker) during the build fixes this and should make the build a bit more portable without requiring users to change their default build driver configuration.#10994
d39c8b5Thanks @pombosilva! - Make Workflows instances list command cursor based#10892
7d0417bThanks @dario-piotrowicz! - improve the diffing representation forwrangler deploy(run under--x-remote-diff-check)Updated dependencies [
36d7054,dd5f769,ee7d710,8211bc9]:v4.43.0Compare Source
Minor Changes
940b44dThanks @devin-ai-integration! - feat:wrangler init --from-dashnow generateswrangler.jsoncconfig files instead ofwrangler.tomlfilesPatch Changes
#10938
e52d0ecThanks @penalosa! - Acquire Cloudflare Access tokens for additional requests made during awrangler dev --remotesession#10923
2429533Thanks @emily-shen! - fix: updatedocker manifest inspectto use full image registry uri when checking if the image exists remotely#10521
88b5b7fThanks @penalosa! - Improves the Wrangler auto-provisioning feature (gated behind the experimental flag--x-provision) by:Configuration
📅 Schedule: Branch creation - "on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.