cloudflare/workers-sdk wrangler@4.132.0

on GitHub

Minor Changes

• #14587 76c0ce6 Thanks @MattieTK! - Categorise the positional path argument to wrangler deploy and wrangler versions upload in command telemetry

  Command telemetry now records a coarse category for the entry-point/assets positional (wrangler deploy <path>) under sanitizedArgs.path, so we can understand whether people pass a file, a directory, or a relational reference such as . or ../example. The possible values are file, directory, current-dir, parent-relative, and not-found, or null when no positional is provided. The raw path is never sent — only the category.

• #15597 a83d7ac Thanks @skepticfx! - Configure application-wide logs for experimental Durable Object-managed Containers

  Set containers[].observability.enabled or containers[].observability.logs.enabled when using scheduling_policy: "durable_object". Normal deployments create missing applications and update explicitly configured log settings without a Container rollout. Omitted settings preserve the application configuration; root Worker observability is not inherited for this policy.

  Version uploads may initialize missing applications but preserve existing settings. Deploying or rolling back Worker versions also preserves existing application settings, and --containers-rollout=none skips their updates.

• #15597 a83d7ac Thanks @skepticfx! - Support per-image build options for experimental Durable Object-managed Containers

  Set build_context and build_vars alongside dockerfile in a Container's named images entries. Context paths resolve relative to the Wrangler configuration file and default to the Dockerfile's directory. Build variables are passed as Docker build arguments. Entries using the same Dockerfile with different contexts or variables are built separately.

  {
    "containers": [
      {
        "class_name": "Sandbox",
        "scheduling_policy": "durable_object",
        "images": {
          "app": {
            "dockerfile": "./docker/Dockerfile",
            "build_context": ".",
            "build_vars": { "APP_ENV": "production" }
          }
        }
      }
    ]
  }

• #15638 fa79b26 Thanks @G4brym! - Support AI Search bindings in Worker Previews

  wrangler preview now accepts ai_search and ai_search_namespaces entries in the previews block and includes them in Preview deployment bindings. This lets Workers that use AI Search instance or namespace bindings attach existing resources to Preview deployments, including preview-specific instance or namespace names.

  These bindings are non-inheritable: declare them explicitly under previews. They attach to existing AI Search resources; preview does not provision new isolated instances or namespaces.

• #15256 16d1310 Thanks @theoephraim! - [private beta]: Add --secrets-file and --var flags to wrangler preview

  Like wrangler deploy and wrangler versions upload, wrangler preview now accepts a --secrets-file flag pointing to a JSON or .env format file, and --var KEY:VALUE pairs that are injected into the Preview deployment as plain text variables. CLI vars override same-named vars from the previews section of your config file, and secrets from the file take precedence over both:

  wrangler preview --secrets-file .env.preview --var API_URL:https://api.example.com

• #15453 ca71205 Thanks @G4brym! - Remove the gated Web Search binding and Wrangler command

  The unreleased search binding and its experimental command have been removed from Wrangler, Miniflare, and configuration APIs.

• #15597 a83d7ac Thanks @skepticfx! - Allow experimental Durable Object-managed Containers to link by name through exports

  Containers using scheduling_policy: "durable_object" can now specify name and link from exports.<Class>.container without repeating class_name. Deploy and version upload resolve that link for image preparation, Worker metadata, and Container application creation.

Patch Changes

• #14775 1be7b97 Thanks @dario-piotrowicz! - Sync Local Explorer endpoint lists across agent hints

  The Local Explorer endpoint list is now consistent across the three places it appears: the AGENTS.md template in create-cloudflare, the runtime agent hint in wrangler dev, and the Vite plugin agent hint. All three now include the observability/clear endpoint, use the canonical /cdn-cgi/local/explorer path, and have cross-reference comments pointing to each other.

• #15409 b149147 Thanks @tpmmorris! - Fix per-query overrides for wrangler ai-search search

  --score-threshold, --max-num-results, --filter, and --reranking are now sent using the AI Search request schema, so the service applies them to searches instead of ignoring them.

• #15633 7db596c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @cloudflare/workers-types	^5.20260911.1	^5.20260915.1
  workerd	1.20260911.1	1.20260915.1

• #14906 a0856da Thanks @exKAZUu! - Surface the original error message, name and stack when the dev server reports an internal error

  Previously wrangler dev could exit with an empty ✘ [ERROR] log that gave no indication of what went wrong (e.g. Network connection lost., see #14641). These errors now include their original message, name and stack, so the failure is actually diagnosable.

• #15179 cb0955f Thanks @rioaguspermana! - Treat 502, 503, and 504 as gateway errors during asset upload retries

  Pages and Workers asset uploads now retry more patiently when the Cloudflare API responds with a 502, 503 or 504 gateway error, reducing concurrency and waiting longer between attempts instead of failing the deploy quickly.

• #15399 982b806 Thanks @tpmmorris! - Improve over-limit run_worker_first errors when duplicate rules are present

  The error now reports distinct and duplicate-entry counts and lists duplicated rules, making it clear when removing redundant entries can bring the configuration within the limit.

  Too many `run_worker_first` rules were provided; 105 rules provided (99 distinct, 6 duplicate entries) exceeds max of 100. Note: duplicate entries count towards the route limit. Ensure that no duplicate rules are present in your `run_worker_first` configuration.
  
  The duplicated rules found are:
  - "/rule/0"
  - "/rule/1"
  - "/rule/2"
  - "/rule/3"
  - "/rule/4"
  ...and 1 more duplicated rule.
  

• #12369 ffabe74 Thanks @43081j! - Replace execa with tinyexec for running subprocesses, shrinking the bundled Wrangler output.

• #15633 7db596c Thanks @dependabot! - Preserve service-worker middleware error propagation with spec-compliant event dispatch

  Wrangler's synthetic service-worker events now propagate listener exceptions to middleware without changing the behavior of user-created EventTarget instances.

• #15400 e03822a Thanks @james-elicx! - Reduce the size of Wrangler's published package

  Exclude test-only, build-only, and obsolete template files from the npm package while retaining all runtime templates.

• #15631 c4a6279 Thanks @petebacondarwin! - Restore static asset upload concurrency after gateway errors

  Static asset uploads previously remained at concurrency one for the rest of the deployment after any 524 response, which could make large deployments exceed the upload session lifetime. Successful uploads now restore the session's original concurrency gradually while retaining gateway throttling. Requests that were already in flight when throttling began do not restore capacity, so a burst of stale successes cannot immediately undo backpressure.

• Updated dependencies [7db596c, e35c4a1, d3565a5, ca71205, 1015cfb, 982b806, 641df47]:

  • miniflare@5.20260915.0-alpha