Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2025

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/workers-types 4.20250801.0 -> 4.20251118.0 age confidence
wrangler (source) 4.27.0 -> 4.49.0 age confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20251118.0

Compare Source

v4.20251117.0

Compare Source

v4.20251115.0

Compare Source

v4.20251113.0

Compare Source

v4.20251111.0

Compare Source

v4.20251109.0

Compare Source

v4.20251107.0

Compare Source

v4.20251106.1

Compare Source

v4.20251014.0

Compare Source

v4.20251011.0

Compare Source

v4.20251008.0

Compare Source

v4.20251004.0

Compare Source

v4.20251003.0

Compare Source

v4.20251001.0

Compare Source

v4.20250927.0

Compare Source

v4.20250926.0

Compare Source

v4.20250924.0

Compare Source

v4.20250923.0

Compare Source

v4.20250922.0

Compare Source

v4.20250921.0

Compare Source

v4.20250920.0

Compare Source

v4.20250919.0

Compare Source

v4.20250918.0

Compare Source

v4.20250917.0

Compare Source

v4.20250913.0

Compare Source

v4.20250912.0

Compare Source

v4.20250911.0

Compare Source

v4.20250910.0

Compare Source

v4.20250909.0

Compare Source

v4.20250906.0

Compare Source

v4.20250905.0

Compare Source

v4.20250904.0

Compare Source

v4.20250903.0

Compare Source

v4.20250902.0

Compare Source

v4.20250831.0

Compare Source

v4.20250830.0

Compare Source

v4.20250829.0

Compare Source

v4.20250828.1

Compare Source

v4.20250828.0

Compare Source

v4.20250826.0

Compare Source

v4.20250823.0

Compare Source

v4.20250822.0

Compare Source

v4.20250821.0

Compare Source

v4.20250820.0

Compare Source

v4.20250819.0

Compare Source

v4.20250816.0

Compare Source

v4.20250813.0

Compare Source

v4.20250812.0

Compare Source

v4.20250810.0

Compare Source

v4.20250809.0

Compare Source

v4.20250807.0

Compare Source

v4.20250806.0

Compare Source

v4.20250805.0

Compare Source

v4.20250803.0

Compare Source

v4.20250802.0

Compare Source

cloudflare/workers-sdk (wrangler)

v4.49.0

Compare Source

Minor Changes
  • #​10703 c5c4ee5 Thanks @​danlapid! - Add support for streaming tail consumers in local dev. This is an experimental new feature that allows you to register a tailStream() handler (compared to the existing tail() handler), which will receive streamed tail events from your Worker (compared to the tail() handler, which only receives batched events after your Worker has finished processing).

  • #​11251 7035804 Thanks @​penalosa! - When the WRANGLER_HIDE_BANNER environment variable is provided, Wrangler will no longer display a version banner. This applies to all commands.

    For instance, previously running wrangler docs would give the following output:

    > wrangler docs
     ⛅️ wrangler 4.47.0
    ───────────────────
    Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/
    

    With WRANGLER_HIDE_BANNER, this is now:

    > WRANGLER_HIDE_BANNER=true wrangler docs
    Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/
    
  • #​11285 d014fa7 Thanks @​vicb! - Implement the wrangler r2 bulk put bucket-name --filename list.json command.

    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).

    [
      { "key": "/path/to/obj", "file": "/path/to/file_1"},
      { "key": "/path/to/other/obj", "file": "/path/to/file_2"},
      // ...
    ]
    

    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 --pipe and plus --concurrency

  • #​11268 15b8460 Thanks @​penalosa! - Support SvelteKit projects in autoconfig

  • #​11258 2011b6a Thanks @​dario-piotrowicz! - Add --dry-run flag to wrangler setup and also a dryRun option to runAutoConfig

Patch Changes

v4.48.0

Compare Source

Minor Changes
  • #​11212 3908162 Thanks @​dario-piotrowicz! - Add autoconfig changes summary for wrangler deploy --x-autoconfig with the option for users to cancel the operation

  • #​11229 14d79f2 Thanks @​dario-piotrowicz! - Enables experimental-deploy-remote-diff-check flag 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 dfc6513 Thanks @​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

v4.47.0

Compare Source

Minor Changes
  • #​11201 5286309 Thanks @​avenceslau! - Add wrangler workflows instances restart command

  • #​11214 5cf8a39 Thanks @​penalosa! - Add the experimental wrangler setup command to run autoconfig outside of the deploy flow.

  • #​11187 8abc789 Thanks @​dario-piotrowicz! - Add possibility for users to edit their project settings during autoconfig

    When 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 settings

Patch Changes

v4.46.0

Compare Source

Minor Changes
Patch Changes
  • #​11160 05440a1 Thanks @​dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when running wrangler deploy --env <TARGET_ENV>

    When running wrangler deploy, with --x-remote-diff-check and 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|-e flag). Now this will also apply when an environment is targeted.

  • #​11162 c3ed531 Thanks @​dario-piotrowicz! - Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it

  • #​11162 c3ed531 Thanks @​dario-piotrowicz! - Fix bindings with remote: true being logged as remote when run via wrangler dev --local

  • Updated dependencies [1ae020d]:

    • miniflare@​4.20251105.0

v4.45.4

Compare Source

Patch Changes
  • #​11133 8ffbd17 Thanks @​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 77ed7e2 Thanks @​dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when running wrangler deploy

    When 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 bb00f9d Thanks @​devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally

  • #​11135 ed666a1 Thanks @​penalosa! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.

  • #​11149 22f25fd Thanks @​penalosa! - Add no-op autoconfig logic behind an experimental flag

  • Updated dependencies [90a2566, 14f60e8]:

v4.45.3

Patch Changes
  • #​11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

    D1 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 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

    The object that holds the environment variables in process.env does not care about the case of its keys
    in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

    Previously, when merging fields from .env files we were replacing this native object with a vanilla
    JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
    when in reality they just had different casing.

v4.45.2

Patch Changes

v4.45.1

Compare Source

Patch Changes

v4.45.0

Compare Source

Minor Changes
  • #​11030 1a8088a Thanks @​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-provision flag. 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 dev will automatically create these resources for you locally, and when you next run wrangler deploy Wrangler 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 4bd4c29 Thanks @​danielrs! - Better Wrangler subdomain defaults warning.

    Improves the warnings that we show users when either worker_dev or preview_urls are missing.

  • #​10927 31e1330 Thanks @​dom96! - Implements python_modules.excludes wrangler config field

    [python_modules]
    excludes = ["**/*.pyc", "**/__pycache__"]
  • #​10741 2f57345 Thanks @​penalosa! - Remove obsolete --x-remote-bindings flag

  • Updated dependencies [ca6c010]:

    • miniflare@​4.20251011.1

v4.44.0

Compare Source

Minor Changes
  • #​10939 d4b4c90 Thanks @​danielrs! - Config preview_urls defaults to workers_dev value.

    Originally, we were defaulting config.preview_urls to true, but we
    were 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 we
    were accidentally disabling Preview URLs for users that only had
    config.workers_dev=true.

    Rather than defaulting config.preview_urls to true or false, we
    default to the resolved value of config.workers_dev. Should result in a
    clearer user experience.

  • #​11027 1a2bbf8 Thanks @​jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

  • #​9705 0ee1a68 Thanks @​hiendv! - Add params type to Workflow type generation. E.g.

    interface Env {
    	MY_WORKFLOW: Workflow<
    		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
    	>;
    }
  • #​10867 dd5f769 Thanks @​austin-mc! - Add media binding support

Patch Changes
  • #​11018 5124818 Thanks @​dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information

  • #​11019 6643bd4 Thanks @​dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

  • #​10768 8211bc9 Thanks @​dario-piotrowicz! - Update logs handling to use the new handleStructuredLogs miniflare option

  • #​10997 3bb034f Thanks @​nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are set
    in the environment, then command failures will append a line to the output file
    encoding the error code and message, if present.

  • #​10986 43503c7 Thanks @​emily-shen! - fix: cleanup any running containers again on wrangler dev exit

  • #​11000 a6de9db Thanks @​jonboulle! - always load container image into local store during build

    BuildKit supports different build drivers. When using the more modern docker-container driver (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 calling getImageRepoTags), it will thus fail, e.g.:

    ⎔ Preparing container image(s)...
    [+] Building 0.3s (8/8) FINISHED                                                                                                                                                                                                     docker-container:default
    
    [...]
    
    WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
    
    ✘ [ERROR] failed inspecting image locally: Error response from daemon: failed to find image cloudflare-dev/sandbox:f86e40e4: docker.io/cloudflare-dev/sandbox:f86e40e4: No such image
    
    

    Explicitly setting the --load flag (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 d39c8b5 Thanks @​pombosilva! - Make Workflows instances list command cursor based

  • #​10892 7d0417b Thanks @​dario-piotrowicz! - improve the diffing representation for wrangler deploy (run under --x-remote-diff-check)

  • Updated dependencies [36d7054, dd5f769, ee7d710, 8211bc9]:

v4.43.0

Compare Source

Minor Changes
Patch Changes
  • #​10938 e52d0ec Thanks @​penalosa! - Acquire Cloudflare Access tokens for additional requests made during a wrangler dev --remote session

  • #​10923 2429533 Thanks @​emily-shen! - fix: update docker manifest inspect to use full image registry uri when checking if the image exists remotely

  • #​10521 88b5b7f Thanks @​penalosa! - Improves the Wrangler auto-provisioning feature (gated behind the experimental flag --x-provision) by:

    • Writing back changes to the user's config f

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.


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

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

@renovate renovate bot force-pushed the renovate/cloudflare branch 4 times, most recently from 4b4c18e to 12da018 Compare September 6, 2025 03:48
@renovate renovate bot force-pushed the renovate/cloudflare branch 3 times, most recently from 0041cd8 to 948f984 Compare September 15, 2025 03:41
@renovate renovate bot force-pushed the renovate/cloudflare branch 7 times, most recently from d40309d to 2518c42 Compare September 24, 2025 08:08
@renovate renovate bot force-pushed the renovate/cloudflare branch 7 times, most recently from b079dea to 8444f46 Compare October 2, 2025 07:07
@renovate renovate bot force-pushed the renovate/cloudflare branch 8 times, most recently from f0fad17 to 34bf474 Compare October 9, 2025 18:15
@renovate renovate bot force-pushed the renovate/cloudflare branch from 34bf474 to 55c66f9 Compare October 11, 2025 01:52
@renovate renovate bot force-pushed the renovate/cloudflare branch 2 times, most recently from c4d61b6 to 29a9cf4 Compare October 20, 2025 21:35
@renovate renovate bot force-pushed the renovate/cloudflare branch 3 times, most recently from 3593e85 to e5d8ad9 Compare October 28, 2025 08:35
@renovate renovate bot force-pushed the renovate/cloudflare branch 3 times, most recently from e21fbb8 to 7e969ea Compare November 4, 2025 13:10
@renovate renovate bot force-pushed the renovate/cloudflare branch 5 times, most recently from 88bc8a1 to 29013a4 Compare November 11, 2025 15:55
@renovate renovate bot force-pushed the renovate/cloudflare branch 5 times, most recently from c453c26 to 372d0cb Compare November 18, 2025 05:55
@renovate renovate bot force-pushed the renovate/cloudflare branch from 372d0cb to 9e231f6 Compare November 18, 2025 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant