Skip to content

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

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

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

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 4.163.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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@hivecommons-hive

hivecommons-hive Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

ℹ️ Sentinel: informational, author is trusted (allow-listed bot), merge is not blocked. Head 4ab98aff1431 matched:

  • sensitive_path: changes 2 sensitive path(s) (package-lock.json, package.json)

No sentinel-alert label was added. The finding is recorded in the dashboard Security tab and /api/sentinel; set sentinel.trusted_authors_block: true to block trusted authors too.

Ready for a human merge: verdict approved 4ab98af, 5/5 checks green, soak 30m0s elapsed. Auto-merge is off for this repo, so a person merges.

The hive never approves on your behalf: approve and merge it on GitHub if you accept it.

@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/060-reviewed Review swarm verdict approve; a gate is still pending (CI running, soak not started) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing labels Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/090-ready-for-human-merge Hive would merge this but trust/role blocks it; a maintainer's /lgtm /approve is all that is missing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants