Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 9, 2024

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 3.51.03.114.17 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v3.114.17

Compare Source

Patch Changes
  • #​11891 6d5557b Thanks @​emily-shen! - Use argument array when executing git commands with wrangler pages deploy

    Pass user provided values from --commit-hash safely to underlying git command.

v3.114.16

Compare Source

Patch Changes
  • #​11689 9bab0a0 Thanks @​ascorbic! - Display a warning when authentication errors occur and the account_id in your Wrangler configuration does not match any of your authenticated accounts. This helps identify configuration issues where you may have the wrong account ID set in your wrangler.toml or wrangler.jsonc file.

  • #​10737 c41a078 Thanks @​workers-devprod! - Allow WRANGLER_SEND_ERROR_REPORTS env var to override whether to report Wrangler crashes to Sentry

  • #​11134 bd39455 Thanks @​petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.

    Now the argument values that are captured come from an allow list,
    and can be marked as ALLOW (capture the real value) or REDACT (capture as "").

  • #​11020 9cb702e Thanks @​dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

  • #​11147 cf4993b Thanks @​FlorentCollin! - Improve the formatting of the D1 execute command to always show the duration in milliseconds with two decimal places.

  • #​11650 cc29ead Thanks @​ascorbic! - fix: respect TypeScript path aliases when resolving non-JS modules with module rules

    When importing non-JavaScript files (like .graphql, .txt, etc.) using TypeScript path aliases defined in tsconfig.json, Wrangler's module-collection plugin now correctly resolves these imports. Previously, path aliases were only respected for JavaScript/TypeScript files, causing imports like import schema from '~lib/schema.graphql' to fail when using module rules.

  • #​11179 7f779e9 Thanks @​ascorbic! - Log a more helpful error when attempting to "r2 object put" a non-existent file

  • #​11501 c78d942 Thanks @​edmundhung! - fix: prevent reporting SQLite error from wrangler d1 execute to Sentry

  • #​11262 b2683f7 Thanks @​workers-devprod! - Avoid using object lookup for OAuth Error classes

  • #​11107 d8037d3 Thanks @​workers-devprod! - Fixed conflict between --env and --expires flags in wrangler r2 object put.

    --e now aliases --env only, and NOT --expires.

  • #​10961 02d2ea9 Thanks @​devin-ai-integration! - Acquire Cloudflare Access tokens for additional requests made during a wrangler dev --remote session

  • #​11108 892ec4f Thanks @​emily-shen! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.

  • #​11138 3db872a Thanks @​devin-ai-integration! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.

  • #​10889 204616c Thanks @​workers-devprod! - Clarify that wrangler check startup generates a local CPU profile

  • #​11491 ed8aaef Thanks @​edmundhung! - Explicitly close FileHandle in wrangler d1 execute to support Node 25

  • #​10962 203e599 Thanks @​devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur

  • #​11601 62754f8 Thanks @​petebacondarwin! - Fix "TypeError: Body is unusable: Body has already been read" when failing to exchange oauth code because of double response.text().

  • #​11138 3db872a Thanks @​devin-ai-integration! - We're soon going to make backend changes that mean that wrangler dev --remote sessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a new wrangler tail-based logging strategy for wrangler dev --remote. For now, you can revert to the previous logging strategy with wrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.

    The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.

  • #​11194 71758e9 Thanks @​petebacondarwin! - add more logging around Wrangler authentication to help diagnose issues

  • Updated dependencies [d006fae, 4ae9ead]:

    • miniflare@​3.20250718.3

v3.114.15

Compare Source

Patch Changes

v3.114.14

Compare Source

Patch Changes
  • #​10330 dab7683 Thanks @​petebacondarwin! - Do not attempt to update queue producer settings when deploying a Worker with a queue binding

    Previously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set different producer settings on a shared queue.

  • #​10233 a00a124 Thanks @​veggiedefender! - Increase the maxBuffer size for capnp uploads

  • #​10228 77a4364 Thanks @​dario-piotrowicz! - fix NonRetryableError thrown with an empty error message not stopping workflow retries locally

  • Updated dependencies []:

    • miniflare@​3.20250718.1

v3.114.13

Compare Source

