Skip to content

Update dependency wrangler to v4 #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency wrangler to v4 #8

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) ^3.47.1 -> ^4.0.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.54.0

Compare Source

Minor Changes

  • #​11512 c15e99e Thanks @​emily-shen! - Enable using ctx.exports with containers

    You can now use containers with Durable Objects that are accessed via ctx.exports.

    Now your config file can look something like this:

    {
	"name": "container-app",
	"main": "src/index.ts",
	"compatibility_date": "2025-12-01",
	"compatibility_flags": ["enable_ctx_exports"], // compat flag needed for now.
	"containers": [
		{
			"image": "./Dockerfile",
			"class_name": "MyDOClassname",
			"name": "my-container"
		},
	],
	"migrations": [
		{
			"tag": "v1",
			"new_sqlite_classes": ["MyDOClassname"],
		},
	],
	// no need to declare your durable object binding here
}

    Note that when using ctx.exports, where you previously accessed a Durable Object via something like env.DO, you should now access with ctx.exports.MyDOClassname.

    Refer to the docs for more information on using ctx.exports.

  • #​11508 b17797c Thanks @​dario-piotrowicz! - Wrangler will no longer try to add additional configuration to projects using @cloudflare/vite-plugin when deploying or running wrangler setup

  • #​11508 b17797c Thanks @​dario-piotrowicz! - When a Vite project is detected, install @cloudflare/vite-plugin

  • #​11576 bb47e20 Thanks @​dario-piotrowicz! - Support Analog projects in autoconfig

  • #​10582 991760d Thanks @​flakey5! - Add containers ssh command

Patch Changes

v4.53.0

Compare Source

Minor Changes

  • #​11500 af54c63 Thanks @​dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

    This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

    Note: the field is experimental and could change while autoconfig is not GA

  • #​11477 9988cc9 Thanks @​ascorbic! - Support Nuxt in autoconfig

  • #​11472 ce295bf Thanks @​dario-piotrowicz! - Support Qwik projects in autoconfig

  • #​10937 9514c9a Thanks @​ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

    This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:

    • region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
    • host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
    • hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource

    These fields are mutually exclusive - only one can be specified at a time.

    Example configuration:

    [placement]
host = "example.com:8123"

  • #​11498 ac861f8 Thanks @​penalosa! - Add React Router support in autoconfig

  • #​11506 79d30d4 Thanks @​vicb! - Set the target JS version to ES2024

Patch Changes

v4.52.1

Compare Source

Patch Changes

v4.52.0

Compare Source

Minor Changes

  • #​11416 abe49d8 Thanks @​dario-piotrowicz! - Remove the wrangler deploy's --x-remote-diff-check experimental flag

    The remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.

  • #​11408 f29e699 Thanks @​ascorbic! - Export unstable helpers useful for generating wrangler config

  • #​11389 2342d2f Thanks @​dario-piotrowicz! - Improve the wrangler deploy flow to also check for potential overrides of secrets.

    Now when you run wrangler deploy Wrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.

  • #​11375 9a1de61 Thanks @​penalosa! - Support TanStack Start in autoconfig

  • #​11360 6b38532 Thanks @​emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

    Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

    Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your config file.

    The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.

  • #​11009 e4ddbc2 Thanks @​dario-piotrowicz! - Allow users to provide an account_id as part of the WorkerConfigObject they pass to maybeStartOrUpdateRemoteProxySession

  • #​11478 2aec2b4 Thanks @​dario-piotrowicz! - Support SolidStart in autoconfig

  • #​11330 5a873bb Thanks @​dario-piotrowicz! - Support Angular projects in autoconfig

  • #​11449 e7b690b Thanks @​penalosa! - Delegate generation of HTTPS certificates to Miniflare

  • #​11448 2b4813b Thanks @​edmundhung! - Bumps esbuild version to 0.27.0

  • #​11335 c47ad11 Thanks @​dario-piotrowicz! - Support internal-only undocumented cross_account_grant service binding property

  • #​11346 a977701 Thanks @​penalosa! - We're soon going to make backend changes that mean that wrangler dev --remote sessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a new wrangler tail-based logging strategy for wrangler dev --remote. For now, you can revert to the previous logging strategy with wrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.

    The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.

