Skip to content

chore(deps): update dependency wrangler to v3.114.6 #1760

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 v3.114.6 #1760

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 23, 2024 •
edited
Loading

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v3.114.6

Compare Source

Patch Changes

  • #​8783 7bcf352 Thanks @​petebacondarwin! - 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.

  • #​8866 db673d6 Thanks @​edmundhung! - 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

  • #​8600 91cf028 Thanks @​workers-devprod! - 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

v3.114.5

Compare Source

Patch Changes

v3.114.4

Compare Source

Patch Changes

v3.114.3

Compare Source

Patch Changes

v3.114.2

Compare Source

Patch Changes

v3.114.1

Compare Source

Patch Changes

  • #​8383 8d6d722 Thanks @​matthewdavidrodgers! - Make kv bulk put --local respect base64:true

    The bulk put api has an optional "base64" boolean property for each key.
    Before storing the key, the value should be decoded from base64.

    For real (remote) kv, this is handled by the rest api. For local kv, it
    seems the base64 field was ignored, meaning encoded base64 content was
    stored locally rather than the raw values.

    To fix, we need to decode each value before putting to the local
    miniflare namespace when base64 is true.

  • #​8273 e3efd68 Thanks @​penalosa! - Support AI, Vectorize, and Images bindings when using @cloudflare/vite-plugin

  • #​8427 a352798 Thanks @​vicb! - update unenv-preset dependency to fix bug with Performance global

    Fixes #​8407
    Fixes #​8409
    Fixes #​8411

  • #​8390 53e6323 Thanks @​GregBrimble! - Parse and apply metafiles (_headers and _redirects) in wrangler dev for Workers Assets

  • #​8392 4d9d9e6 Thanks @​jahands! - fix: retry zone and route lookup API calls

    In rare cases, looking up Zone or Route API calls may fail due to transient errors. This change improves the reliability of wrangler deploy when these errors occur.

    Also fixes a rare issue where concurrent API requests may fail without correctly throwing an error which may cause a deployment to incorrectly appear successful.

  • Updated dependencies [8242e07, 53e6323]:

    • miniflare@3.20250310.0

v3.114.0

Compare Source

Minor Changes
  • #​8367 7b6b0c2 Thanks @​jonesphillip! - Deprecated --id parameter in favor of --name for both the wrangler r2 bucket lifecycle and wrangler r2 bucket lock commands

v3.113.0

Compare Source

Minor Changes
Patch Changes

  • #​8338 2d40989 Thanks @​GregBrimble! - feat: Upload _headers and _redirects if present with Workers Assets as part of wrangler deploy and wrangler versions upload.

  • #​8288 cf14e17 Thanks @​CarmenPopoviciu! - feat: Add assets Proxy Worker skeleton in miniflare

    This commit implements a very basic Proxy Worker skeleton, and wires it in the "pipeline" miniflare creates for assets. This Worker will be incrementally worked on, but for now, the current implementation will forward all incoming requests to the Router Worker, thus leaving the current assets behaviour in local dev, the same.

    This is an experimental feature available under the --x-assets-rpc flag: wrangler dev --x-assets-rpc.

  • #​8216 af9a57a Thanks @​ns476! - Support Images binding in wrangler types

  • #​8304 fbba583 Thanks @​jahands! - chore: add concurrency and caching for Zone IDs and Workers routes lookups

    Workers with many routes can result in duplicate Zone lookups during deployments, making deployments unnecessarily slow. This compounded by the lack of concurrency when making these API requests.

    This change deduplicates these requests and adds concurrency to help speed up deployments.

  • Updated dependencies [2d40989, da568e5, cf14e17, 79c7810]:

    • miniflare@3.20250224.0

v3.112.0

Compare Source

Minor Changes

  • #​8256 f59d95b Thanks @​jbwcloudflare! - Add two new Queues commands: pause-delivery and resume-delivery

    These new commands allow users to pause and resume the delivery of messages to Queue Consumers

Patch Changes

v3.111.0

Compare Source

Minor Changes
Patch Changes

v3.110.0

Compare Source

Minor Changes
  • #​8253 6dd1e23 Thanks @​CarmenPopoviciu! - Add --cwd global argument to the wrangler CLI to allow changing the current working directory before running any command.
Patch Changes

v3.109.3

Compare Source

Patch Changes

v3.109.2

Compare Source

Patch Changes

v3.109.1

Compare Source

Patch Changes

v3.109.0

Compare Source

Minor Changes

  • #​8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

  • #​8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

  • #​8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

    This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

  • #​8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

    This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

    Advanced usage:

    • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
    • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/
Patch Changes

  • #​8112 fff677e Thanks @​penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

  • #​8120 3fb801f Thanks @​sdnts! - Check bounds when overriding delivery delay when creating Queues

  • #​7950 4db1fb5 Thanks @​cmackenzie1! - Add local binding support for Worker Pipelines

  • #​8119 1bc60d7 Thanks @​penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

  • #​8130 1aa2a91 Thanks @​emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

    User provided strings are still left redacted as always.

  • #​8061 35710e5 Thanks @​emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

    Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

  • Updated dependencies [4db1fb5]:

    • miniflare@3.20250204.1

v3.108.1

Compare Source

Patch Changes

  • #​8103 a025ad2 Thanks @​emily-shen! - fix: fix bug where wrangler secret list --format=json was printing the wrangler banner.

  • Updated dependencies []:

    • miniflare@3.20250204.0

v3.108.0

Compare Source

Minor Changes

  • #​7990 b1966df Thanks @​cmsparks! - Add WRANGLER_CI_OVERRIDE_NAME for Workers CI

  • #​8028 b2dca9a Thanks @​emily-shen! - feat: Also log when no bindings are found.

    We currently print a worker's bindings during dev, versions upload and deploy. This just also prints something when there's no bindings found, in case you were expecting bindings.

  • #​8037 71fd250 Thanks @​WillTaylorDev! - Provides unsafe.metadata configurations when using wrangler versions secret put.

Patch Changes

  • #​8058 1f80d69 Thanks @​WillTaylorDev! - Bugfix: Modified versions secret put to inherit all known bindings, which circumvents a limitation in the API which does not return all fields for all bindings.

  • #​7986 88514c8 Thanks @​andyjessop! - docs: clarifies that local resources are "simulated locally" or "connected to remote resource", and adds console messages to help explain local dev

  • #​8008 9d08af8 Thanks @​ns476! - Add support for Images bindings (in private beta for now), with optional local support for platforms where Sharp is available.

  • #​7769 6abe69c Thanks @​cmackenzie1! - Adds the following new option for wrangler pipelines create and wrangler pipelines update commands:

    --cors-origins           CORS origin allowlist for HTTP endpoint (use * for any origin)  [array]

  • #​7290 0c0374c Thanks @​emily-shen! - fix: add support for workers with assets when running multiple workers in one wrangler dev instance

    https://github.com/cloudflare/workers-sdk/pull/7251 added support for running multiple Workers in one wrangler dev/miniflare session. e.g. wrangler dev -c wrangler.toml -c ../worker2/wrangler.toml, which among other things, allowed cross-service RPC to Durable Objects.

    However this did not work in the same way as production when there was a Worker with assets - this PR should fix that.

  • #​7769 6abe69c Thanks @​cmackenzie1! - Rename wrangler pipelines <create|update> flags

    The following parameters have been renamed:

    Previous Name New Name
    access-key-id r2-access-key-id
    secret-access-key r2-secret-access-key
    transform transform-worker
    r2 r2-bucket
    prefix r2-prefix
    binding enable-worker-binding
    http enable-http
    authentication require-http-auth
    filename file-template
    filepath partition-template

  • #​8012 c412a31 Thanks @​mtlemilio! - Use fetchPagedListResult when listing Hyperdrive configs from the API

    This fixes an issue where only 20 configs were being listed.

  • #​8077 60310cd Thanks @​emily-shen! - feat: add telemetry to experimental auto-provisioning

  • Updated dependencies [c80dbd8, 0c0374c]:

    • miniflare@3.20250204.0

v3.107.3

Compare Source

Patch Changes

  • #​7378 59c7c8e Thanks @​IRCody! - Add build and push helper sub-commands under the cloudchamber command.

  • Updated dependencies []:

    • miniflare@3.20250129.0

v3.107.2

Compare Source

Patch Changes

v3.107.1

Compare Source

Patch Changes

  • #​7981 e2b3306 Thanks @​WalshyDev! - Fixes a regression introduced in Wrangler 3.107.0 in which [assets] was not being inherited from the top-level environment.

  • Updated dependencies [ab49886]:

    • miniflare@3.20250129.0

v3.107.0

Compare Source

Minor Changes
Patch Changes

  • #​7945 d758215 Thanks @​ns476! - Add Images binding (in private beta for the time being)

  • #​7947 f57bc4e Thanks @​dario-piotrowicz! - fix: avoid getPlatformProxy logging twice that it is using vars defined in .dev.vars files

    when getPlatformProxy is called and it retrieves values from .dev.vars files, it logs twice
    a message like: Using vars defined in .dev.vars, the changes here make sure that in such cases
    this log only appears once

  • #​7889 38db4ed Thanks @​emily-shen! - feat: add experimental resource auto-provisioning to versions upload

  • #​7864 de6fa18 Thanks @​dario-piotrowicz! - Update the unstable_getMiniflareWorkerOptions types to always include an env parameter.

    The unstable_getMiniflareWorkerOptions types, when accepting a config object as the first argument,
    didn't accept a second env argument. The changes here make sure they do, since the env is still
    relevant for picking up variables from .dev.vars files.

  • #​7964 bc4d6c8 Thanks @​LuisDuarte1! - Fix scripts binding to a workflow in a different script overriding workflow config

  • Updated dependencies [cf4f47a]:

    • miniflare@3.20250124.1

v3.106.0

Compare Source

Minor Changes

  • #​7856 2b6f149 Thanks @​emily-shen! - feat: add sanitised error messages to Wrangler telemetry

    Error messages that have been audited for potential inclusion of personal information, and explicitly opted-in, are now included in Wrangler's telemetry collection. Collected error messages will not include any filepaths, user input or any other potentially private content.

  • #​7900 bd9228e Thanks @​vicb! - chore(wrangler): update unenv dependency version

    unenv@2.0.0-rc.1 allows using the workerd implementation for
    the Node modules net, timers, and timers/promises.
    See unjs/unenv#396.

Patch Changes

  • #​7904 50b13f6 Thanks @​WalshyDev! - fix: validation for R2 bucket names, the regex was wrongly rejecting buckets starting with a number and the message wasn't as clear as it could be on what was going wrong.

  • #​7895 134d61d Thanks @​jahands! - Fix regression in retryOnAPIFailure preventing any requests from being retried

    Also fixes a regression in pipelines that prevented 401 errors from being retried when waiting for an API token to become active.

  • #​7879 5c02e46 Thanks @​andyjessop! - Fix to not require local connection string when using Hyperdrive and wrangler dev --remote

  • #​7860 13ab591 Thanks @​vicb! - refactor(wrangler): make JSON parsing independent of Node

    Switch jsonc-parser to parse json:

    • JSON.parse() exception messages are not stable across Node versions
    • While jsonc-parser is used, JSONC specific syntax is disabled

  • Updated dependencies []:

    • miniflare@3.20250124.0

v3.105.1

Compare Source

Patch Changes

v3.105.0

Compare Source

Minor Changes

  • #​7466 e5ebdb1 Thanks @​Ltadrian! - feat: implement the wrangler cert upload command

    This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

    For uploading mTLS certificate, run:

    • wrangler cert upload mtls-certificate --cert cert.pem --key key.pem --name MY_CERT

    For uploading CA certificate chain, run:

    • wrangler cert upload certificate-authority --ca-cert server-ca.pem --name SERVER_CA
Patch Changes

v3.104.0

Compare Source

Minor Changes

  • #​7715 26fa9e8 Thanks @​penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

  • #​7816 f6cc029 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.json
{
	"name": "my-worker",
	"assets": {
		"directory": "./public/",
		"binding": "ASSETS"
	},
	"vars": {
		"MY_VAR": "my-var"
	}
}
    import { getPlatformProxy } from "wrangler";

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

if (env.ASSETS) {
	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

  • #​7785 cccfe51 Thanks @​joshthoward! - Fix Durable Objects transfer migration validation

  • #​7821 fcaa02c Thanks @​vicb! - fix(wrangler): fix wrangler config schema defaults

  • #​7832 97d2a1b Thanks @​petebacondarwin! - Relax the messaging when Wrangler uses redirected configuration

    Previously the messaging was rendered as a warning, which implied that the user
    had done something wrong. Now it is just a regular info message.

  • #​7806 d7adb50 Thanks @​vicb! - chore: update unenv to 2.0.0-rc.0

    Pull a couple changes in node:timers

    The unenv update also includes #unjs/unenv/381 which implements
    stdout, stderr and stdin of node:process with node:tty

  • #​7828 9077a67 Thanks @​edmundhung! - improve multi account error message in non-interactive mode

  • Updated dependencies []:

    • miniflare@3.20241230.2

v3.103.2

Compare Source

Patch Changes

v3.103.1

Compare Source

Patch Changes

v3.103.0

Compare Source

Minor Changes

  • #​5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

    add a new --strict-vars option to wrangler types that developers can (by setting the
    flag to false) use to disable the default strict/literal types generation for their variables

    opting out of strict variables can be useful when developers change often their vars values,
    even more so when multiple environments are involved

v3.102.0

Compare Source

Minor Changes
Patch Changes

  • #​7750 df0e5be Thanks @​andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output of wrangler dev, and adds-in the same tag for Durable Objects (which are emulated locally in wrangler dev).

  • #​7732 d102b60 Thanks @​Ankcorn! - fix pages secret bulk copy

  • #​7706 c63f1b0 Thanks @​penalosa! - Remove the server-based dev registry in favour of the more stable file-based dev registry. There should be no user-facing impact.

  • Updated dependencies [8e9aa40]:

    • miniflare@3.20241230.2

v3.101.0

Compare Source

Minor Changes

  • #​7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

  • #​7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

    Run wrangler secret bulk .dev.vars to add the env file

    //.dev.vars
KEY=VALUE
KEY_2=VALUE

    This will upload the secrets KEY and KEY_2 to your worker

  • #​7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

    This new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
    which Wrangler can use instead of user configuration when running deploy-related commands.
    It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:

  • wrangler deploy
  • wrangler dev
  • wrangler versions upload
  • wrangler versions deploy
  • wrangler pages deploy
  • wrangler pages build
  • wrangler pages build-env
Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

{ "configPath": "../../path/to/wrangler.json" }

When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.

  • The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.

    name = "my-worker"
main = "src/index.ts"
[[kv_namespaces]]
binding = "<BINDING_NAME1>"
id = "<NAMESPACE_ID1>"

    Note that this configuration points main at user code entry-point.

  • The user runs a custom build, which might read the wrangler.toml to find the entry-point:

    > my-tool build

  • This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:

    - dist
  - index.js
	- wrangler.json
- .wrangler
  - deploy
	  - config.json

    The dist/wrangler.json will contain:

    {
	"name": "my-worker",
	"main": "./index.js",
	"kv_namespaces": [
		{ "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
	]
}

    And the .wrangler/deploy/config.json will contain:

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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Sep 23, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 23, 2024 •
edited
Loading

💻 Website Preview

The latest changes are available as preview in: https://pr-1760.guild-dev-website.pages.dev

@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 48a40ba to 3d5b7fb Compare September 25, 2024 09:54
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.78.8 chore(deps): update dependency wrangler to v3.78.9 Sep 25, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 3d5b7fb to 44ad324 Compare September 25, 2024 23:19
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.78.9 chore(deps): update dependency wrangler to v3.78.10 Sep 25, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 44ad324 to 5b04251 Compare September 27, 2024 12:32
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.78.10 chore(deps): update dependency wrangler to v3.78.11 Sep 27, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 5b04251 to 60b60d5 Compare September 27, 2024 19:06
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.78.11 chore(deps): update dependency wrangler to v3.78.12 Sep 27, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 60b60d5 to 100a08d Compare October 1, 2024 16:02
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.78.12 chore(deps): update dependency wrangler to v3.79.0 Oct 1, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 100a08d to 2d0d6d8 Compare October 4, 2024 12:54
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.79.0 chore(deps): update dependency wrangler to v3.80.0 Oct 4, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 2d0d6d8 to ab94e32 Compare October 7, 2024 19:58
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.80.0 chore(deps): update dependency wrangler to v3.80.1 Oct 7, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from ab94e32 to d7ad259 Compare October 8, 2024 22:31
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.80.1 chore(deps): update dependency wrangler to v3.80.2 Oct 8, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from d7ad259 to c45f92b Compare October 10, 2024 21:02
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.80.2 chore(deps): update dependency wrangler to v3.80.3 Oct 10, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from c45f92b to 07ac460 Compare October 11, 2024 19:44
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.80.3 chore(deps): update dependency wrangler to v3.80.4 Oct 11, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 07ac460 to 3ef4c55 Compare October 16, 2024 15:11
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.80.4 chore(deps): update dependency wrangler to v3.80.5 Oct 16, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 3ef4c55 to c26add3 Compare October 17, 2024 17:42
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.80.5 chore(deps): update dependency wrangler to v3.81.0 Oct 17, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from c26add3 to fe8af93 Compare October 22, 2024 21:48
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.81.0 chore(deps): update dependency wrangler to v3.82.0 Oct 22, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from fe8af93 to ad0097b Compare October 24, 2024 11:26
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.82.0 chore(deps): update dependency wrangler to v3.83.0 Oct 24, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 1c79be8 to 424eda7 Compare March 4, 2025 12:13
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.111.0 chore(deps): update dependency wrangler to v3.112.0 Mar 4, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 424eda7 to e2aab74 Compare March 6, 2025 02:33
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.112.0 chore(deps): update dependency wrangler to v3.113.0 Mar 6, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from e2aab74 to 40ea6a1 Compare March 6, 2025 19:12
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.113.0 chore(deps): update dependency wrangler to v3.114.0 Mar 6, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 40ea6a1 to 3f979e2 Compare March 10, 2025 10:57
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.0 chore(deps): update dependency wrangler to v3.112.0 Mar 10, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 3f979e2 to c88182c Compare March 11, 2025 19:51
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.112.0 chore(deps): update dependency wrangler to v3.114.1 Mar 11, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from c88182c to 9136997 Compare March 17, 2025 22:58
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.1 chore(deps): update dependency wrangler to v3.114.2 Mar 17, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 9136997 to 32d233e Compare March 18, 2025 14:09
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from 2b0a8b2 to 8741602 Compare March 23, 2025 06:57
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 8741602 to 2fcc914 Compare March 26, 2025 23:03
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.2 chore(deps): update dependency wrangler to v3.114.3 Mar 26, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 2fcc914 to 835b04a Compare April 3, 2025 16:01
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.3 chore(deps): update dependency wrangler to v3.114.4 Apr 3, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 835b04a to 340fea4 Compare April 9, 2025 19:50
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.4 chore(deps): update dependency wrangler to v3.114.5 Apr 9, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 340fea4 to ce557f5 Compare April 14, 2025 17:07
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.5 chore(deps): update dependency wrangler to v3.114.6 Apr 14, 2025
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
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants