Skip to content

chore(deps): update dependency wrangler to v4.164.0 - #492

Merged
kruton merged 1 commit into
developfrom
renovate/wrangler-4.x
Nov 20, 2026
Merged

kruton merged 1 commit into
developfrom
renovate/wrangler-4.x

Conversation

@renovate

@renovate renovate Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 4.162.0 → 4.164.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

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


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 force-pushed the renovate/wrangler-4.x branch from ff61b52 to 19fd5cf Compare November 19, 2026 13:07
@renovate
renovate Bot force-pushed the renovate/wrangler-4.x branch from 19fd5cf to 7af0c4f Compare November 20, 2026 17:02
@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 20, 2026
@sonarqubecloud

Copy link
Copy Markdown

@kruton
kruton merged commit a05ccb8 into develop Nov 20, 2026
15 checks passed
@kruton
kruton deleted the renovate/wrangler-4.x branch November 20, 2026 17:15
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.

1 participant