Patch Changes

  • #​11397 b154de2 Thanks @​vicb! - Use more workerd native modules

    Node modules punycode, trace_events, cluster, wasi, and domains will be used when enabled
    via a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.

  • #​11452 76f0540 Thanks @​penalosa! - Remove uses of eval() from the Wrangler bundle

  • #​11284 695fa25 Thanks @​dom96! - Removes duplicate module warnings when vendoring Python packages

  • #​11249 504e258 Thanks @​dario-piotrowicz! - fix: Generalize autoconfig wording

    Generalize the autoconfig wording so that when it doesn't specifically mention "deployment" (since it can be run via wrangler setup or the autoconfig programmatic API)

  • #​11455 d25f7e2 Thanks @​dario-piotrowicz! - Fix autoconfig using absolute paths for static projects

    Running the experimental autoconfig logic through wrangler setup and wrangler deploy --x-autoconfig on a static project results in absolute paths being used. This is incorrect, especially when such paths are being included in the generated wrangler.jsonc. The changes here fix the autoconfig logic to use paths relative to the project's root instead.

    For example given a project located in /Users/usr/projects/sites/my-static-site, before:

    // wrangler.jsonc at /Users/usr/projects/sites/my-static-site
  {
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "static",
    "compatibility_date": "2025-11-27",
    "observability": {
      "enabled": true
    },
    "assets": {
      "directory": "/Users/usr/projects/sites/my-static-site/public"
    }
  }

    and after:

    // wrangler.jsonc at /Users/usr/projects/sites/my-static-site
  {
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "static",
    "compatibility_date": "2025-11-27",
    "observability": {
      "enabled": true
    },
    "assets": {
      "directory": "public"
    }
  }

  • #​11484 1cfae2d Thanks @​edmundhung! - Explicitly close FileHandle in wrangler d1 execute to support Node 25

  • #​11383 1d685cb Thanks @​dario-piotrowicz! - Fix: ensure that when a remote proxy session creation fails a hard error is surfaced to the user (both in wrangler dev and in the programmatic API).

    When using remote bindings, either with wrangler dev or via startRemoteProxySession/maybeStartOrUpdateRemoteProxySession the remote proxy session necessary to connect to the remote resources can fail to be created, this might happen if for example you try to set a binding with some invalid values such as:

    MY_R2: {
	type: "r2_bucket",
	bucket_name: "non-existent", // No bucket called "non-existent" exists
	remote: true,
},

    Before this could go undetected and cause unwanted behaviors such as requests handling hanging indefinitely, now wrangler will instead crash (or throw a hard error ion the programmatic API), clearly indicating that something went wrong during the remote session's creation.

  • #​11366 edf896d Thanks @​ascorbic! - Use correctly-formatted names when displaying detected framework details

  • #​11461 9eaa9e2 Thanks @​dario-piotrowicz! - Update the structure of the configure method of autoconfig frameworks

    Update the signature of the configure function of autoconfig frameworks (AutoconfigDetails#Framework), before they would return a RawConfig object to use to update the project's wrangler config file, now they return an object that includes the RawConfig and that can potentially also hold additional data relevant to the configuration.

  • Updated dependencies [2b4813b, b154de2, 5ee3780, 6e63b57, 71ab562, 5e937c1]:

v4.51.0

Compare Source

Minor Changes

  • #​11345 d524e55 Thanks @​penalosa! - Enable experimental support for autoconfig-powered Astro projects

  • #​11228 43903a3 Thanks @​petebacondarwin! - Support CLOUDFLARE_ENV environment variable for selecting the active environment

    This change enables users to select the environment for commands such as CLOUDFLARE_ENV=prod wrangler versions upload. The --env command line argument takes precedence.

    The CLOUDFLARE_ENV environment variable is mostly used with the @cloudflare/vite-plugin to select the environment for building the Worker to be deployed. This build also generates a "redirected deploy config" that is flattened to only contain the active environment.
    To avoid accidentally deploying a version that is built for one environment to a different environment, there is an additional check to ensure that if the user specifies an environment in Wrangler it matches the original selected environment from the build.

Patch Changes

v4.50.0

Compare Source

Minor Changes

  • #​11219 524a6e5 Thanks @​Ltadrian! - Implement Hyperdrive binding TLS miniflare proxy. This will allow for wrangler dev hyperdrive bindings to connect to external
    databases that require TLS.

  • #​11233 c922a81 Thanks @​emily-shen! - Add containers.unsafe to allow internal users to use additional container features

Patch Changes

v4.49.1

Compare Source

Patch Changes

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

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 3 times, most recently from abecd31 to 1bb596f Compare July 28, 2025 18:25
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 4bb912e to a7fb2d1 Compare August 5, 2025 09:58
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 730d399 to 7c901c7 Compare August 13, 2025 16:41
@renovate renovate bot mentioned this pull request Aug 14, 2025
Open
1 task
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 156672a to e0c53bf Compare August 21, 2025 16:36
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 611aca4 to 54d78e2 Compare August 28, 2025 17:40
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 8adbdd4 to 91bc601 Compare September 9, 2025 14:47
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from e24c9dd to 486333f Compare September 18, 2025 17:26
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 5 times, most recently from 9c50ebb to e573f02 Compare September 30, 2025 14:39
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 1bf7a62 to 666cfdf Compare October 3, 2025 16:48
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 0e0869c to f94920c Compare October 9, 2025 18:07
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 2ed66dc to 0bda52b Compare October 21, 2025 10:38
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 9d97bc8 to 5c92e27 Compare October 28, 2025 13:04
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 4dd1409 to a3e3aba Compare November 4, 2025 20:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 9a8b5f7 to 40ddccd Compare November 11, 2025 16:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from a3380e0 to 986fddb Compare November 20, 2025 14:06
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 1f941af to 9968b9d Compare November 26, 2025 17:32
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 782063f to a75e437 Compare December 4, 2025 21:36
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from a75e437 to 9caaf6a Compare December 11, 2025 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant