Skip to content
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

chore(deps): update dependency wrangler to v3.57.1 #92

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

chore(deps): update dependency wrangler to v3.57.1 #92

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 24, 2024 •
edited

Mend Renovate

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v3.57.1

Compare Source

Patch Changes

  • #​5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

  • #​5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

    If a Pages project fails to deploy, wrangler pages deploy will log
    an error message, but exit successfully. It should instead throw a
    FatalError.

  • #​5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

    Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

  • #​5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

v3.57.0

Compare Source

Minor Changes

  • #​5696 7e97ba8 Thanks @​geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

  • #​5819 63f7acb Thanks @​CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure

    Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:

    ✨ Deployment complete!

    This commit ensures that we provide users with:

    • the correct feedback with respect to their Pages deployment
    • the appropriate messaging depending on the status of their project's deployment status
    • the appropriate logs in case of a deployment failure

  • #​5814 2869e03 Thanks @​CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help

    Running wrangler pages --help will list, amongst others, the following global flags:

    -j, --experimental-json-config
-c, --config
-e, --env
-h, --help
-v, --version

    This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.

    This commit ensures we display the correct global flags that apply to Pages.

  • #​5818 df2daf2 Thanks @​WalshyDev! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.

    If you're currently using the old binding, please move over to the new version_metadata binding by adding:

    [version_metadata]
binding = "CF_VERSION_METADATA"

    and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

Patch Changes

  • #​5838 609debd Thanks @​petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

  • #​5832 86a6e09 Thanks @​petebacondarwin! - fix: do not allow non-string values in bulk secret uploads

    Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a
    JSON file that contained non-string secrets, since these are not supported
    by the Cloudflare backend.

    This change reintroduces that check to give the user a helpful error message
    rather than a cryptic workers.api.error.invalid_script_config error code.

v3.56.0

Compare Source

Minor Changes
  • #​5712 151bc3d Thanks @​penalosa! - feat: Support mtls_certificates and browser bindings when using wrangler.toml with a Pages project
Patch Changes

  • #​5813 9627cef Thanks @​GregBrimble! - fix: Upload Pages project assets with more grace

    • Reduces the maximum bucket size from 50 MiB to 40 MiB.
    • Reduces the maximum asset count from 5000 to 2000.
    • Allows for more retries (with increased sleep between attempts) when encountering an API gateway failure.

  • Updated dependencies [0725f6f, 89b6d7f]:

    • miniflare@3.20240512.0

v3.55.0

Compare Source

Minor Changes

  • #​5570 66bdad0 Thanks @​sesteves! - feature: support delayed delivery in the miniflare's queue simulator.

    This change updates the miniflare's queue broker to support delayed delivery of messages, both when sending the message from a producer and when retrying the message from a consumer.

Patch Changes

  • #​5740 97741db Thanks @​WalshyDev! - chore: log "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback to support migration from the deprecated "Deployment ID". Users should update any parsing to use "Version ID" before "Deployment ID" is removed.

  • #​5754 f673c66 Thanks @​RamIdeas! - fix: when using custom builds, the wrangler dev proxy server was sometimes left in a paused state

    This could be observed as the browser loading indefinitely, after saving a source file (unchanged) when using custom builds. This is now fixed by ensuring the proxy server is unpaused after a short timeout period.

  • Updated dependencies [66bdad0, 9b4af8a]:

    • miniflare@3.20240419.1

v3.53.1

Compare Source

Patch Changes

  • #​5091 6365c90 Thanks @​Cherry! - fix: better handle dashes and other invalid JS identifier characters in wrangler types generation for vars, bindings, etc.

    Previously, with the following in your wrangler.toml, an invalid types file would be generated:

    [vars]
some-var = "foobar"

    Now, the generated types file will be valid:

    interface Env {
	"some-var": "foobar";
}

  • #​5748 27966a4 Thanks @​penalosa! - fix: Load sourcemaps relative to the entry directory, not cwd.

  • #​5746 1dd9f7e Thanks @​petebacondarwin! - fix: suggest trying to update Wrangler if there is a newer one available after an unexpected error

  • #​5226 f63e7a5 Thanks @​DaniFoldi! - fix: remove second Wrangler banner from wrangler dispatch-namespace rename

v3.53.0

Compare Source

Minor Changes

  • #​5604 327a456 Thanks @​dario-piotrowicz! - feat: add support for environments in getPlatformProxy

    allow getPlatformProxy to target environments by allowing users to specify an environment option

    Example usage:

    const { env } = await getPlatformProxy({
	environment: "production",
});
Patch Changes

v3.52.0

Compare Source

