Skip to content
This repository has been archived by the owner on Apr 6, 2024. It is now read-only.

chore(deps): update dependency wrangler to v3 #8

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

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

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

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

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

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

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

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

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

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 following will be generated:

    interface Env {
    	SEND_EMAIL: SendEmail;
    	VECTORIZE: VectorizeIndex;
    	HYPERDRIVE: Hyperdrive;
    	MTLS: Fetcher;
    	BROWSER: Fetcher;
    	AI: Fetcher;
    }
  • Updated dependencies [11951f3, 11951f3]:

v3.31.0

Compare Source

Minor Changes
Patch Changes
  • #​5132 82a3f94 Thanks @​mrbbot! - fix: switch default logging level of unstable_dev() to warn

    When running unstable_dev() in its default "test mode", the logging level was set to none. This meant any Worker startup errors or helpful warnings wouldn't be shown. This change switches the default to warn. To restore the previous behaviour, include logLevel: "none" in your options object:

    const worker = await unstable_dev("path/to/script.js", {
    	logLevel: "none",
    });
  • #​5128 d27e2a7 Thanks @​taylorlee! - fix: Add legacy_env support to experimental versions upload command.

  • #​5087 a5231de Thanks @​dario-piotrowicz! - fix: make wrangler types always generate a d.ts file for module workers

    Currently if a config file doesn't define any binding nor module, running
    wrangler types against such file would not produce a d.ts file.

    Producing a d.ts file can however still be beneficial as it would define a correct
    env interface (even if empty) that can be expanded/referenced by user code (this can
    be particularly convenient for scaffolding tools that may want to always generate an
    env interface).

    Example:
    Before wrangler types --env-interface MyEnv run with an empty wrangler.toml file
    would not generate any file, after these change it would instead generate a file with
    the following content:

    interface MyEnv {
    }
    
  • #​5138 3dd9089 Thanks @​G4brym! - fix: ensure Workers-AI local mode fetcher returns headers to client worker

  • Updated dependencies [42bcc72, 42bcc72]:

v3.30.1

Compare Source

Patch Changes
  • #​5106 2ed7f32 Thanks @​RamIdeas! - fix: automatically drain incoming request bodies

    Previously, requests sent to wrangler dev with unconsumed bodies could result in Network connection lost errors. This change attempts to work around the issue by ensuring incoming request bodies are drained if they're not used. This is a temporary fix whilst we try to address the underlying issue. Whilst we don't think this change will introduce any other issues, it can be disabled by setting the WRANGLER_DISABLE_REQUEST_BODY_DRAINING=true environment variable. Note this fix is only applied if you've enabled Wrangler's bundling—--no-bundle mode continues to have the previous behaviour.

  • #​5107 65d0399 Thanks @​penalosa! - fix: Ensures that switching to remote mode during a dev session (from local mode) will correctly use the right zone. Previously, zone detection happened before the dev session was mounted, and so dev sessions started with local mode would have no zone inferred, and would have failed to start, with an ugly error.

  • #​5107 65d0399 Thanks @​penalosa! - fix: Ensure that preview sessions created without a zone don't switch the host on which to start the preview from the one returned by the API.

  • #​4833 54f6bfc Thanks @​admah! - fix: remove extra arguments from wrangler init deprecation message and update recommended c3 version

    c3 can now infer the pre-existing type from the presence of the --existing-script flag so we can remove the extra type argument. C3 2.5.0 introduces an auto-update feature that will make sure users get the latest minor version of c3 and prevent problems where older 2.x.x versions get cached by previous runs of wrangler init.

v3.30.0

Compare Source

