Skip to content

chore(deps): update dependency wrangler to v4.27.0 #621

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

chore(deps): update dependency wrangler to v4.27.0 #621

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 23, 2025 •
edited
Loading

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v4.27.0

Compare Source

Minor Changes

  • #​9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

    If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode,
    they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

    These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
    Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

    Further details:

    • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
    • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
    • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
    • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
    • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.
Patch Changes

  • #​10051 0f7820e Thanks @​nikitassharma! - Add support for custom instance limits for containers. For example, instead of
    having to use the preconfigured dev/standard/basic instance types, you can now
    set:

    instance_type: {
  vcpu: 1,
  memory_mib: 1024,
  disk_mb: 4000
}

    This feature is currently only available to customers on an enterprise plan.

  • #​10149 e9bb8d3 Thanks @​vicb! - fix require("debug") in nodejs_compat mode

  • Updated dependencies [9b61f44]:

v4.26.1

Compare Source

Patch Changes

  • #​10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

    Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

    In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

  • #​10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

  • #​10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

  • #​9897 755a249 Thanks @​edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint

  • Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

v4.26.0

Compare Source

Minor Changes

  • #​10016 c5b291d Thanks @​emily-shen! - Interactively handle wrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.

    For example:

    npx wrangler deploy ./public will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    npx wrangler deploy --assets=./public will now ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    In non-interactive contexts, Wrangler will error as it currently does.

  • #​9971 19794bf Thanks @​edmundhung! - Improved script source display on the pretty error screen

Patch Changes

  • #​9800 3d4f946 Thanks @​helloimalastair! - remove banner from r2 getobject in pipe mode

  • #​9910 7245101 Thanks @​dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is ready

    fix the fact that when starting a local (or remote) dev session the log saying Ready on http://localhost:xxxx could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)

  • #​10031 823cba8 Thanks @​vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

  • #​10032 154acf7 Thanks @​dario-piotrowicz! - add support for containers in wrangler multiworker dev

    currently when running wrangler dev with different workers (meaning that the -c|--config flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.

  • #​9988 7fb0bfd Thanks @​penalosa! - Correctly label mtls remote bindings warning

  • Updated dependencies [823cba8, 19794bf, 059a39e]:

v4.25.1

Compare Source

Patch Changes

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 Change

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 Apr 23, 2025 •
edited
Loading

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 3.58% 511 / 14259
🔵 Statements 3.58% 511 / 14259
🔵 Functions 38.87% 131 / 337
🔵 Branches 59.81% 189 / 316
File CoverageNo changed files found.
Generated in workflow #1456 for commit acd474a by the Vitest Coverage Report Action

@cloudflare-workers-and-pages Cloudflare Workers and Pages
Copy link

cloudflare-workers-and-pages bot commented Apr 23, 2025 •
edited
Loading

Deploying sos25-client with  Cloudflare Pages  Cloudflare Pages

Latest commit: acd474a
Status: ✅  Deploy successful!
Preview URL: https://c146d308.sos25-client.pages.dev
Branch Preview URL: https://renovate-wrangler-4-x-lockfi.sos25-client.pages.dev

View logs

@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from cd93782 to c3aea06 Compare April 23, 2025 16:06
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.12.1 chore(deps): update dependency wrangler to v4.13.0 Apr 23, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from c3aea06 to 525495b Compare April 24, 2025 19:50
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.13.0 chore(deps): update dependency wrangler to v4.13.1 Apr 24, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 525495b to 6c876a2 Compare April 25, 2025 11:47
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.13.1 chore(deps): update dependency wrangler to v4.13.2 Apr 25, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 6c876a2 to 2d3f962 Compare April 29, 2025 23:04
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.13.2 chore(deps): update dependency wrangler to v4.14.0 Apr 29, 2025
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.14.0 chore(deps): update dependency wrangler to v4.13.2 Apr 30, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 2d3f962 to 07e9425 Compare April 30, 2025 19:57
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 07e9425 to 50b2317 Compare May 1, 2025 19:21
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.13.2 chore(deps): update dependency wrangler to v4.14.1 May 1, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 50b2317 to e9b7474 Compare May 6, 2025 10:49
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.14.1 chore(deps): update dependency wrangler to v4.14.2 May 6, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from e9b7474 to 90255e6 Compare May 6, 2025 20:08
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.14.2 chore(deps): update dependency wrangler to v4.14.1 May 6, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 90255e6 to be12a1c Compare May 7, 2025 16:15
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.14.1 chore(deps): update dependency wrangler to v4.14.3 May 7, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 30e69ea to e9cbf4c Compare July 8, 2025 12:00
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.23.0 chore(deps): update dependency wrangler to v4.24.0 Jul 8, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from e9cbf4c to 45e5a51 Compare July 10, 2025 12:07
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.24.0 chore(deps): update dependency wrangler to v4.24.1 Jul 10, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 45e5a51 to fac103c Compare July 10, 2025 16:33
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.24.1 chore(deps): update dependency wrangler to v4.24.0 Jul 10, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from fac103c to be945fb Compare July 10, 2025 22:14
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.24.0 chore(deps): update dependency wrangler to v4.24.3 Jul 10, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from be945fb to 0df66c0 Compare July 16, 2025 12:08
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.24.3 chore(deps): update dependency wrangler to v4.24.4 Jul 16, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 0df66c0 to b9f2b78 Compare July 17, 2025 17:16
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.24.4 chore(deps): update dependency wrangler to v4.25.0 Jul 17, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from b9f2b78 to c8903e5 Compare July 22, 2025 17:06
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.25.0 chore(deps): update dependency wrangler to v4.25.1 Jul 22, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from c8903e5 to acd474a Compare July 24, 2025 14:48
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.25.1 chore(deps): update dependency wrangler to v4.26.0 Jul 24, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from acd474a to 7877ed7 Compare July 29, 2025 17:36
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.26.0 chore(deps): update dependency wrangler to v4.26.1 Jul 29, 2025
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v4.26.1 chore(deps): update dependency wrangler to v4.27.0 Jul 31, 2025
@renovate renovate bot force-pushed the renovate/wrangler-4.x-lockfile branch from 7877ed7 to 6c70ec7 Compare August 3, 2025 17:14
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