Skip to content

chore(deps): update dependency wrangler to v4 #555

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: trunk
Choose a base branch
from
Open

chore(deps): update dependency wrangler to v4 #555

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 Confidence
wrangler (source) 3.114.11 -> 4.25.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.25.0

Compare Source

Minor Changes
Patch Changes

v4.24.4

Compare Source

Patch Changes

v4.24.3

Compare Source

Patch Changes

  • #​9923 c01c4ee Thanks @​gpanders! - Fix image name resolution when modifying a container application

  • #​9833 3743896 Thanks @​dario-piotrowicz! - fix: ensure that container builds don't disrupt dev hotkey handling

    currently container builds run during local development (via wrangler dev or startWorker) prevent the standard hotkeys not to be recognized (most noticeably ctrl+c, preventing developers from existing the process), the changes here ensure that hotkeys are instead correctly handled as expected

  • Updated dependencies []:

v4.24.2

Compare Source

Patch Changes

v4.24.1

Compare Source

Patch Changes

  • #​9765 05adc61 Thanks @​hasip-timurtas! - Build container images without the user's account ID. This allows containers to be built and verified in dry run mode (where we do not necessarily have the user's account info).

    When we push the image to the managed registry, we first re-tag the image to include the user's account ID so that the image has the full resolved image name.

  • Updated dependencies [bb09e50, 25dbe54, 3bdec6b]:

v4.24.0

Compare Source

Minor Changes

  • #​9796 ba69586 Thanks @​simonabadoiu! - Browser Rendering local mode

  • #​9825 49c85c5 Thanks @​ReppCodes! - Add support for origin_connection_limit to Wrangler

    Configure connection limits to Hyperdrive via command line options:

    • --origin-connection-limit: The (soft) maximum number of connections that Hyperdrive may establish to the origin database.

  • #​9064 a1181bf Thanks @​sdnts! - Added an event-subscriptions subcommand

Patch Changes

  • #​9729 1b3a2b7 Thanks @​404Wolf! - Set docker build context to the Dockerfile directory when image_build_context is not explicitly provided

  • #​9845 dbfa4ef Thanks @​jonboulle! - remove extraneous double spaces from Wrangler help output

  • #​9811 fc29c31 Thanks @​gpanders! - Fix unauthorized errors on "containers images delete".

  • #​9813 45497ab Thanks @​gpanders! - Support container image names without account ID

  • #​9821 a447d67 Thanks @​WillTaylorDev! - Preview Aliases: Force alias generation to meet stricter naming requirements.

    For cases where CI is requesting Wrangler to generate the alias based on the branch name, we want a stricter check around the generated alias name in order to avoid version upload failures. If a valid alias name was not able to be generated, we warn and do not provide an alias (avoiding a version upload failure).

  • #​9840 7c55f9e Thanks @​dario-piotrowicz! - fix: make sure that the experimental remoteBindings flag is properly handled in getPlatformProxy

    There are two issues related to how the experimental remoteBindings flag is handled in getPlatformProxy that are being fixed by this change:

    • the experimental_remote configuration flag set on service bindings is incorrectly always taken into account, even if remoteBindings is set to false
    • the experimental_remote configuration flag of all the other bindings is never taken into account (effectively preventing the bindings to be used in remote mode) since the remoteBindings flag is not being properly propagated

  • #​9801 0bb619a Thanks @​IRCody! - Containers: Fix issue where setting an image URI instead of dockerfile would incorrectly not update the image

  • #​9872 a727db3 Thanks @​emily-shen! - fix: resolve Dockerfile path relative to the Wrangler config path

    This fixes a bug where Wrangler would not be able to find a Dockerfile if a Wrangler config path had been specified with the --config flag.

  • #​9815 1358034 Thanks @​gpanders! - Remove --json flag from containers and cloudchamber commands (except for "images list")

  • #​9734 1a58bc3 Thanks @​penalosa! - Make Wrangler warn more loudly if you're missing auth scopes

  • #​9748 7e3aa1b Thanks @​alsuren! - Internal-only WRANGLER_D1_EXTRA_LOCATION_CHOICES environment variable for enabling D1's testing location hints

  • Updated dependencies [ba69586, 1a75f85, 395f36d, 6f344bf]:

v4.23.0

Compare Source

Minor Changes

  • #​9535 56dc5c4 Thanks @​penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

    Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

  • #​9810 8acaf43 Thanks @​WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.

Patch Changes

v4.22.0

Compare Source

Minor Changes

  • #​7871 f2a8d4a Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

    this change makes sure that that getPlatformProxy, when the input configuration
    file contains an assets field, correctly returns the appropriate asset binding proxy

    example:

    // wrangler.jsonc
{
	"name": "my-worker",
	"assets": {
		"directory": "./public/",
		"binding": "ASSETS",
	},
}
    import { getPlatformProxy } from "wrangler";