Minor Changes
  • #​4742 c2f3f1e Thanks @​benycodes! - feat: allow preserving file names when defining rules for non-js modules

    The developer is now able to specify the `preserve_file_names property in wrangler.toml
    which specifies whether Wrangler will preserve the file names additional modules that are
    added to the deployment bundle of a Worker.

    If not set to true, files will be named using the pattern ${fileHash}-${basename}.
    For example, 34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico.

    Resolves #​4741

Patch Changes

v3.29.0

Compare Source

Minor Changes
  • #​5042 5693d076 Thanks @​dario-piotrowicz! - feat: add new --env-interface to wrangler types

    Allow users to specify the name of the interface that they want wrangler types to generate for the env parameter, via the new CLI flag --env-interface

    Example:

    wrangler types --env-interface CloudflareEnv

    generates

    interface CloudflareEnv {}

    instead of

    interface Env {}
  • #​5042 5693d076 Thanks @​dario-piotrowicz! - feat: add new path positional argument to wrangler types

    Allow users to specify the path to the typings (.d.ts) file they want
    wrangler types to generate

    Example:

    wrangler types ./my-env.d.ts

    generates a my-env.d.ts file in the current directory
    instead of creating a worker-configuration.d.ts file

Patch Changes
  • #​5042 5693d076 Thanks @​dario-piotrowicz! - feat: include command run in the wrangler types comment

    In the comment added to the .d.ts file generated by wrangler types
    include the command run to generated the file

  • #​5042 5693d076 Thanks @​dario-piotrowicz! - fix: make wrangler types honor top level config argument

    The wrangler types command currently ignores the -c|--config argument
    (although it is still getting shown in the command's help message). Make
    sure that the command honors the flag.
    Also, if no config file is detected
    present a warning to the user

  • #​5042 5693d076 Thanks @​dario-piotrowicz! - fix: make the wrangler types command pick up local secret keys from .dev.vars

    Make sure that the wrangler types command correctly picks up
    secret keys defined in .dev.vars and includes them in the generated
    file (marking them as generic string types of course)

  • Updated dependencies [b03db864]:

v3.28.4

Compare Source

Patch Changes
  • #​5050 88be4b84 Thanks @​nora-soderlund! - fix: allow kv:namespace create to accept a namespace name that contains characters not allowed in a binding name

    This command tries to use the namespace name as the binding. Previously, we would unnecessarily error if this namespace name did not fit the binding name constraints. Now we accept such names and then remove invalid characters when generating the binding name.

v3.28.3

Compare Source

Patch Changes
  • #​5026 04584722 Thanks @​dario-piotrowicz! - fix: make sure getPlatformProxy produces a production-like caches object

    make sure that the caches object returned to getPlatformProxy behaves
    in the same manner as the one present in production (where calling unsupported
    methods throws a helpful error message)

    note: make sure that the unsupported methods are however not included in the
    CacheStorage type definition

  • #​5030 55ea0721 Thanks @​mrbbot! - fix: don't suggest reporting user errors to GitHub

    Wrangler has two different types of errors: internal errors caused by something going wrong, and user errors caused by an invalid configuration. Previously, we would encourage users to submit bug reports for user errors, even though there's nothing we can do to fix them. This change ensures we only suggest this for internal errors.

  • #​4900 3389f2e9 Thanks @​OilyLime! - feature: allow hyperdrive users to set local connection string as environment variable

    Wrangler dev now supports the HYPERDRIVE_LOCAL_CONNECTION_STRING environmental variable for connecting to a local database instance when testing Hyperdrive in local development. This environmental variable takes precedence over the localConnectionString set in wrangler.toml.

  • #​5033 b1ace91b Thanks @​mrbbot! - fix: wait for actual port before opening browser with --port=0

    Previously, running wrangler dev --remote --port=0 and then immediately pressing b would open localhost:0 in your default browser. This change queues up opening the browser until Wrangler knows the port the dev server was started on.

v3.28.2

Compare Source

Patch Changes
  • #​4950 05360e43 Thanks @​petebacondarwin! - fix: ensure we do not rewrite external Origin headers in wrangler dev

    In https://github.com/cloudflare/workers-sdk/pull/4812 we tried to fix the Origin headers to match the Host header but were overzealous and rewrote Origin headers for external origins (outside of the proxy server's origin).

    This is now fixed, and moreover we rewrite any headers that refer to the proxy server on the request with the configured host and vice versa on the response.

    This should ensure that CORS is not broken in browsers when a different host is being simulated based on routes in the Wrangler configuration.

  • #​5002 315a651b Thanks @​dario-piotrowicz! - chore: rename getBindingsProxy to getPlatformProxy

    initially getBindingsProxy was supposed to only provide proxies for bindings,
    the utility has however grown, including now cf, ctx and caches, to
    clarify the increased scope the utility is getting renamed to getPlatformProxy
    and its bindings field is getting renamed env

    note: getBindingProxy with its signature is still kept available, making this
    a non breaking change

  • Updated dependencies [05360e43]:

v3.28.1

Compare Source

Patch Changes
  • #​4962 d6585178 Thanks @​mrbbot! - fix: ensure wrangler dev can reload without crashing when importing node:* modules

    The previous Wrangler release introduced a regression that caused reloads to fail when importing node:* modules. This change fixes that, and ensures these modules can always be resolved.

v3.28.0

Compare Source

Minor Changes
  • #​4499 cf9c029b Thanks @​penalosa! - feat: Support runtime-agnostic polyfills

    Previously, Wrangler treated any imports of node:* modules as build-time errors (unless one of the two Node.js compatibility modes was enabled). This is sometimes overly aggressive, since those imports are often not hit at runtime (for instance, it was impossible to write a library that worked across Node.JS and Workers, using Node packages only when running in Node). Here's an example of a function that would cause Wrangler to fail to build:

    export function randomBytes(length: nu

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 added the renovate label May 28, 2023
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from cb65443 to 28047ec Compare July 11, 2023 22:45
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3 chore(deps): update dependency wrangler to v3 - autoclosed Aug 28, 2023
@renovate renovate bot closed this Aug 28, 2023
@renovate renovate bot deleted the renovate/wrangler-3.x branch August 28, 2023 17:37
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3 - autoclosed chore(deps): update dependency wrangler to v3 Aug 28, 2023
@renovate renovate bot reopened this Aug 28, 2023
@renovate renovate bot restored the renovate/wrangler-3.x branch August 28, 2023 21:34
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from b443dbc to c83ef42 Compare September 20, 2023 16:42
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 8d3849d to 71dfdc0 Compare September 28, 2023 20:00
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 68107ec to fec467a Compare October 12, 2023 18:37
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 481179b to c808de9 Compare October 17, 2023 22:31
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 97c0a7d to 52bf9bf Compare February 6, 2024 21:57
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 22287e7 to 5955710 Compare February 13, 2024 19:13
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from 28ad275 to 91a6d84 Compare February 22, 2024 23:04
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 3 times, most recently from fa423d3 to 723cdd8 Compare March 5, 2024 19:10
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 5 times, most recently from 9431cc0 to 15836c6 Compare March 14, 2024 17:14
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 4 times, most recently from a9c0280 to f0507a6 Compare March 26, 2024 19:21
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 6 times, most recently from 325ee14 to 5adb78b Compare April 2, 2024 22:59
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 7fff770 to a4c42ac Compare April 5, 2024 02:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants