Skip to content

chore(deps): update dependency wrangler to v4.166.0 - #75

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/wrangler-4.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/wrangler-4.x

Conversation

@renovate

@renovate renovate Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 4.147.0 → 4.166.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.166.0

Compare Source

Minor Changes
  • #​16961 bf7568a Thanks @​dario-piotrowicz! - Show configured trigger targets during experimental wrangler triggers deploy --dry-run

    Dry runs now print a "Would deploy" summary of routes, custom domains, cron schedules, Queue producers and consumers, Workflows, event triggers, and Email Routing addresses instead of exiting without a summary. Explicitly empty cron schedules and Email Routing addresses are shown as removals. The preview makes no API requests or authentication checks; when workers.dev is enabled, it reports that setting without looking up the account's subdomain.

  • #​16679 be6aa81 Thanks @​mglewis! - Add images.url_transformations to the Wrangler configuration

    The images block now accepts a url_transformations object for controlling /cdn-cgi/image/ transformations on requests served by a Worker. enabled is required, and allowed_origins optionally lists the origins images may be fetched from (use ["*"] to allow any origin). binding is now optional, so url_transformations can be configured without an Images binding:

    {
      "images": {
        "url_transformations": {
          "enabled": true,
          "allowed_origins": ["images.example.com"]
        }
      }
    }

    Like the rest of the images block, url_transformations is not inherited by named environments, and must be specified in each environment that needs it.

    cloudflare.config.ts gains the equivalent setting as a top-level images field on the Worker, with the Images binding remaining in env:

    export default defineConfig({
      worker: {
        name: "my-worker",
        compatibilityDate: "2026-11-01",
        images: {
          urlTransformations: {
            enabled: true,
            allowedOrigins: ["images.example.com"],
          },
        },
      },
    });

    cf migrate carries images.url_transformations over to this field.

    This change adds configuration and validation only. url_transformations is not supported in previews.

  • #​14114 dce615c Thanks @​dario-piotrowicz! - Add --show-diff flag to wrangler triggers deploy

    When --show-diff is passed, the command fetches the currently deployed trigger configuration from the remote worker and displays a colored diff against the local configuration before deploying. This covers routes, custom domains, cron schedules, and the workers_dev/preview_urls subdomain settings. Route and custom-domain lists are fetched only when that category has local entries to deploy, avoiding unnecessary permission requirements. Queue consumers and event triggers are not compared.

    The flag also works with --dry-run to preview these changes without actually deploying. Displaying a diff requires authentication, including during a dry run.

Patch Changes
  • #​17031 95fd4c2 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-19

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​17031 95fd4c2 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261118.1 ^5.20261119.1
    workerd 1.20261118.1 1.20261119.1
  • #​16961 bf7568a Thanks @​dario-piotrowicz! - Validate external Workflow settings before updating Worker triggers

    Reject limits, concurrency, schedules, default_retention, and jurisdiction configured on external Workflows before making trigger API calls. This prevents failed deployments from partially updating workers.dev or routes; dry runs reject the same invalid configurations.

  • #​17044 56974d4 Thanks @​petebacondarwin! - Warn when invocation logs are enabled while logs are disabled

    Configuration validation now warns when observability.logs.invocation_logs is true and observability.logs.enabled is false. Invocation logging remains disabled until observability.logs.enabled is set to true.

  • #​17072 3c91a13 Thanks @​mykcs! - Recover when concurrent wrangler preview builds try to create the same Preview name.

    If another build creates a Preview after the initial lookup, Wrangler now reads the existing Preview and applies the requested Preview settings instead of failing with Cloudflare API error 100338. Other creation errors still fail, and existing Previews are never deleted.

  • #​17081 08eeaf4 Thanks @​Naapperas! - Wait for a just-uploaded Worker version to become readable during deploys

    For a few seconds after a version is uploaded, the Workers API can alternate between returning it and reporting it as not found. wrangler versions deploy failed on the first not-found read, and wrangler deploy for Durable Object-managed containers gave up after about 2 seconds and reported that the container settings were not fully applied.

    Both now keep retrying a not-found version for up to about 12 seconds and log a message while they wait. These reads also retry transient API failures, such as server errors, rate limiting, timeouts and network errors, which can wait longer when the API asks for it. Other errors still fail immediately.

  • #​17030 f3f7bbc Thanks @​cpojer! - Stop running Docker at the end of builds for projects with no Containers

    Builds that write the Build Output Specification ran docker image ls on every build to find image tags left by a previous build, even when the project configured no Containers. On a machine with Docker installed this added about a quarter of a second to each build, and the build waited on the Docker CLI for as long as it took to respond. The lookup is now skipped when the project has no Containers and the build output being replaced had none either. Projects that configure Containers, and the first build after the last Container is removed, still remove previous tags as before.

  • #​17043 4f5b118 Thanks @​petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixes

    This patch includes six upstream security fixes covering caching, redirects, and Subresource Integrity verification. Update the shared Undici dependency and matching types together so affected packages ship the patched version.

  • #​17035 1b563db Thanks @​petebacondarwin! - Fix remote bindings authentication with API tokens scoped to an individual Worker

    Remote bindings now create preview sessions through the Worker-scoped endpoint. When the response includes a usable exchange URL, its hostname is used without account-wide Workers subdomain access; otherwise, the existing account subdomain lookup or registration is used. This applies to getPlatformProxy and remote bindings in Wrangler, the Cloudflare Vite plugin, and the Vitest integration. Tokens still need permission to update the named Worker.

  • Updated dependencies [8712fc5, 95fd4c2, 95fd4c2, be6aa81, 8f45554, 56974d4, 08eeaf4, 629f135, 4f5b118, 629f135, 8f45554]:

v4.165.0

Compare Source

Minor Changes
  • #​10598 24bd3c3 Thanks @​Ehbraheem! - Add a new --force flag to d1 migrations apply which skips the interactive confirmation and applies any pending migrations non-interactively. This is useful for CI and automation.

    Usage example:

    wrangler d1 migrations apply <db> --remote --force
    

    Fixes #​5017

Patch Changes
  • #​16019 8f26e90 Thanks @​penalosa! - Correct the dry-run setup message to say "exiting now" instead of "existing now".

    The previous wording contained a typo and appeared in Wrangler setup output and other consumers of shared autoconfig.

  • #​17003 3595295 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-18

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​17003 3595295 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261117.1 ^5.20261118.1
    workerd 1.20261117.1 1.20261118.1
  • #​16719 f833c8a Thanks @​jaeminbird! - Report .dev.vars and .env files that are not UTF-8 instead of silently loading no variables

    Before Wrangler would incorrectly read non UTF-8 .dev.vars and .env files as UTF-8. A .dev.vars file that is not UTF-8 now stops wrangler dev with a message that says how to fix it, and a .env file that is not UTF-8 is skipped with a warning. UTF-8 files, with or without a BOM, load as before.

  • #​14334 67d7c0a Thanks @​Divkix! - Replace the unmaintained asset hashing dependency with hash-wasm

    Keep asset hashes unchanged for Workers and Pages deployments and local Pages development while using a maintained WebAssembly implementation.

  • #​16949 110c162 Thanks @​edmundhung! - Fail remote RPC binding requests on network errors instead of hanging

    Remote bindings that connect over RPC treated every network failure, such as being offline, a DNS or TLS error, as a preview reload. The request then waited silently for a reload that never came. These requests now fail with the error, while GET and HEAD requests interrupted by an actual reload are still retried.

  • #​14578 6750663 Thanks @​penalosa! - Fix TypeScript errors when importing Wrangler's APIs

    Projects that import Wrangler's APIs, such as getPlatformProxy or defineWranglerConfig, can now type-check with skipLibCheck: false. The published types no longer refer to missing internal packages, and their required type dependencies are installed automatically.

  • Updated dependencies [0a4315f, 3595295, 3595295, 6750663, 6750663, d04e667, 6750663, 5a6e450]:

v4.164.0

Compare Source

