Skip to content

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

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

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

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

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
wrangler (source) ^3.81.0 -> ^4.14.4 age adoption passing confidence

Release Notes

cloudflare/workers-sdk (wrangler)

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

  • #​8435 8e3688f Thanks @​emily-shen! - fix: include assets binding when printing summary of bindings

  • #​8675 f043b74 Thanks @​vicb! - Bump @cloudflare/unenv-preset to 2.3.1

    Use the workerd native implementation of createSecureContext and checkServerIdentity from node:tls. The functions have been implemented in cloudflare/workerd#3754.

v4.4.1

Compare Source

Patch Changes

v4.4.0

Compare Source

Minor Changes
Patch Changes

v4.3.0

Compare Source

Minor Changes
Patch Changes

v4.2.0

Compare Source

Minor Changes
Patch Changes

v4.1.0

Compare Source

Minor Changes

  • #​8337 1b2aa91 Thanks @​Ltadrian! - Add mTLS configuration fields to Hyperdrive command

    hyperdrive create test123 ... --ca-certificate-uuid=CA_CERT_UUID --mtls-certificate-uuid=MTLS_CERT_UUID

Patch Changes

v4.0.0

Compare Source

Major Changes

  • #​7334 869ec7b Thanks @​penalosa! - Use --local by default for wrangler kv key and wrangler r2 object commands

  • #​7334 869ec7b Thanks @​dario-piotrowicz! - chore: remove deprecated getBindingsProxy

    remove the deprecated getBindingsProxy utility which has been replaced with getPlatformProxy

  • #​7334 869ec7b Thanks @​penalosa! - Remove the deprecated --format argument on wrangler deploy and wrangler dev.

    Remove deprecated config fields:

    • type
    • webpack_config
    • miniflare
    • build.upload
    • zone_id
    • usage_model
    • experimental_services
    • kv-namespaces

  • #​7334 869ec7b Thanks @​rozenmd! - Remove wrangler d1 backups

    This change removes wrangler d1 backups, a set of alpha-only commands that would allow folks to interact with backups of their D1 alpha DBs.

    For production D1 DBs, you can restore previous versions of your database with wrangler d1 time-travel and export it at any time with wrangler d1 export.

    Closes #​7470

  • #​7334 869ec7b Thanks @​rozenmd! - Remove --batch-size as an option for wrangler d1 execute and wrangler d1 migrations apply

    This change removes the deprecated --batch-size flag, as it is no longer necessary to decrease the number of queries wrangler sends to D1.

    Closes #​7470

  • #​7334 869ec7b Thanks @​rozenmd! - Remove alpha support from wrangler d1 migrations apply

    This change removes code that would take a backup of D1 alpha databases before proceeding with applying a migration.

    We can remove this code as alpha DBs have not accepted queries in months.

    Closes #​7470

  • #​7334 869ec7b Thanks @​penalosa! - Remove the deprecated wrangler generate command. Instead, use the C3 CLI to create new projects: https://developers.cloudflare.com/pages/get-started/c3/

  • #​7334 869ec7b Thanks @​penalosa! - Remove the deprecated wrangler init --no-delegate-c3 command. wrangler init is still available, but will always delegate to C3.

  • #​7334 869ec7b Thanks @​penalosa! - Remove support for legacy assets.

    This removes support for legacy assets using the --legacy-assets flag or legacy_assets config field. Instead, you should use Workers Assets

  • #​7334 869ec7b Thanks @​penalosa! - Remove the deprecated wrangler publish command. Instead, use wrangler deploy, which takes exactly the same arguments.

    Additionally, remove the following deprecated commands, which are no longer supported.

    • wrangler config
    • wrangler preview
    • wrangler route
    • wrangler subdomain

    Remove the following deprecated command aliases:

    • wrangler secret:*, replaced by wrangler secret *
    • wrangler kv:*, replaced by wrangler kv *

  • #​7334 869ec7b Thanks @​penalosa! - Remove the deprecated wrangler version command. Instead, use wrangler --version to check the current version of Wrangler.

  • #​7334 869ec7b Thanks @​penalosa! - The --node-compat flag and node_compat config properties are no longer supported as of Wrangler v4. Instead, use the nodejs_compat compatibility flag. This includes the functionality from legacy node_compat polyfills and natively implemented Node.js APIs. See https://developers.cloudflare.com/workers/runtime-apis/nodejs for more information.

    If you need to replicate the behaviour of the legacy node_compat feature, refer to https://developers.cloudflare.com/workers/wrangler/migration/update-v3-to-v4/ for a detailed guide.

  • #​7334 869ec7b Thanks @​threepointone! - chore: update esbuild

    This patch updates esbuild from 0.17.19 to 0.24.2. That's a big bump! Lots has gone into esbuild since May '23. All the details are available at https://github.com/evanw/esbuild/blob/main/CHANGELOG.md / https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md.

    • We now support all modern JavasScript/TypeScript features suported by esbuild (as of December 2024). New additions include standard decorators, auto-accessors, and the using syntax.

    • 0.18 introduced wider support for configuration specified via tsconfig.json https://github.com/evanw/esbuild/issues/3019. After observing the (lack of) any actual broken code over the last year for this release, we feel comfortable releasing this without considering it a breaking change.

    • 0.19.3 introduced support for import attributes

      import stuff from './stuff.json' with { type: 'json' }

      While we don't currently expose the esbuild configuration for developers to add their own plugins to customise how modules with import attributes are bundled, we may introduce new "types" ourselves in the future.

    • 0.19.0 introduced support for wildcard imports. Specifics here (https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md#0190). tl;dr -

      • These 2 patterns will bundle all files that match the glob pattern into a single file.

        const json1 = await import("./data/" + kind + ".json");
        const json2 = await import(`./data/${kind}.json`);

      • This pattern will NOT bundle any matching patterns:

        const path = "./data/" + kind + ".js";
const json2 = await import(path);

        You can use find_additional_modules to bundle any additional modules that are not referenced in the code but are required by the project.

      Now, this MAY be a breaking change for some. Specifically, if you were previously using the pattern (that will now include all files matching the glob pattern in the bundle), BUT find_additional_modules was NOT configured to include some files, those files would now be included in the bundle. For example, consider this code:

      // src/index.js
export default {
	async fetch() {
		const url = new URL(request.url);
		const name = url.pathname;
		const value = (await import("." + name)).default;
		return new Response(value);
	},
};

      Imagine if in that folder, you had these 3 files:

      // src/one.js
export default "one";
      // src/two.js
export default "two";
      // src/hidden/secret.js
export default "do not share this secret";

      And your wrangler.toml was:

      name = "my-worker"
main = "src/index.js

      Before this update:

      1. A request to anything but http://localhost:8787/ would error. For example, a request to http://localhost:8787/one.js would error with No such module "one.js".
      2. Let's configure wrangler.toml to include all .js files in the src folder:
      name = "my-worker"
main = "src/index.js

find_additional_modules = true
rules = [
  { type = "ESM

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@vercel Vercel
Copy link

vercel bot commented Mar 17, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
jiosaavn-api-ts ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 8, 2025 9:45am
jiosaavn-private ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 8, 2025 9:45am

@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from bbb6023 to 3653976 Compare March 18, 2025 01:01
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 3653976 to 2f8498a Compare March 19, 2025 13:35
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 2f8498a to e5fa12d Compare March 21, 2025 00:58
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from e5fa12d to 0dddd27 Compare March 22, 2025 16:26
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 0dddd27 to 32bae51 Compare March 26, 2025 09:27
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 32bae51 to 87f6360 Compare March 26, 2025 18:00
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 87f6360 to fcc13b3 Compare March 27, 2025 20:36
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from fcc13b3 to bb20a1c Compare March 28, 2025 16:45
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from bb20a1c to 89f6751 Compare April 2, 2025 20:53
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from f0b2e7b to ec4424f Compare April 24, 2025 18:45
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from ec4424f to a1e05f3 Compare April 25, 2025 16:36
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from a1e05f3 to 4da1ad5 Compare April 29, 2025 18:32
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 4da1ad5 to 92e195a Compare April 30, 2025 18:53
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 92e195a to 9b6d156 Compare May 1, 2025 20:45
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 9b6d156 to 5bc3448 Compare May 6, 2025 14:41
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 5bc3448 to 2565d21 Compare May 6, 2025 18:51
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 2565d21 to 89e5296 Compare May 7, 2025 15:48
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 89e5296 to dd6e1bf Compare May 8, 2025 09:44
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