Minor Changes

  • #​5666 81d9615 Thanks @​CarmenPopoviciu! - fix: Fix Pages config validation around Durable Objects

    Today Pages cannot deploy Durable Objects itself. For this reason it is mandatory that when declaring Durable Objects bindings in the config file, the script_name is specified. We are currently not failing validation if
    script_name is not specified but we should. These changes fix that.

Patch Changes

v3.51.2

Compare Source

Patch Changes

v3.51.0

Compare Source

Minor Changes

  • #​5477 9a46e03 Thanks @​pmiguel! - feature: Changed Queues client to use the new QueueId and ConsumerId-based endpoints.

  • #​5172 fbe1c9c Thanks @​GregBrimble! - feat: Allow marking external modules (with --external) to avoid bundling them when building Pages Functions

    It's useful for Pages Plugins which want to declare a peer dependency.

Patch Changes

v3.50.0

Compare Source

Minor Changes

  • #​5587 d95450f Thanks @​CarmenPopoviciu! - fix: pages functions build-env should throw error if invalid Pages config file is found

  • #​5572 65aa21c Thanks @​CarmenPopoviciu! - fix: fix pages function build-env to exit with code rather than throw fatal error

    Currently pages functions build-env throws a fatal error if a config file does not exit, or if it is invalid. This causes issues for the CI system. We should instead exit with a specific code, if any of those situations arises.

  • #​5291 ce00a44 Thanks @​pmiguel! - feature: Added bespoke OAuth scope for Queues management.

Patch Changes
  • Updated dependencies [08b4908]:
    • miniflare@3.20240405.1

v3.49.0

Compare Source

Minor Changes
Patch Changes

  • #​5374 7999dd2 Thanks @​maxwellpeterson! - fix: Improvements to --init-from-dash

    Adds user-specified CPU limit to wrangler.toml if one exists. Excludes usage_model from wrangler.toml in all cases, since this field is deprecated and no longer used.

  • #​5553 dcd65dd Thanks @​rozenmd! - fix: refactor d1's time-travel compatibility check

  • #​5380 57d5658 Thanks @​GregBrimble! - fix: Respect --no-bundle when deploying a _worker.js/ directory in Pages projects

  • #​5536 a7aa28a Thanks @​Cherry! - fix: resolve a regression where wrangler pages dev would bind to port 8787 by default instead of 8788 since wrangler@3.38.0

  • Updated dependencies [9575a51]:

    • miniflare@3.20240405.0

v3.48.0

Compare Source

Minor Changes

  • #​5429 c5561b7 Thanks @​ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it is
    enabled on your account.

    Wrangler supports an -s flag that allows the user to specify a storage class when creating a bucket,
    changing the default storage class of a bucket, and uploading an object.

    wrangler r2 bucket create ia-bucket -s InfrequentAccess
wrangler r2 bucket update storage-class my-bucket -s InfrequentAccess
wrangler r2 object put bucket/ia-object -s InfrequentAccess --file foo
Patch Changes

v3.47.1

Compare Source

Patch Changes
  • Updated dependencies [9f15ce1]:
    • miniflare@3.20240404.0

v3.47.0

Compare Source

Minor Changes
  • #​5506 7734f80 Thanks @​penalosa! - feat: Add interactive prompt to wrangler pages download config if an existing wrangler.toml file exists

v3.46.0

Compare Source

Minor Changes

  • #​5282 b7ddde1 Thanks @​maxwellpeterson! - feature: Add source map support for Workers

    Adds the source_maps boolean config option. When enabled, source maps included in the build output are uploaded alongside the built code modules. Uploaded source maps can then be used to remap stack traces emitted by the Workers runtime.

  • #​5215 cd03d1d Thanks @​GregBrimble! - feature: support named entrypoints in service bindings

    This change allows service bindings to bind to a named export of another Worker. As an example, consider the following Worker named bound:

    import { WorkerEntrypoint } from "cloudflare:workers";

export class EntrypointA extends WorkerEntrypoint {
	fetch(request) {
		return new Response("Hello from entrypoint A!");
	}
}

export const entrypointB: ExportedHandler = {
	fetch(request, env, ctx) {
		return new Response("Hello from entrypoint B!");
	}
};

export default <ExportedHandler>{
	fetch(request, env, ctx) {
		return new Response("Hello from the default entrypoint!");
	}
};

    Up until now, you could only bind to the default entrypoint. With this change, you can bind to EntrypointA or entrypointB too using the new entrypoint option:

    [[services]]
binding = "SERVICE"
service = "bound"
entrypoint = "EntrypointA"

    To bind to named entrypoints with wrangler pages dev, use the # character:

    $ wrangler pages dev --service=SERVICE=bound#EntrypointA
Patch Changes

  • #​5215 cd03d1d Thanks @​GregBrimble! - fix: ensure request url and cf properties preserved across service bindings

    Previously, Wrangler could rewrite url and cf properties when sending requests via service bindings or Durable Object stubs. To match production behaviour, this change ensures these properties are preserved.

  • Updated dependencies [cd03d1d, 6c3be5b, cd03d1d, cd03d1d]:

    • miniflare@3.20240403.0

v3.45.0

Compare Source

Minor Changes

  • #​5377 5d68744 Thanks @​CarmenPopoviciu! - feat: Add wrangler.toml support in wrangler pages deploy

    As we are adding wrangler.toml support for Pages, we want to ensure that wrangler pages deploy works with a configuration file.

  • #​5471 489b9c5 Thanks @​zebp! - feature: Add version-id filter for Worker tailing to filter logs by scriptVersion in a gradual deployment

    This allows users to only get logs in a gradual deployment if you are troubleshooting issues
    specific to one deployment. Example:
    npx wrangler tail --version-id 72d3f357-4e52-47c5-8805-90be978c403f

Patch Changes

v3.44.0

Compare Source

Minor Changes

  • #​5461 f69e562 Thanks @​mattdeboard! - feature: Add command for fetching R2 Event Notification configurations for a given bucket

    This allows users to see the entire event notification configuration -- i.e. every rule for every configured queue -- for a single bucket with a single request.

    This change also improves messaging of console output when creating a new bucket notification.

Patch Changes

v3.43.0

Compare Source

Minor Changes
Patch Changes

v3.42.0

Compare Source

Minor Changes

  • #​5371 77152f3 Thanks @​G4brym! - feature: remove requirement for @cloudflare/ai package to use Workers AI

    Previously, to get the correct Workers AI API, you needed to wrap your env.AI binding with new Ai() from @cloudflare/ai. This change moves the contents of @cloudflare/ai into the Workers runtime itself, meaning env.AI is now an instance of Ai, without the need for wrapping.

Patch Changes
  • Updated dependencies [d994066]:
    • miniflare@3.20240329.0

v3.41.0

Compare Source

Minor Changes

v3.40.0

Compare Source

Minor Changes

  • #​5426 9343714 Thanks @​RamIdeas! - feature: added a new wrangler triggers deploy command

    This command currently requires the --experimental-versions flag.

    This command extracts the trigger deployment logic from wrangler deploy and allows users to update their currently deployed Worker's triggers without doing another deployment. This is primarily useful for users of wrangler versions upload and wrangler versions deploy who can then run wrangler triggers deploy to apply trigger changes to their currently deployed Worker Versions.

    The command can also be used even if not using the wrangler versions ... commands. And, in fact, users are already using it implicitly when running wrangler deploy.

  • #​4932 dc0c1dc Thanks @​xortive! - feature: Add support for private networking in Hyperdrive configs

  • #​5369 7115568 Thanks @​mattdeboard! - fix: Use queue name, not ID, for r2 bucket event-notification subcommands

    Since the original command was not yet operational, this update does not constitute a breaking change.

    Instead of providing the queue ID as the parameter to --queue, users must provide the queue name. Under the hood, we will query the Queues API for the queue ID given the queue name.

  • #​5413 976adec Thanks @​pmiguel! - feature: Added Queue delivery controls support in wrangler.toml

  • #​5412 3e5a932 Thanks @​RamIdeas! - feature: adds the --json option to wrangler deployments list --experimental-versions, wrangler deployments status --experimental-versions, wrangler versions list --experimental-versions and wrangler versions view --experimental-versions which will format the output as clean JSON. The --experimental-versions flag is still required for these commands.

  • #​5258 fbdca7d Thanks @​OilyLime! - feature: URL decode components of the Hyperdrive config connection string

  • #​5416 47b325a Thanks @​mattdeboard! - fix: minor improvements to R2 notification subcommand

    1. r2 bucket event-notification <subcommand> becomes r2 bucket notification <subcommand>
    2. Parameters to --event-type use - instead of _ (e.g. object_create -> object-create)

    Since the original command was not yet operational, this update does not constitute a breaking change.

Patch Changes

  • #​5419 daac6a2 Thanks @​RamIdeas! - chore: add helpful logging to --experimental-versions commands

  • #​5400 c90dd6b Thanks @​RamIdeas! - chore: log of impending change of "Deployment ID" to "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback. This is a warning of a future change for anyone depending on the output text format, for example by grepping the output in automated flows.

  • #​5422 b341614 Thanks @​geelen! - fix: remove d1BetaWarning and all usages

    This PR removes the warning that D1 is in beta for all D1 commands.

  • Updated dependencies [fbdca7d]:

    • miniflare@3.20240320.1

v3.39.0

Compare Source

Minor Changes

  • #​5373 5bd8db8 Thanks @​RamIdeas! - feature: Implement versioned rollbacks via wrangler rollback [version-id] --experimental-versions.

    Please note, the experimental-versions flag is required to use the new behaviour. The original wrangler rollback command is unchanged if run without this flag.

Patch Changes

  • #​5366 e11e169 Thanks @​RamIdeas! - fix: save non-versioned script-settings (logpush, tail_consumers) on wrangler versions deploy. This command still requires --experimental-versions.

  • #​5405 7c701bf Thanks @​RamIdeas! - chore: add wrangler deployments view [deployment-id] --experimental-versions command

    This command will display an error message which points the user to run either wrangler deployments status --experimental-versions or wrangler versions view <version-id> --experimental-versions instead.

v3.38.0

Compare Source

Minor Changes

  • #​5310 528c011 Thanks @​penalosa! - feat: Watch the entire module root for changes in --no-bundle mode, rather than just the entrypoint file.

  • #​5327 7d160c7 Thanks @​penalosa! - feat: Add wrangler pages download config

  • #​5284 f5e2367 Thanks @​CarmenPopoviciu! - feat: Add wrangler.toml support in wrangler pages dev

    As we are adding wrangler.toml support for Pages, we want to ensure that wrangler pages dev works with a configuration file.

  • #​5353 3be826f Thanks @​penalosa! - feat: Updates wrangler pages functions build to support using configuration from wrangler.toml in the generated output.

  • #​5102 ba52208 Thanks @​pmiguel! - feature: add support for queue delivery controls on wrangler queues create

Patch Changes

v3.37.0

Compare Source

Minor Changes

  • #​5294 bdc121d Thanks @​mattdeboard! - feature: Add event-notification commands in support of event notifications for Cloudflare R2.

    Included are commands for creating and deleting event notification configurations for individual buckets.

  • #​5231 e88ad44 Thanks @​w-kuhn! - feature: Add support for configuring HTTP Pull consumers for Queues

    HTTP Pull consumers can be used to pull messages from queues via https request.

Patch Changes

  • #​5317 9fd7eba Thanks @​GregBrimble! - chore: Deprecate -- <command>, --proxy and --script-path options from wrangler pages dev.

    Build your application to a directory and run the wrangler pages dev <directory> instead. This results in a more faithful emulation of production behavior.

  • Updated dependencies [248a318]:

    • miniflare@3.20240320.0

v3.36.0

Compare Source

Minor Changes

  • #​5234 e739b7f Thanks @​CarmenPopoviciu! - feat: Implement environment inheritance for Pages configuration

    For Pages, Wrangler will not require both of the supported named environments ("preview" | "production") to be explicitly defined in the config file. If either [env.production] or [env.preview] is left unspecified, Wrangler will use the top-level environment when targeting that named Pages environment.

Patch Changes

  • #​5306 c60fed0 Thanks @​taylorlee! - fix: Remove triggered_by annotation from experimental versions deploy command which is now set by the API and cannot be set by the client.

  • #​5321 ac93411 Thanks @​RamIdeas! - fix: rename --experimental-gradual-rollouts to --experimental-versions flag

    The --experimental-gradual-rollouts flag has been made an alias and will still work.

    And additional shorthand alias --x-versions has also been added and will work too.

  • #​5324 bfc4282 Thanks @​penalosa! - fix: Ignore OPTIONS requests in Wrangler's oauth server

  • #​5099 93150aa Thanks @​KaiSpencer! - feat: expose --show-interactive-dev-session flag

    This flag controls the interactive mode of the dev session, a feature that already exists internally but was not exposed to the user.
    This is useful for CI/CD environments where the interactive mode is not desired, or running in tools like turbo and nx.

v3.35.0

Compare Source

Minor Changes

  • #​5166 133a190 Thanks @​CarmenPopoviciu! - feat: Implement config file validation for Pages projects

    Wrangler proper has a mechanism in place through which it validates a wrangler.toml file for Workers projects. As part of adding wrangler toml support for Pages, we need to put a similar mechanism in place, to validate a configuration file against Pages specific requirements.

  • #​5279 0a86050 Thanks @​penalosa! - feat: Support the hidden command wrangler pages functions build-env

  • #​5093 a676f55 Thanks @​benycodes! - feature: add --dispatch-namespace to wrangler deploy to support uploading Workers directly to a Workers for Platforms dispatch namespace.

Patch Changes

  • #​5275 e1f2576 Thanks @​petebacondarwin! - fix: ensure tail exits when the WebSocket disconnects

    Previously when the tail WebSocket disconnected, e.g. because of an Internet failure,
    the wrangler tail command would just hang and neither exit nor any longer receive tail messages.

    Now the process exits with an exit code of 1, and outputs an error message.

    The error message is formatted appropriately, if the tail format is set to json.

    Fixes #​3927

  • #​5069 8f79981 Thanks @​RamIdeas! - chore: deprecate wrangler version command

    wrangler version is an undocumented alias for wrangler --version. It is being deprecated in favour of the more conventional flag syntax to avoid confusion with a new (upcoming) wrangler versions command.

  • Updated dependencies [1720f0a]:

    • miniflare@3.20240314.0

v3.34.2

Compare Source

Patch Changes
  • #​5238 a0768bc Thanks @​RamIdeas! - fix: versions upload annotations (--message and/or --tag) are now applied correctly to the uploaded Worker Version

v3.34.1

Compare Source

Patch Changes
  • Updated dependencies [2e50d51]:
    • miniflare@3.20240304.2

v3.34.0

Compare Source

Minor Changes

  • #​5224 03484c2 Thanks @​RamIdeas! - feature: Implement wrangler deployments list and wrangler deployments status behind --experimental-gradual-rollouts flag.

  • #​5115 29e8151 Thanks @​RamIdeas! - feature: Implement wrangler versions deploy command.

    For now, invocations should use the --experimental-gradual-rollouts flag.

    Without args, a user will be guided through prompts. If args are specified, they are used as the default values for the prompts. If the --yes flag is specified, the defaults are automatically accepted for a non-interactive flow.

  • #​5208 4730b6c Thanks @​RamIdeas! - feature: Implement wrangler versions list and wrangler versions view commands behind the --experimental-gradual-rollouts flag.

  • #​5064 bd935cf Thanks @​OilyLime! - feature: Improve create and update logic for hyperdrive to include caching settings

v3.33.0

Compare Source

Minor Changes

  • #​4930 2680462 Thanks @​rozenmd! - refactor: default wrangler d1 execute and wrangler d1 migrations commands to local mode first, to match wrangler dev

    This PR defaults wrangler d1 execute and wrangler d1 migrations commands to use the local development environment provided by wrangler to match the default behaviour in wrangler dev.

    BREAKING CHANGE (for a beta feature): wrangler d1 execute and wrangler d1 migrations commands now default --local to true. When running wrangler d1 execute against a remote D1 database, you will need to provide the --remote flag.

Patch Changes

  • #​5184 046930e Thanks @​nora-soderlund! - fix: change d1 migrations create to use the highest migration number rather than the first non-existing migration number to allow for gaps in the migration files.

  • Updated dependencies [1235d48, 27fb22b]:

    • miniflare@3.20240304.1

v3.32.0

Compare Source

Minor Changes
Patch Changes

  • #​5089 5b85dc9 Thanks @​DaniFoldi! - fix: include all currently existing bindings in wrangler types

    Add support for Email Send, Vectorize, Hyperdrive, mTLS, Browser Rendering and Workers AI bindings in wrangler types

    For example, from the following wrangler.toml setup:

    [browser]
binding = "BROWSER"

[ai]
binding = "AI"

[[send_email]]
name = "SEND_EMAIL"

[[vectorize]]
binding = "VECTORIZE"
index_name = "VECTORIZE_NAME"

[[hyperdrive]]
binding = "HYPERDRIVE"
id = "HYPERDRIVE_ID"

[[mtls_certificates]]
binding = "MTLS"
certificate_id = "MTLS_CERTIFICATE_ID"

    Previously, nothing would have been included in the generated Environment.
    Now, the followin

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.52.0 chore(deps): update dependency wrangler to v3.53.0 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from f6adca8 to a886c5b Compare May 2, 2024 22:41
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.53.0 chore(deps): update dependency wrangler to v3.53.1 May 2, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from a886c5b to 953081e Compare May 9, 2024 17:06
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.53.1 chore(deps): update dependency wrangler to v3.55.0 May 9, 2024
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.55.0 chore(deps): update dependency wrangler to v3.56.0 May 14, 2024
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.56.0 chore(deps): update dependency wrangler to v3.57.0 May 17, 2024
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.57.0 chore(deps): update dependency wrangler to v3.57.1 May 21, 2024
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.

None yet
0 participants