Minor Changes
  • #​16450 5f05841 Thanks @​xortive! - Add custom CA and client certificate references to Workers VPC service TLS settings

    Workers VPC (open beta) service create and update commands accept --certificate-authority and --client-certificate UUIDs. Use either flag alone or both together. Whenever you supply either reference, explicitly choose --cert-verification-mode:

    • verify_full: verify the origin certificate chain and hostname (the platform default).
    • verify_ca: verify the chain but skip hostname verification, weakening origin identity checks.
    • disabled: do not verify the origin certificate; this allows connections to impersonated origins and is unsafe for production.

    For HTTP services, these settings apply to HTTPS connections, not plaintext HTTP. TCP services can use them for upstream TLS, including PostgreSQL.

    TLS settings are per-service only: host and resolver networks have no TLS settings or inheritance. Omitting TLS settings uses platform defaults (certificate chain and hostname verification). Explicit mode-only configuration, including verify_full, is accepted. A custom CA cannot be combined with disabled; a client certificate without a custom CA can.

    Upload certificates using the existing commands, then use the returned IDs below. Replace <ca-uuid>, <client-uuid>, <tunnel-uuid>, and service IDs with your own values; certificate references must be valid UUIDs. Upload replacement certificates the same way before rotating their references.

    pnpm exec wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca
    pnpm exec wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client

    Create an HTTPS service with both a custom trust chain and an mTLS client certificate, or a PostgreSQL TCP service with only a custom CA:

    pnpm exec wrangler vpc service create private-web \
      --type http --https-port 443 --ipv4 10.0.0.10 --tunnel-id <tunnel-uuid> \
      --certificate-authority <ca-uuid> --client-certificate <client-uuid> \
      --cert-verification-mode verify_full
    
    pnpm exec wrangler vpc service create private-db \
      --type tcp --tcp-port 5432 --app-protocol postgresql \
      --hostname db.internal.example --resolver-ips 10.0.0.53 --tunnel-id <tunnel-uuid> \
      --certificate-authority <ca-uuid> --cert-verification-mode verify_full

    For client-certificate-only configuration, use --client-certificate <client-uuid> --cert-verification-mode verify_full instead of the certificate flags in either create command.

    Updates replace the complete service configuration, including TLS settings, in a single request, the same as cf workers-vpc services update. Pass every TLS option the service should keep: certificate references and the verification mode that you omit are cleared, and an update without TLS options returns the service to the platform defaults. Removing a reference releases its backend certificate binding but does not delete the uploaded account certificate. For example, rotate the web service's client certificate while keeping its CA:

    pnpm exec wrangler vpc service update <web-service-uuid> \
      --name private-web --type http --https-port 443 \
      --ipv4 10.0.0.10 --tunnel-id <tunnel-uuid> \
      --certificate-authority <ca-uuid> --client-certificate <replacement-client-uuid> \
      --cert-verification-mode verify_full

    To remove the CA while keeping the client certificate, repeat the update with only --client-certificate <client-uuid> and a verification mode.

    Inspect the service's verification mode and CA/client certificate UUIDs (or None), without exposing certificate or private-key contents:

    pnpm exec wrangler vpc service get <service-uuid>
Patch Changes

v4.163.0

Compare Source

Minor Changes
  • #​16917 d36b39d Thanks @​jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer

    vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.

  • #​16246 349fc4e Thanks @​leostera! - Start local Workflows from Artifacts events

    Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports.

    Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.

Patch Changes
  • #​16803 b219078 Thanks @​petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commands

    cf dev, cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internal cf-vite delegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare @cloudflare/vite-plugin in its own manifest, or add vite or vite-plus as a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via --config are evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detected nodeModulesPaths in order, adding .bin to each directory. Lookup stops at the validated workspace root; standalone applications use only their own node_modules/.bin.

    Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS .cjs and .cts Vite configs to ESM imports and exports in .mjs or .mts before adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.

  • #​16944 db3c071 Thanks @​danlapid! - Stop wrangler dev from missing config file changes made soon after a reload

    wrangler dev replaced its config file watcher on every reload without waiting for the new one to start, so a change saved in that gap was never applied. It now keeps one watcher while the set of watched files is unchanged, and reports a config as applied only once its files are being watched. A second change saved within 50 ms of the previous one is no longer dropped either.

  • #​16920 81e56dd Thanks @​benbuzbee! - Use the effective max_instances value when choosing the default container rollout steps

    When max_instances was omitted, Wrangler deployed 20 instances but chose rollout steps as if there were 0 instances, so the rollout used a single 100% step. Wrangler now uses [10, 100] for omitted max_instances, while still using a single 100% step when max_instances is 0 or 1.

  • #​16946 e97c9f8 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16946 e97c9f8 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261113.1 ^5.20261116.1
    workerd 1.20261113.1 1.20261116.1
  • #​16874 4335eac Thanks @​petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials

    Check access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.

  • #​16917 d36b39d Thanks @​jamesopstad! - Detect Cloudflare Build Output of any version before deploying

    wrangler deploy, wrangler versions upload and wrangler preview refuse to run in a project that has Cloudflare Build Output, because that output belongs to cf. Detection now looks for any .cloudflare/output/v<N>/ directory rather than only the root config of the current version, so output left by an older or newer cf is still caught.

  • Updated dependencies [e97c9f8, e97c9f8, 349fc4e, 0bf81ac]:

v4.162.0

Compare Source

Minor Changes
  • #​16735 f005593 Thanks @​leostera! - Use the local simulator for Artifacts bindings that omit remote

    Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos in wrangler dev or vite dev, set "remote": true on the binding (dev: { remote: true } in cloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.

    While remote is omitted, wrangler dev, getPlatformProxy() and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Set remote: true to use deployed repos, or remote: false to silence this warning." Workers Vitest and wrangler dev --local already used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.

  • #​16749 032f8c2 Thanks @​vaishnav-mk! - Reject settings on a workflows binding to a Workflow declared in exports

    A workflows binding can still bind a Workflow that the Worker declares in exports, but it can no longer set limits, concurrency, schedules, default_retention, or jurisdiction for it. Set them on the export instead. Previously the binding and the export could both set them as long as they agreed, so configurations that set them on the binding now stop with an error that says which setting to move.

  • #​16749 032f8c2 Thanks @​vaishnav-mk! - Upload Workflow export settings with the Worker

    wrangler deploy and wrangler versions upload now include the settings of each workflow export (limits, concurrency, schedules, default_retention, and jurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker with workflow exports also send a Cloudflare-Workers-Script-Api-Date header, which lets the Workers API provision Workflow exports from these settings as part of the upload. wrangler deploy and wrangler triggers deploy still create or update each Workflow through the Workflows API afterwards, as before.

    If provisioning a scheduled Workflow fails because the account is on the free plan, wrangler deploy now explains that scheduled Workflows require a paid Workers plan.

Patch Changes
  • #​16849 3cea40b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-12

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16886 63eb6da Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-13

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16849 3cea40b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261110.1 ^5.20261112.1
    workerd 1.20261110.1 1.20261112.1
  • #​16886 63eb6da Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261112.1 ^5.20261113.1
    workerd 1.20261112.1 1.20261113.1
  • #​16864 3b1b408 Thanks @​MattieTK! - Fix packages with nested package.json files missing from deploy metadata

    Packages such as hono, stripe and @modelcontextprotocol/sdk were silently omitted from the package dependency metadata reported during wrangler deploy and wrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.

  • #​16862 c889551 Thanks @​petebacondarwin! - Fix requests hanging when a local Worker reload finishes before an inflight request fails

    Wrangler now immediately processes retriable requests when the replacement Worker is already ready. Previously, these requests could remain queued until another request arrived, particularly on Windows where connection failures can take longer to report.

  • Updated dependencies [f005593, 61eacca, 856842e, 856842e, 3cea40b, 63eb6da, 3cea40b, 63eb6da]:

v4.161.0

Compare Source

Minor Changes
  • #​16840 8b2a363 Thanks @​jamesopstad! - Write source maps in Build Output with sources relative to each source map file

    This changes the experimental Build Output that wrangler build --experimental-cf-build-output and cf-wrangler build write. Their source maps were prepared as if for upload, with sources relative to the project root. For Workers that Wrangler does not bundle, leading ../ segments were also removed, which lost the location of some files. They now point from each source map's location in bundle/ to the original files, like the source maps the Vite plugin writes.

Patch Changes
  • #​16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and cloudflare.config.ts settings in remote bindings errors from cf-wrangler

    When cf runs development through the cf-wrangler delegate and remote bindings cannot be authenticated, the error now tells you to run cf auth whoami, cf auth logout and cf auth login instead of the Wrangler commands, and the Cloudflare Access hint names cf. The Flagship error for a binding whose app has not been created now names the binding's id setting instead of app_id, and suggests cf flagship apps create. wrangler dev still names Wrangler's commands and settings.

  • #​16527 dc47e6d Thanks @​petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assets

    Relative _redirects targets now use shared pathname normalization after placeholder replacement, keeping repeated separators within the site's path. Explicit external targets (including scheme-less URLs such as //example.com/path), query values and fragments retain their contents.

  • #​16559 575d136 Thanks @​edmundhung! - Update @netlify/build-info to 11.3.1

  • #​16838 3626ee8 Thanks @​jamesopstad! - Keep the remote bindings session when you remove the last remote binding

    When you removed the last remote binding while wrangler dev was running, Wrangler restarted the remote bindings session with credentials that ignored --profile and the account_id in your Wrangler config. So it could use a different account or ask you to choose one. Wrangler now keeps the existing session, and starts a new one with your current credentials when you add a remote binding again.

  • Updated dependencies [dc47e6d]:

v4.160.1

Compare Source

Patch Changes

v4.160.0

Compare Source

Minor Changes
  • #​16760 cb9534f Thanks @​petebacondarwin! - Support forwarded Wrangler development server options in the experimental cf-wrangler delegate

    cf dev can now forward options such as --inspector-port 9229, --ip, --var, and --persist-to to the Wrangler development runtime. The delegate reuses Wrangler's dev option definitions and validation while retaining project config discovery, --mode environment selection, local development, and its .cloudflare/state default. Invalid option combinations produce a single-line usage error and exit code 2 before starting the server.

    Place server options that overlap cf's global options after --, for example cf dev -- --local --persist-to "custom state". Config and script overrides, whole-worker remote development, and Wrangler's global options remain unsupported.

  • #​16739 6af492e Thanks @​GregBrimble! - Add custom Cloudflare API headers through CLOUDFLARE_API_HEADERS

    Set CLOUDFLARE_API_HEADERS to a JSON object such as {"X-Custom-Header":"value"} to add headers to Cloudflare API requests. Custom headers override existing unprotected request headers, body and transport headers are protected, and header values outside the diagnostic allowlist remain redacted regardless of log sanitization settings.

Patch Changes
  • #​16810 cdc970b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-10

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16810 cdc970b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261109.1 ^5.20261110.1
    workerd 1.20261109.1 1.20261110.1
  • [#​16709](https

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 label Oct 7, 2026
@renovate renovate Bot added the dependencies label Oct 7, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from a2a9ce3 to 303ead4 Compare October 8, 2026 20:06
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.148.0 chore(deps): update dependency wrangler to v4.149.0 Oct 8, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 303ead4 to d208cc6 Compare October 13, 2026 10:45
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.149.0 chore(deps): update dependency wrangler to v4.150.0 Oct 13, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from d208cc6 to 3e98b53 Compare October 14, 2026 06:04
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.150.0 chore(deps): update dependency wrangler to v4.151.0 Oct 14, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 3e98b53 to 0a7f9a4 Compare October 16, 2026 10:01
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.151.0 chore(deps): update dependency wrangler to v4.151.1 Oct 16, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 0a7f9a4 to 75346c6 Compare October 19, 2026 13:00
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.151.1 chore(deps): update dependency wrangler to v4.151.2 Oct 19, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 75346c6 to 5cb5e9b Compare October 20, 2026 16:00
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.151.2 chore(deps): update dependency wrangler to v4.151.3 Oct 20, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 5cb5e9b to 0e5f3e9 Compare October 22, 2026 19:57
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.151.3 chore(deps): update dependency wrangler to v4.152.0 Oct 22, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 0e5f3e9 to c75fd8a Compare October 30, 2026 20:16
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.152.0 chore(deps): update dependency wrangler to v4.156.0 Oct 30, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from c75fd8a to 33c2132 Compare November 2, 2026 02:13
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.156.0 chore(deps): update dependency wrangler to v4.156.1 Nov 2, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 33c2132 to 42f06f9 Compare November 2, 2026 19:42
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.156.1 chore(deps): update dependency wrangler to v4.156.2 Nov 2, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 42f06f9 to e3c4d48 Compare November 3, 2026 15:39
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.156.2 chore(deps): update dependency wrangler to v4.157.0 Nov 3, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from e3c4d48 to a5e54c4 Compare November 5, 2026 13:45
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.157.0 chore(deps): update dependency wrangler to v4.158.0 Nov 5, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from a5e54c4 to ca7e009 Compare November 9, 2026 22:02
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.158.0 chore(deps): update dependency wrangler to v4.159.0 Nov 9, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from ca7e009 to c5a5103 Compare November 10, 2026 14:57
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.159.0 chore(deps): update dependency wrangler to v4.160.0 Nov 10, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from c5a5103 to 6cddd1d Compare November 11, 2026 23:00
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.160.0 chore(deps): update dependency wrangler to v4.160.1 Nov 11, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 6cddd1d to 2ee791a Compare November 12, 2026 16:10
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.160.1 chore(deps): update dependency wrangler to v4.161.0 Nov 12, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 2ee791a to 532910f Compare November 13, 2026 20:30
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.161.0 chore(deps): update dependency wrangler to v4.162.0 Nov 13, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 532910f to 8701efb Compare November 16, 2026 13:04
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.162.0 chore(deps): update dependency wrangler to v4.163.0 Nov 16, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 8701efb to aa3013f Compare November 17, 2026 20:10
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.163.0 chore(deps): update dependency wrangler to v4.164.0 Nov 17, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from aa3013f to 830ccdc Compare November 19, 2026 07:11
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.164.0 chore(deps): update dependency wrangler to v4.165.0 Nov 19, 2026
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 830ccdc to 8555bc6 Compare November 21, 2026 02:22
@renovate renovate Bot changed the title chore(deps): update dependency wrangler to v4.165.0 chore(deps): update dependency wrangler to v4.166.0 Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant