Skip to content

Update dependency wrangler to v4 #152

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
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency wrangler to v4 #152

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

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

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
wrangler (source) 3.53.1 -> 4.19.1 age adoption passing confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.19.1

Compare Source

Patch Changes

v4.19.0

Compare Source

Minor Changes
Patch Changes

v4.18.0

Compare Source

Minor Changes
Patch Changes

  • #​9308 d3a6eb3 Thanks @​dario-piotrowicz! - expose new utilities and types to aid consumers of the programmatic mixed-mode API

    Specifically the exports have been added:

    • Experimental_MixedModeSession: type representing a mixed-mode session
    • Experimental_ConfigBindingsOptions: type representing config-bindings
    • experimental_pickRemoteBindings: utility for picking only the remote bindings from a record of start-worker bindings.
    • unstable_convertConfigBindingsToStartWorkerBindings: utility for converting config-bindings into start-worker bindings (that can be passed to startMixedModeSession)

  • #​9347 b8f058c Thanks @​penalosa! - Improve binding display on narrower terminals

  • Updated dependencies [d9d937a, e39a45f, fdae3f7]:

    • miniflare@4.20250525.0

v4.17.0

Compare Source

Minor Changes

  • #​9321 6c03bde Thanks @​petebacondarwin! - Add support for FedRAMP High compliance region

    Now it is possible to target Wrangler at the FedRAMP High compliance region.
    There are two ways to signal to Wrangler to run in this mode:

    • set "compliance_region": "fedramp_high" in a Wrangler configuration
    • set CLOUDFLARE_COMPLIANCE_REGION=fedramp_high environment variable when running Wrangler

    If both are provided and the values do not match then Wrangler will exit with an error.

    When in this mode OAuth authentication is not supported.
    It is necessary to authenticate using a Cloudflare API Token acquired from the Cloudflare FedRAMP High dashboard.

    Most bindings and commands are supported in this mode.

    • Unsupported commands may result in API requests that are not supported - possibly 422 Unprocessable Entity responses.
    • Unsupported bindings may work in local dev, as there is no local validation, but will fail at Worker deployment time.

    Resolves DEVX-1921.

  • #​9330 34c71ce Thanks @​edmundhung! - Updated internal configuration to use Miniflare’s new defaultPersistRoot instead of per-plugin persist flags

  • #​8973 cc7fae4 Thanks @​Caio-Nogueira! - Show latest instance by default on workflows instances describe command

Patch Changes

v4.16.1

Compare Source

Patch Changes

v4.16.0

Compare Source

Minor Changes

  • #​9288 3b8f7f1 Thanks @​petebacondarwin! - allow --name and --env args on wrangler deploy

    Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
    Now specifying --name is supported and will override any names set in the Wrangler config:

    wrangler.json

    {
	"name": "config-worker"
	"env": {
		"staging": { "name": "config-worker-env" }
	}
}
    Command Previous (Worker name) Proposed (Worker name) Comment
    wrangler deploy --name=args-worker "args-worker" "args-worker" CLI arg used
    wrangler deploy --name=args-worker --env=staging Error "args-worker" CLI arg used
    wrangler deploy --name=args-worker --env=prod Error "args-worker" CLI arg used
    wrangler deploy "config-worker" "config-worker" Top-level config used
    wrangler deploy --env=staging "config-worker-env" "config-worker-env" Named env config used
    wrangler deploy --env=prod "config-worker-prod" "config-worker-prod" CLI arg and top-level config combined

  • #​9265 16de0d5 Thanks @​edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

  • #​9234 2fe6219 Thanks @​emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

  • #​9269 66d975e Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

    Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

    Also include the ai binding since the bindings is already remote by default anyways.

  • #​9151 5ab035d Thanks @​gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

  • #​9231 02d40ed Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

    Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

    Also include the ai binding since the bindings is already remote by default anyways.

  • #​9221 2ef31a9 Thanks @​vicb! - bump @cloudflare/unenv-preset

  • #​9277 db5ea8f Thanks @​penalosa! - Support Mixed Mode for more binding types

  • #​9266 f2a16f1 Thanks @​petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

  • #​9245 b87b472 Thanks @​penalosa! - Support Mixed Mode Dispatch Namespaces

  • Updated dependencies [db5ea8f, b87b472]:

    • miniflare@4.20250508.3

v4.15.2

Compare Source

Patch Changes

v4.15.1

Compare Source

Patch Changes

  • #​9248 07f4010 Thanks @​vicb! - fix unenv version mismatch

  • #​9219 ea71df3 Thanks @​vicb! - bump unenv to 2.0.0-rc.17

  • #​9246 d033a7d Thanks @​edmundhung! - fix: strip CF-Connecting-IP header within fetch

    In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

  • Updated dependencies [f61a08e, ea71df3, d033a7d]:

v4.15.0

Compare Source

Minor Changes

  • #​8794 02f0699 Thanks @​eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Fetcher;
}

    This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}

  • #​8716 63a6504 Thanks @​ItsWendell! - add --metafile flag to generate esbuild metadata file during build

  • #​9122 f17ee08 Thanks @​avenceslau! - Unhide wrangler workflows delete command

Patch Changes

v4.14.4

Compare Source

Patch Changes

  • #​9124 d0d62e6 Thanks @​dario-piotrowicz! - make that unstable_startWorker can correctly throw configuration errors

    make sure that unstable_startWorker can throw configuration related errors when:

    • the utility is called
    • the worker's setConfig is called with the throwErrors argument set to true

    additionally when an error is thrown when unstable_startWorker is called make sure
    that the worker is properly disposed (since, given the fact that it is not returned
    by the utility the utility's caller wouldn't have any way to dispose it themselves)

v4.14.3

Compare Source

Patch Changes

v4.14.2

Compare Source

Patch Changes

v4.14.1

Compare Source

Patch Changes

  • #​9085 cdc88d8 Thanks @​petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

    Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.

  • #​9095 508a1a3 Thanks @​petebacondarwin! - wrangler login put custom callback host and port into the auth URL

  • #​9113 82e220e Thanks @​dario-piotrowicz! - Add x-mixed-mode flag

    This experimental flag currently has no effect. More details will be shared as we roll out its functionality.

  • Updated dependencies [357d42a]:

    • miniflare@4.20250428.1

v4.14.0

Compare Source

Minor Changes
Patch Changes

v4.13.2

Compare Source

Patch Changes
  • Updated dependencies [2c50115]:
    • miniflare@4.20250424.1

v4.13.1

Compare Source

Patch Changes

v4.13.0

Compare Source

Minor Changes

  • #​8640 5ce70bd Thanks @​kentonv! - Add support for defining props on a Service binding.

    In your configuration file, you can define a service binding with props:

    {
	"services": [
		{
			"binding": "MY_SERVICE",
			"service": "some-worker",
			"props": { "foo": 123, "bar": "value" }
		}
	]
}

    These can then be accessed by the callee:

    import { WorkerEntrypoint } from "cloudflare:workers";

export default class extends WorkerEntrypoint {
	fetch() {
		return new Response(JSON.stringify(this.ctx.props));
	}
}

  • #​8771 0cfcfe0 Thanks @​dario-piotrowicz! - feat: add config.keep_names option

    Adds a new option to Wrangler to allow developers to opt out of esbuild's keep_names option (https://esbuild.github.io/api/#keep-names). By default, Wrangler sets this to true

    This is something developers should not usually need to care about, but sometimes
    keep_names can create issues, and in such cases they will be now able to opt-out.

    Example wrangler.jsonc:

    {
	"name": "my-worker",
	"main": "src/worker.ts",
	"keep_names": false
}
Patch Changes

v4.12.1

Compare Source

Patch Changes

v4.12.0

Compare Source

Minor Changes
Patch Changes

  • #​8889 eab7ad9 Thanks @​penalosa! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

  • #​8673 5de2b9a Thanks @​IRCody! - Add containers {info, list, delete} subcommands.

  • Updated dependencies [62c40d7]:

    • miniflare@4.20250416.0

v4.11.1

Compare Source

Patch Changes

v4.11.0

Compare Source

Minor Changes
Patch Changes

  • #​8885 f2802f9 Thanks @​CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message

  • #​8924 d2b44a2 Thanks @​dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on
    deploy commands when an environment is specified and a redirected configuration
    is in use (the reason being that redirected configurations should not include
    any environment), this check is problematic with pages commands where the
    "production" environment is anyways set by default, to address this the validation
    check is being relaxed here on pages commands

  • Updated dependencies [f5413c5]:

    • miniflare@4.20250410.0

v4.10.0

Compare Source

Minor Changes
Patch Changes

v4.9.1

Compare Source

Patch Changes
  • Updated dependencies [d454ad9]:
    • miniflare@4.20250408.0

v4.9.0

Compare Source

Minor Changes
Patch Changes

  • #​8809 09464a6 Thanks @​dario-piotrowicz! - improve error message when redirected config contains environments

    this 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

  • Updated dependencies [afd93b9, 930ebb2]:

    • miniflare@4.20250405.1

v4.8.0

Compare Source

Minor Changes
Patch Changes

  • #​8780 4e69fb6 Thanks @​cmackenzie1! - - Rename wrangler pipelines show to wrangler 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 from wrangler 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.

  • #​8596 75b454c Thanks @​dario-piotrowicz! - add validation to redirected configs in regards to environments

    add 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: Unhide wrangler 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.

  • Updated dependencies [93267cf, ec7e621]:

    • miniflare@4.20250405.0

v4.7.2

Compare Source

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 fails

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

  • Updated dependencies [e0efb6f, 0a401d0]:

    • miniflare@4.20250404.0

v4.7.1

Compare Source

Patch Changes

v4.7.0

Compare Source

Minor Changes
Patch Changes

v4.6.0

Compare Source

Minor Changes
Patch Changes

v4.5.1

Compare Source

Patch Changes

  • #​8666 f29f018 Thanks @​penalosa! - Remove NodeJSCompatModule. This was never fully supported, and never worked for deploying Workers from Wrangler.

  • Updated dependencies [cad99dc, f29f018]:

    • miniflare@4.20250321.1

v4.5.0

Compare Source

Minor Changes
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 3 times, most recently from c3d345e to 2a65e6a Compare May 20, 2025 11:59
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from b173683 to 491a751 Compare May 27, 2025 16:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 491a751 to 8426bf9 Compare May 29, 2025 14:34
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 8426bf9 to bd3684d Compare June 6, 2025 02:53
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.
0 participants