Patch Changes
  • #​10015 b5d9bb0 Thanks @​dario-piotrowicz! - fix wrangler dev logs being logged on the incorrect level in some cases

    currently the way wrangler dev prints logs is faulty, for example the following code

    console.error("this is an error");
    console.warn("this is a warning");
    console.debug("this is a debug");

    inside a worker would cause the following logs:

    ✘ [ERROR] this is an error
    
    ✘ [ERROR] this is a warning
    
    this is a debug
    

    (note that the warning is printed as an error and the debug log is printed even if by default it should not)

    the changes here make sure that the logs are instead logged to their correct level, so for the code about the following will be logged instead:

    ✘ [ERROR] this is an error
    
    ▲ [WARNING] this is a warning
    

    (running wrangler dev with the --log-level=debug flag will also cause the debug log to be included as well)

  • #​10187 f480ec7 Thanks @​workers-devprod! - Deleting when Pages project binds to worker requires confirmation

  • #​10182 1f686ef Thanks @​devin-ai-integration! - fix: report startup errors before workerd profiling

  • #​10226 989e17e Thanks @​petebacondarwin! - Enforce 64-character limit for Workflow binding names locally to match production validation

  • #​10216 76d3002 Thanks @​devin-ai-integration! - Add macOS version validation to prevent EPIPE errors on unsupported macOS versions (below 13.5). Miniflare and C3 fail hard while Wrangler shows warnings but continues execution.

  • #​10261 8c38b65 Thanks @​petebacondarwin! - fix: strip ANSI escape codes from log files to improve readability and parsing

  • #​10171 0d73563 Thanks @​devin-ai-integration! - Handle UTF BOM in config files - detect and remove UTF-8 BOMs, error on unsupported BOMs (UTF-16, UTF-32)

  • Updated dependencies [b5d9bb0, 76d3002]:

    • miniflare@​3.20250718.1

v3.114.12

Compare Source

Patch Changes

v3.114.11

Compare Source

Patch Changes
  • #​9685 cbea64b Thanks @​WillTaylorDev! - Select only successfully deployed deployments when tailing.

  • #​9776 6e09672 Thanks @​vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

  • #​9694 dacfc35 Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

    this change makes sure that that getPlatformProxy, when the input configuration
    file contains an assets field, correctly returns the appropriate asset binding proxy

    example:

    // wrangler.jsonc
    {
    	"name": "my-worker",
    	"assets": {
    		"directory": "./public/",
    		"binding": "ASSETS",
    	},
    }
    import { getPlatformProxy } from "wrangler";
    
    const { env, dispose } = await getPlatformProxy();
    
    const text = await (await env.ASSETS.fetch("http://0.0.0.0/file.txt")).text();
    console.log(text); // logs the content of file.txt
    
    await dispose();
  • #​9807 4dd026b Thanks @​penalosa! - Better messaging for account owned tokens in wrangler whoami

v3.114.10

Compare Source

Patch Changes

v3.114.9

Compare Source

Patch Changes

v3.114.8

Compare Source

Patch Changes
  • #​9086 a2a56c8 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.

  • #​9037 d0d0025 Thanks @​CarmenPopoviciu! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.

  • #​9093 2f2f7ba Thanks @​CarmenPopoviciu! - fix: Validate input file for Vectorize inserts

  • Updated dependencies [fc04292, a01adca]:

    • miniflare@​3.20250408.1

v3.114.7

Compare Source

Patch Changes
  • #​8955 b7eba92 Thanks @​workers-devprod! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

  • #​8928 8bcb257 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

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

Configuration

📅 Schedule: Branch creation - "before 6am,every weekend" in timezone Europe/Oslo, 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
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @cloudflare/[email protected]
npm ERR! node_modules/@cloudflare/workers-types
npm ERR!   dev @cloudflare/workers-types@"3.19.0" from the root project
npm ERR!   peer @cloudflare/workers-types@"^2.0.0 || ^3.0.0" from @remix-run/[email protected]
npm ERR!   node_modules/@remix-run/cloudflare
npm ERR!     @remix-run/cloudflare@"1.11.1" from the root project
npm ERR!     @remix-run/cloudflare@"1.11.1" from @remix-run/[email protected]
npm ERR!     node_modules/@remix-run/cloudflare-pages
npm ERR!       @remix-run/cloudflare-pages@"1.11.1" from the root project
npm ERR!   1 more (@remix-run/cloudflare-pages)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @cloudflare/workers-types@"^4.20250408.0" from [email protected]
npm ERR! node_modules/wrangler
npm ERR!   dev wrangler@"3.114.17" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @cloudflare/[email protected]
npm ERR! node_modules/@cloudflare/workers-types
npm ERR!   peerOptional @cloudflare/workers-types@"^4.20250408.0" from [email protected]
npm ERR!   node_modules/wrangler
npm ERR!     dev wrangler@"3.114.17" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-02T18_09_25_629Z-debug-0.log

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented May 9, 2024

Deploying capracon-2023 with  Cloudflare Pages  Cloudflare Pages

Latest commit: 92a71a4
Status:🚫  Build failed.

View logs

@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 2e8c049 to 6644e38 Compare May 12, 2024 20: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 12, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 6644e38 to 49cdcfe Compare May 17, 2024 23:29
@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 17, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 49cdcfe to fdff82f Compare May 20, 2024 07:12
@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 20, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from fdff82f to 5ba131f Compare May 24, 2024 16:13
@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 24, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 5ba131f to bd2eac5 Compare May 31, 2024 18:25
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.57.1 chore(deps): update dependency wrangler to v3.57.2 May 31, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from bd2eac5 to 646c536 Compare June 3, 2024 17:11
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.57.2 chore(deps): update dependency wrangler to v3.58.0 Jun 3, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 646c536 to ae2222b Compare June 7, 2024 18:55
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.58.0 chore(deps): update dependency wrangler to v3.59.0 Jun 7, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from ae2222b to 3729aee Compare June 10, 2024 13:28
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.59.0 chore(deps): update dependency wrangler to v3.60.0 Jun 10, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 3729aee to bcd0839 Compare June 10, 2024 22:30
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.60.0 chore(deps): update dependency wrangler to v3.59.0 Jun 10, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from bcd0839 to 5480a80 Compare June 13, 2024 22:11
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.59.0 chore(deps): update dependency wrangler to v3.60.1 Jun 13, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 5480a80 to e19ec8e Compare June 14, 2024 18:42
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.60.1 chore(deps): update dependency wrangler to v3.60.2 Jun 14, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from e19ec8e to 61d9a7c Compare June 17, 2024 12:28
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.60.2 chore(deps): update dependency wrangler to v3.60.3 Jun 17, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 61d9a7c to 71ba494 Compare June 21, 2024 17:27
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.60.3 chore(deps): update dependency wrangler to v3.61.0 Jun 21, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 71ba494 to 3b42f54 Compare June 28, 2024 15:18
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.61.0 chore(deps): update dependency wrangler to v3.62.0 Jun 28, 2024
@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 29, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 4ac1f30 to d44f12b Compare April 6, 2025 13:56
@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 6, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from d44f12b to 3a4234b Compare April 12, 2025 15:10
@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 12, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 3a4234b to 8323e8c Compare April 17, 2025 12:25
@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 17, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 8323e8c to 7a7cdf7 Compare April 25, 2025 20:24
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.6 chore(deps): update dependency wrangler to v3.114.7 Apr 25, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 7a7cdf7 to 73e0dd0 Compare May 4, 2025 22:32
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.7 chore(deps): update dependency wrangler to v3.114.8 May 4, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 73e0dd0 to 402e796 Compare May 25, 2025 10:35
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.8 chore(deps): update dependency wrangler to v3.114.9 May 25, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 402e796 to 0c5d6fb Compare June 28, 2025 09:59
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.9 chore(deps): update dependency wrangler to v3.114.10 Jun 28, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 0c5d6fb to 6a094d1 Compare July 12, 2025 17:49
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.10 chore(deps): update dependency wrangler to v3.114.11 Jul 12, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 6a094d1 to e9361d6 Compare July 31, 2025 17:48
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.11 chore(deps): update dependency wrangler to v3.114.12 Jul 31, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from e9361d6 to fac620f Compare August 10, 2025 20:57
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.12 chore(deps): update dependency wrangler to v3.114.13 Aug 10, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from fac620f to 2afa064 Compare August 23, 2025 12:34
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.13 chore(deps): update dependency wrangler to v3.114.14 Aug 23, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 2afa064 to f4b3dce Compare October 9, 2025 19:08
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.14 chore(deps): update dependency wrangler to v3.114.15 Oct 9, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from f4b3dce to 61b9a58 Compare December 22, 2025 18:36
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.15 chore(deps): update dependency wrangler to v3.114.16 Dec 22, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 61b9a58 to 92a71a4 Compare January 16, 2026 18:51
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.16 chore(deps): update dependency wrangler to v3.114.17 Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants