Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2025

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 3.53.1 -> 4.46.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

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 file (not necessary, but can make it resilient to binding name changes)
    • Fixing --dry-run, which previously threw an error when your config file had auto provisioned resources
    • Improve R2 bindings display to include the bucket_name from the config file on upload
    • Fixing bindings view for specific versions to not display TOML

v4.42.2

Compare Source

Patch Changes
  • #​10881 ce832d5 Thanks @​garvit-gupta! - Add table-level compaction commands for R2 Data Catalog:

    • wrangler r2 bucket catalog compaction enable <bucket> [namespace] [table]
    • wrangler r2 bucket catalog compaction disable <bucket> [namespace] [table]

    This allows you to enable and disable automatic file compaction for a specific R2 data catalog table.

  • #​10888 d0ab919 Thanks @​lrapoport-cf! - Clarify that wrangler check startup generates a local CPU profile

  • Updated dependencies [42e256f, 4462bc1]:

    • miniflare@​4.20251008.0

v4.42.1

Compare Source

Patch Changes

v4.42.0

Compare Source

Minor Changes
Patch Changes

v4.41.0

Compare Source

Minor Changes
  • #​10507 21a0bef Thanks @​dario-piotrowicz! - Add strict mode for the wrangler deploy command

    Add a new flag: --strict that makes the wrangler deploy command be more strict and not deploy workers when the deployment could be potentially problematic. This "strict mode" currently only affects non-interactive sessions where conflicts with the remote settings for the worker (for example when the worker has been re-deployed via the dashboard) will cause the deployment to fail instead of automatically overriding the remote settings.

  • #​10710 7f2386e Thanks @​penalosa! - Add prompt to resource creation flow allowing for newly created resources to be remote.

Patch Changes

v4.40.3

Compare Source

Patch Changes

v4.40.2

Compare Source

Patch Changes

v4.40.1

Compare Source

Patch Changes

v4.40.0

Compare Source

Minor Changes
  • #​10743 a7ac751 Thanks @​jonesphillip! - Changes --fileSizeMB to --file-size for wrangler r2 bucket catalog compaction command.
    Small fixes for pipelines commands.
Patch Changes
  • #​10706 81fd733 Thanks @​1000hz! - Fixed an issue that caused some Workers to have an incorrect service tag applied when using a redirected configuration file (as used by the Cloudflare Vite plugin). This resulted in these Workers not being correctly grouped with their sibling environments in the Cloudflare dashboard.

  • Updated dependencies [06e9a48]:

    • miniflare@​4.20250924.0

v4.39.0

Compare Source

Minor Changes
  • #​10647 555a6da Thanks @​efalcao! - VPC service binding support

  • #​10612 97a72cc Thanks @​jonesphillip! - Added new pipelines commands (pipelines, streams, sinks, setup), moved old pipelines commands behind --legacy

  • #​10652 acd48ed Thanks @​edmundhung! - Rename Hyperdrive local connection string environment variable from WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME> to CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME>. The old variable name is still supported but will now show a deprecation warning.

  • #​10721 55a10a3 Thanks @​penalosa! - Stabilise Worker Loader bindings

Patch Changes

v4.38.0

Compare Source

Minor Changes
Patch Changes

v4.37.1

Compare Source

Patch Changes
  • #​10658 3029b9a Thanks @​1000hz! - Fixed an issue with service tags not being applied properly to Workers when the Wrangler configuration file did not include a top-level name property.

  • #​10657 31ec996 Thanks @​penalosa! - Disable remote bindings with the --local flag

  • Updated dependencies [783afeb]:

    • miniflare@​4.20250913.0

v4.37.0

Compare Source

Minor Changes
  • #​10546 d53a0bc Thanks @​1000hz! - On deploy or version upload, Workers with multiple environments are tagged with metadata that groups them together in the Cloudflare Dashboard.

  • #​10596 735785e Thanks @​penalosa! - Add Miniflare & Wrangler support for unbound Durable Objects

  • #​10622 15c34e2 Thanks @​nagraham! - Modify R2 Data Catalog compaction commands to enable/disable for Catalog (remove table/namespace args), and require Cloudflare API token on enable.

Patch Changes
  • Updated dependencies [735785e]:
    • miniflare@​4.20250906.2

v4.36.0

Compare Source

Minor Changes
Patch Changes

v4.35.0

Compare Source

Minor Changes
  • #​10491 5cb806f Thanks @​zebp! - Add traces, OTEL destinations, and configurable persistence to observability settings

    Adds a new traces field to the observability settings in your Worker configuration that configures the behavior of automatic tracing. Both traces and logs support providing a list of OpenTelemetry compliant destinations where your logs/traces will be exported to as well as an implicitly-enabled persist option that controls whether or not logs/traces are persisted to the Cloudflare observability platform and viewable in the Cloudflare dashboard.

Patch Changes

v4.34.0

Compare Source

Minor Changes
  • #​10478 cc47b51 Thanks @​danielrs! - Beta feature preview_urls is now disabled by default.

    This change makes preview_urls disabled by default when it's not provided, making
    the feature opt-in instead of opt-out.

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from ccff204 to 1432fda Compare March 22, 2025 17:23
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 075e98f to 60c5f71 Compare March 28, 2025 15:26
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 6 times, most recently from 5256a14 to 4730e2a Compare April 8, 2025 23:21
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from d5c854a to b6a5fce Compare April 17, 2025 07:06
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 1a70cb3 to a82f4af Compare April 25, 2025 13:49
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 182af2f to 36b6f4e Compare May 6, 2025 10:32
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 2756402 to 6683383 Compare May 13, 2025 13:51
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 38d9643 to 402abf6 Compare August 18, 2025 18:12
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 7412c67 to 06de7ac Compare August 28, 2025 13:06
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 83bc938 to 2534039 Compare September 6, 2025 18:23
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from bf28ea4 to df601ed Compare September 15, 2025 02:10
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 0d22c55 to 425da8b Compare September 18, 2025 18:14
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 5 times, most recently from 44d1ab3 to f04f0aa Compare September 30, 2025 15:01
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from d44e2f3 to 6c172da Compare October 9, 2025 16:43
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 6c172da to 0bdd986 Compare October 14, 2025 18:39
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 09e2bc4 to 4cf9e2e Compare October 28, 2025 09:53
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from ed987d4 to 08ceb1f Compare November 4, 2025 21:03
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 08ceb1f to 9dfede3 Compare November 6, 2025 17:06
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