const { env, dispose } = await getPlatformProxy();

const text = await (await env.ASSETS.fetch("http://0.0.0.0/file.txt")).text();
console.log(text); // logs the content of file.txt

await dispose();
Patch Changes

v4.21.2

Compare Source

Patch Changes

v4.21.1

Compare Source

Patch Changes

v4.21.0

Compare Source

Minor Changes
Patch Changes

  • #​9695 0e64c35 Thanks @​emily-shen! - Move hotkey registration later in dev start up

    This should have no functional change, but allows us to conditionally render hotkeys based on config.

  • #​9098 ef20754 Thanks @​jseba! - Migrate Workers Containers commands to Containers API Endpoints

    The Workers Containers API was built on top of Cloudchamber, but has now been moved to its own API
    with a reduced scoping and new token.

  • #​9712 2a4c467 Thanks @​emily-shen! - Make wrangler container commands print open-beta status

v4.20.5

Compare Source

Patch Changes

  • #​9688 086e29d Thanks @​dario-piotrowicz! - add remote bindings support to getPlatformProxy

    Example:

    // wrangler.jsonc
{
	"name": "get-platform-proxy-test",
	"services": [
		{
			"binding": "MY_WORKER",
			"service": "my-worker",
			"experimental_remote": true
		}
	]
}
    // index.mjs
import { getPlatformProxy } from "wrangler";

const { env } = await getPlatformProxy({
	experimental: {
		remoteBindings: true,
	},
});

// env.MY_WORKER.fetch() fetches from the remote my-worker service

  • #​9558 d5edf52 Thanks @​ichernetsky-cf! - wrangler containers apply uses observability configuration.

  • #​9678 24b2c66 Thanks @​dario-piotrowicz! - remove warnings during config validations on experimental_remote fields

    wrangler commands, run without the --x-remote-bindings flag, parsing config files containing experimental_remote fields currently show warnings stating that the field is not recognized. This is usually more cumbersome than helpful so here we're loosening up this validation and making wrangler always recognize the field even when no --x-remote-bindings flag is provided

  • #​9633 3f478af Thanks @​nikitassharma! - Add support for setting an instance type for containers in wrangler. This allows users to configure memory, disk, and vCPU by setting instance type when interacting with containers.

  • #​9596 5162c51 Thanks @​CarmenPopoviciu! - add ability to pull images for containers local dev

  • Updated dependencies [bfb791e, 5162c51]:

v4.20.4

Compare Source

Patch Changes

v4.20.3

Compare Source

Patch Changes

v4.20.2

Compare Source

Patch Changes

v4.20.1

Compare Source

Patch Changes

v4.20.0

Compare Source

Minor Changes
Patch Changes

v4.19.2

Compare Source

Patch Changes

  • #​9461 66edd2f Thanks @​skepticfx! - Enforce disk limits on container builds

  • #​9481 d1a1787 Thanks @​WillTaylorDev! - Force autogenerated aliases to be fully lowercased.

  • #​9480 1f84092 Thanks @​dario-piotrowicz! - add experimentalMixedMode dev option to unstable_startWorker

    add an new experimentalMixedMode dev option to unstable_startWorker
    that allows developers to programmatically start a new mixed mode
    session using startWorker.

    Example usage:

    // index.mjs
import { unstable_startWorker } from "wrangler";

await unstable_startWorker({
	dev: {
		experimentalMixedMode: true,
	},
});
    // wrangler.jsonc
{
	"$schema": "node_modules/wrangler/config-schema.json",
	"name": "programmatic-start-worker-example",
	"main": "src/index.ts",
	"compatibility_date": "2025-06-01",
	"services": [
		{ "binding": "REMOTE_WORKER", "service": "remote-worker", "remote": true }
	]
}

  • Updated dependencies [4ab5a40, 485cd08, e3b3ef5, 3261957]:

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]:

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 bi

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.

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 13, 2025 •
edited
Loading

size-limit report 📦

Path Size
src/_worker.ts 6.73 KB (0%)

@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 8 times, most recently from c81b62f to 61d49a9 Compare March 21, 2025 02:10
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 9 times, most recently from c370a91 to 6d156e7 Compare March 28, 2025 02:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 9 times, most recently from ebeecb1 to 69188a7 Compare April 4, 2025 10:06
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from b2a5082 to 5afdbd1 Compare April 5, 2025 05:47
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 8 times, most recently from 8ef75b6 to 1e286aa Compare July 1, 2025 07:42
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 8 times, most recently from c0b270b to 9e88389 Compare July 8, 2025 13:55
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 9 times, most recently from 48a60f1 to e22ab9b Compare July 15, 2025 07:33
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 4fb8028 to 78e60fd Compare July 18, 2025 07:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 78e60fd to 25c0655 Compare July 19, 2025 05: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