chore(deps): update external dev fixes by renovate[bot] · Pull Request #195 · adobe/da-collab

renovate · 2026-08-31T20:48:46Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
lint-staged	`17.3.0` → `17.6.0`
mocha-multi-reporters	`1.5.1` → `1.5.2`
wrangler (source)	`4.119.0` → `4.141.0`

Release Notes

lint-staged/lint-staged (lint-staged)

`v17.6.0`

Compare Source

Minor Changes

#1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

import { defineConfig } from 'lint-staged/config'

export default defineConfig({
  '*': {
    title: 'Fail if PDF files are committed',
    task: async (filepaths, { log }) => {
      const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
      if (pdfFiles.length > 0) {
        log('PDF files should not be committed: %s', pdfFiles)
        throw new Error('Failed')
      }
    },
  },
})

#1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

#1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.
#1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):
```
import { defineConfig } from 'lint-staged/config'

export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
})
```
#1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.
#1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

`v17.5.1`

Compare Source

Patch Changes

#1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

`v17.5.0`

Compare Source

Minor Changes

#1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.

Patch Changes

#1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.
#1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.
#1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

`v17.4.1`

Compare Source

Patch Changes

#1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

stanleyhlng/mocha-multi-reporters (mocha-multi-reporters)

`v1.5.2`

Compare Source

cloudflare/workers-sdk (wrangler)

`v4.141.0`

Compare Source

Minor Changes

#15658 8280086 Thanks @jqmmes! - Add Durable Objects code update strategies to Worker deployments

Use --durable-objects-code-update-mode immediate with wrangler deploy, wrangler versions deploy, and wrangler rollback to update code without waiting for active instances to hibernate. Use --durable-objects-code-update-mode deferred 30s to set a maximum delay, or configure durable_objects.code_update_strategy with mode and max_delay. When unset, the strategy defaults to deferred with a 5-minute maximum delay; delays cannot exceed 24 hours and must use millisecond precision.
#15800 bd56b98 Thanks @Refaerds! - Add Browser Run as an event source for Queue subscriptions

You can now create Queue subscriptions with --source browserRun.

Patch Changes

#15864 ee2b200 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260923.1 ^5.20260925.1

workerd 1.20260923.1 1.20260925.1
#15207 805af2f Thanks @exKAZUu! - Show the stack and cause of failed proxied requests in wrangler dev debug logs

When a request proxied to the local Worker fails, running with --log-level debug now shows the underlying error's stack and cause chain.
Updated dependencies [ee2b200, c91279b]:
- miniflare@5.20260925.0-alpha

`v4.140.0`

Compare Source

Minor Changes

#15822 8f7916c Thanks @GregBrimble! - Support Containers in Worker Preview deployments with the Build Output.

Patch Changes

Updated dependencies []:
- miniflare@5.20260923.0-alpha

`v4.139.0`

Compare Source

Minor Changes

#15792 479e1e8 Thanks @flakey5! - Configure SSH for experimental Durable Object-managed Containers

Set containers[].ssh and containers[].authorized_keys when using scheduling_policy: "durable_object". These are application-wide settings that follow the same rules as the existing Durable Object-managed Container settings: normal deployments create missing applications and update explicitly configured values, while omitted settings preserve the existing application configuration.
```
// wrangler.jsonc
{
  "containers": [
    {
      "name": "sandbox",
      "class_name": "Sandbox",
      "scheduling_policy": "durable_object",
      "ssh": { "enabled": true },
      "authorized_keys": [
        { "name": "laptop", "public_key": "ssh-ed25519 AAAA..." }
      ]
    }
  ]
}
```
#15648 52c0e9f Thanks @tpmmorris! - Expose configured Cron Triggers to local development consumers

Wrangler now passes the active environment's exact Cron Trigger expressions to Miniflare so Local Explorer can display them. Headless agent sessions also advertise the Local Explorer scheduled invocation API.
#15786 bdda4c3 Thanks @ThomasRubini! - Support UDP connect handlers in local development

The experimental connect configuration now accepts protocol: "udp", with optional idle_timeout_ms and max_pending_bytes settings. UDP datagrams are delivered to the Worker's connect() handler using workerd's value-mode socket streams, and can be tested with Miniflare#dispatchConnect({ protocol: "udp" }).
#15779 fc3cbaa Thanks @Naapperas! - Support workflow entries in the exports configuration map

A Worker can now declare the Workflows it defines in exports, keyed by the WorkflowEntrypoint class name:
```
{
  "exports": {
    "MyWorkflow": {
      "type": "workflow",
      "name": "my-workflow",
      "limits": { "steps": 100 },
      "schedules": "0 * * * *"
    }
  }
}
```
A workflow export accepts the same settings as a workflows binding: limits, concurrency, schedules, and default_retention. wrangler deploy and wrangler versions upload send these entries to the upload API by name, and wrangler deploy and wrangler triggers deploy provision the Workflow with its settings, just as they do for workflows bindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export. @cloudflare/config adds the matching exports.workflow() helper. Local development does not yet act on these entries.

Patch Changes

#15796 be72815 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260921.1 ^5.20260923.1

workerd 1.20260921.1 1.20260923.1
#14847 940c692 Thanks @TheSaiEaranti! - Emulate the deterministic-ID uniqueness contract in the local Workflows binding

The local Workflows binding now matches the documented production behavior for deterministic instance IDs: create({ id }) with an ID that already exists throws (instance.already_exists) and retains the existing instance, and createBatch() skips IDs that already exist or repeat within the batch, excluding them from the result instead of creating duplicate executions. Previously both paths silently created duplicates, so code relying on deterministic IDs for idempotency (for example a Queue consumer creating one workflow per message) appeared to work locally while double-executing workflow bodies.
#15803 cd60c9c Thanks @pmiguel! - Show --jurisdiction in help for wrangler kv namespace create

The option was supported but omitted from the command's help output. Users can now discover how to create KV namespaces in a specific jurisdiction.
#15838 15799d4 Thanks @oddharsh! - Update smol-toml to 1.9.0 to fix slow parsing of very large TOML files

Parse time for TOML config files now grows linearly with their size, instead of with its square: a 40,000-line file that took 259 ms to parse now takes 17 ms, while typical wrangler.toml files parse in the same time as before. This addresses the GHSA-r4xh-jqrq-34v2 advisory against earlier versions of the parser.

Some TOML syntax errors now point at the character that caused them. For example, a wrangler.toml containing INVALID "FILE is now reported as illegal character in key at the ", rather than incomplete key-value at the start of the line.
Updated dependencies [52c0e9f, 44f5295, be72815, 940c692, bdda4c3, fc3cbaa]:
- miniflare@5.20260923.0-alpha

`v4.138.0`

Compare Source

Minor Changes

#15776 b03f960 Thanks @edevil! - Add event-code support to temporary Worker deployments

Use wrangler deploy --temporary --event-code <code> to provision an account for an event. Wrangler requires explicit server acknowledgement before caching the account and keeps the event code out of its cache and telemetry.
#15817 6e77c53 Thanks @jamesopstad! - Allow framework commands to produce Preview Build Output with the experimental config

When cf previews deploy invokes a framework build command, Preview intent is now preserved. Function-based cloudflare.config.ts files receive isPreview: true, and generated Build Output is marked as a Preview build.

Patch Changes

#15806 8fade73 Thanks @NuroDev! - Standardize Zod validation error output

Format validation errors with Zod's built-in prettifyError() helper so Miniflare, Wrangler, the Vite plugin, and the Vitest plugin show consistent messages and property paths.
Updated dependencies [a71237a, 8fade73]:
- miniflare@5.20260921.1-alpha

`v4.137.0`

Compare Source

Minor Changes

#15778 cd7508c Thanks @jamesopstad! - Generate types during development and supported builds with Vite's experimental.newConfig option or Wrangler's --experimental-new-config flag (and --experimental-cf-build-output for builds)

When Wrangler's --experimental-new-config flag or Vite's experimental.newConfig option is enabled, inferred configuration and runtime declarations are now kept in .cloudflare/types/index.d.ts. Vite refreshes them during development and production builds. Wrangler refreshes them during development and when building with both --experimental-new-config and --experimental-cf-build-output. In the experimental wrangler.config.ts format, the types option is now top-level because it applies to both commands.

Patch Changes

#15765 1bdb96d Thanks @th0m! - Prepare the required egress sidecar for local Containers without configured images

Wrangler dev and Vite dev/preview now pull the required sidecar for Durable Object-managed Containers that select their application image at start time. Previously, these Containers failed to start unless the sidecar image was already cached in Docker.
#15712 f5605f5 Thanks @alsuren! - Match D1 SQL statement splitting to the local SQLite runtime

Wrangler now uses SQLite's statement-completion state machine when splitting D1 SQL files. This keeps trigger, quoted identifier, comment, and keyword handling consistent with local execution.

`v4.136.3`

Compare Source

Patch Changes

#15662 59267fc Thanks @oddharsh! - Update smol-toml to 1.8.0

This updates the bundled TOML parser that reads wrangler.toml to a version that addresses two advisories against 1.5.2: GHSA-7w5x-hrqm-74c2 (a value followed by a comment with no trailing newline, such as a=[1 #, put the parser in an infinite loop) and GHSA-v3rj-xjv7-4jmq (thousands of consecutive comment lines overflowed the stack). On the old version, wrangler deploy against a wrangler.toml ending in a=[1 # never returned; it now fails with Invalid TOML document: cannot find end of structure.
#15760 6906bf0 Thanks @yomna-shousha! - Warn when wrangler preview returns only non-custom-domain URLs even though custom-domain Preview URLs are configured.
#15761 354ebdb Thanks @podonnell-dev! - Fix Preview output artifacts to always include the resolved parent Worker name

Preview artifacts now use Wrangler's resolved Worker name instead of relying on the Preview API response to include it.
Updated dependencies []:
- miniflare@5.20260921.0-alpha

`v4.136.2`

Compare Source

Patch Changes

#15762 ad20547 Thanks @podonnell-dev! - Fix wrangler types generating runtime headers with trailing whitespace

Runtime type headers without compatibility flags now end at the compatibility date, keeping generated types reproducible when tools remove trailing whitespace.
#15703 02c1d83 Thanks @KianNH! - Improve Container image listing and deletion

List all image pages using read-only credentials, validate tags before deletion, and report successful deletion when the garbage-collection request fails.
#15700 275184d Thanks @KianNH! - Fix Container SSH connection setup and shutdown

Prevent SSH connections from stalling during setup and ensure proxy processes exit when sessions close.
#15759 bd59eca Thanks @petebacondarwin! - Show valid sha256-prefixed tags in Container image listings

Container image listings now distinguish valid OCI tags such as sha256-release from synthetic digest entries such as sha256:<digest>.
Updated dependencies []:
- miniflare@5.20260921.0-alpha

`v4.136.1`

Compare Source

Patch Changes

#15744 0ed4c54 Thanks @podonnell-dev! - Improve wrangler preview onboarding guidance

Wrangler now displays placeholder replacement guidance directly beneath the suggested Preview configuration instead of as a separate warning. JSON output continues to include the guidance in its structured onboarding messages.
#15678 703922d Thanks @christhorwarth! - Read workers.dev URLs from the Worker resource during deployment

Wrangler no longer requires account-level subdomain permission to display Worker and version-preview URLs. It now uses the Worker-scoped URL fields while preserving account-level registration for accounts without a workers.dev subdomain.
Updated dependencies [14d946d]:
- @cloudflare/unenv-preset@2.16.2

`v4.136.0`

Compare Source

Minor Changes

#15713 3c75cad Thanks @jamesopstad! - Identify experimental Build Output resource configs by filename and location

The root remains config.json, Worker configs are now worker.config.json, and Container configs are now container.config.json. Resource configs no longer contain top-level type discriminators, while settings and build context are stored together in the root config.
#15713 3c75cad Thanks @jamesopstad! - Define experimental Cloudflare configuration with a single default export

Experimental cloudflare.config.ts files now define settings and resources together in a default-exported defineConfig() call. Add a Worker under worker, add Containers to the containers array, or omit both to provide settings only.
```
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };

export default defineConfig({
	accountId: "...",
	complianceRegion: "public",
	worker: {
		name: "my-worker",
		compatibilityDate: "2026-09-18",
		entrypoint,
	},
});
```
#15720 35668d7 Thanks @alexkli! - Add experimental --zone and --zone-id flags to wrangler deploy and wrangler triggers deploy to attach a zone to routes passed via --route

Routes passed on the command line were always sent to the Cloudflare API as bare patterns. Zones with an SSL for SaaS entitlement reject such routes with error 10082 ("When using wildcard host ssl for saas entitlement you must specify the zone per route using zone_id or zone_name"), and until now the only way to set a zone was in the config file, which --route overrides.

The new flags are experimental and must be enabled with --experimental-route-zones (alias --x-route-zones). Pass a single zone to apply it to all routes, or one zone per route in the same order as the --route flags:

wrangler deploy --x-route-zones --route "app.example.com/*" --route "api.example.com/*" --zone example.com

wrangler deploy --x-route-zones --route "a.example.com/*" --zone example.com --route "b.example.net/*" --zone example.net

--zone sets zone_name and --zone-id sets zone_id on each route. The two flags cannot be combined, and passing more than one zone requires exactly one per --route. Routes without zone flags behave exactly as before.
#15699 45b3b81 Thanks @skepticfx! - Remove the experimental Container image environment binding

Durable Object-managed Containers now use ctx.container.images without Wrangler generating env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Update code using the experimental environment binding to read ctx.container.images and regenerate your Worker types.

Version deployments identify managed applications from native named images, and --containers-rollout=none preserves native Container metadata. Containers without named images must first be provisioned with wrangler deploy; versions upload verifies that their applications already exist. The old binding is no longer read or reserved, including on previously uploaded versions. keep_vars retains existing variables as usual; redeploy without it to remove an existing experimental binding.
#15702 8235e6a Thanks @podonnell-dev! - Return structured configuration errors from wrangler preview --json

When a Worker is missing its Preview configuration, JSON mode now returns an error, a suggested_config patch, and any associated onboarding messages without interactive output or terminal formatting. This changes the private-beta Preview command to make automated onboarding reliable.
#15577 731a2ee Thanks @sdnts! - Add support for jurisdictions to Queues subcommands

Patch Changes

#15711 91e2f86 Thanks @ghostwriternr! - Allow local Container images without exposed ports

Wrangler and the Cloudflare Vite plugin no longer reject images that omit Docker EXPOSE metadata. Local Containers can run command-only workloads or serve traffic through workerd without declaring an unused image port.
#15740 c5913a6 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260918.1 ^5.20260921.1

workerd 1.20260918.1 1.20260921.1
#15471 0751490 Thanks @edmundhung! - Fix cf builds for static projects that serve assets from the project root

The experimental Build Output path now omits the reserved .cloudflare directory when the project root is used for static assets. This prevents recursive output copying in Wrangler while preserving the existing behaviour for other asset directories.
#15440 43b1f85 Thanks @HuzaifaAbdulRehman! - Rebase absolute non-JavaScript module specifiers when preserve_file_names is enabled

With preserve_file_names set, a non-JS module imported by an absolute path kept that path as its module name. The build machine's filesystem layout ended up inside the deployed Worker, and the module was never written to --outdir. A local dry run reported success while the upload failed server-side with error code 10021. Tooling that rewrites externals to absolute paths hits this, which is how it was found in @opennextjs/cloudflare with WASM imports.

Absolute specifiers are now rebased to ./<basename>, which is what the hashed branch of the same code already does minus the hash prefix. Relative specifiers keep the behaviour they had.
Updated dependencies [c5913a6, 3c75cad]:
- miniflare@5.20260921.0-alpha

`v4.135.0`

Compare Source

Minor Changes

#15609 1f070c8 Thanks @emily-shen! - Build Containers when emitting experimental Build Output

Wrangler and the Cloudflare Vite plugin now build Dockerfile-backed Container images when experimental Build Output is enabled. Container configs are emitted under .cloudflare/output/v0/containers with local image references, while existing registry references pass through unchanged.
#15329 c4c9b75 Thanks @akshitsinha! - Evaluate Flagship flags locally during development

Flagship bindings now use the local Miniflare store by default in Wrangler and the Vite plugin, keeping development offline and isolated from production flags. Set remote: true on a binding to continue using its remote app.

Use wrangler flagship flags pull <APP_ID> to seed the store from a remote app. Flag management commands also accept --local to read and update the local store directly.
#15701 643e5cc Thanks @WillTaylorDev! - Pass Preview intent to defineWorker and upload its resolved configuration

Preview builds now evaluate programmatic Worker configuration with ctx.isPreview set to true and record that intent in Build Output. The shared Preview uploader deploys the resolved bindings and settings while preserving configured Preview base values when it creates a Preview.

Patch Changes

#15705 a0485d5 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260917.1 ^5.20260918.1

workerd 1.20260917.1 1.20260918.1
#15587 629ddef Thanks @Kuldeeep18! - Fix duration calculation for running workflow instances, steps, and attempts in wrangler workflows instances describe

wrangler workflows instances describe previously distorted the elapsed duration of in-progress instances, steps, and attempts across non-UTC timezones by stripping " GMT" from toUTCString(), causing new Date(...) to parse the timestamp in the local client timezone. The duration is now correctly computed against the current time.
Updated dependencies [a0485d5]:
- miniflare@5.20260918.0-alpha

`v4.134.0`

Compare Source

Minor Changes

#15684 6874aa9 Thanks @Ankcorn! - Add support for configuring real-time Issues with observability.issues.enabled

Wrangler now validates and uploads the Issues setting alongside the existing logs and traces observability options. The experimental configuration format supports the equivalent observability.issues.enabled option.
#15681 d96b319 Thanks @podonnell-dev! - Mark wrangler preview commands as open beta

Wrangler now labels Preview commands as open beta in help output and command warnings, matching the feature's public availability.
#15673 2b39fc2 Thanks @ghostwriternr! - Support explicit named Container image selection in Wrangler local development

Wrangler builds or pulls named images configured through Wrangler JSON or TOML and exposes their local tags through ctx.container.images. Pass one of those references to ctx.container.start({ image }) to select the image.

This extends the experimental Durable Object-managed Containers interface. Named images are opt-in and do not become the Container's default image. A Container without a default image must supply an image or full Container snapshot when starting.

Patch Changes

#15689 876eea1 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260916.1 ^5.20260917.1

workerd 1.20260916.1 1.20260917.1
Updated dependencies [2298cf1, 876eea1]:
- miniflare@5.20260917.0-alpha

`v4.133.0`

Compare Source

Minor Changes

#15600 bac0c6a Thanks @podonnell-dev! - Add placement configuration for Previews

You can now configure placement in the previews block. Preview-specific placement overrides the top-level placement configuration for Preview Defaults and deployments.
#15600 bac0c6a Thanks @podonnell-dev! - Improve onboarding guidance for Previews (when previews block is missing from configuration file)

When a local previews block is absent, Wrangler writes the Preview Base configuration to the local config file. When no Preview Base configuration exists, Wrangler prints a placeholder configuration derived from production bindings and warns against reusing production binding configuration.

Patch Changes

#15483 71b6f10 Thanks @tpmmorris! - Align Local Explorer Workflow instance status requests with production

Local Explorer and Wrangler local mode now use the production-compatible status request field for pausing, resuming, restarting, and terminating Workflow instances. Direct Local Explorer API consumers must replace the previous action field with status.

Successful Local Explorer status updates now return the production-compatible instance status and response timestamp instead of the local-only result.success acknowledgement.
#15665 ad23e6e Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260915.1 ^5.20260916.1

workerd 1.20260915.1 1.20260916.1
#15655 be2437a Thanks @WillTaylorDev! - Send exports with Worker Preview deployments

wrangler preview dropped the exports block from deployment requests. Durable Objects reached through ctx.exports had no Preview namespace, and cache settings for each entrypoint were lost too.
Updated dependencies [71b6f10, ad23e6e, 6f3d7b5]:
- miniflare@5.20260916.0-alpha

`v4.132.0`

Compare Source

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 overri

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Zurich)

Branch creation
- "after 2pm on Monday"
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2026-08-31T20:48:49Z

⚠️ 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 warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: wrangler@4.141.0
npm error Found: @cloudflare/workers-types@5.20260804.1
npm error node_modules/@cloudflare/workers-types
npm error   @cloudflare/workers-types@"5.20260804.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @cloudflare/workers-types@"^5.20260925.1" from wrangler@4.141.0
npm error node_modules/wrangler
npm error   dev wrangler@"4.141.0" from the root project
npm error
npm error Conflicting peer dependency: @cloudflare/workers-types@5.20260926.1
npm error node_modules/@cloudflare/workers-types
npm error   peerOptional @cloudflare/workers-types@"^5.20260925.1" from wrangler@4.141.0
npm error   node_modules/wrangler
npm error     dev wrangler@"4.141.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-10T06_40_25_022Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-10T06_40_25_022Z-debug-0.log

renovate Bot changed the title ~~chore(deps): update dependency wrangler to v4.123.0~~ chore(deps): update dependency wrangler to v4.124.0 Sep 1, 2026

renovate Bot force-pushed the renovate-external-dev-fixes branch 5 times, most recently from 2cdd1af to 6187a7c Compare September 4, 2026 00:11

renovate Bot changed the title ~~chore(deps): update dependency wrangler to v4.124.0~~ chore(deps): update dependency wrangler to v4.125.0 Sep 4, 2026

renovate Bot force-pushed the renovate-external-dev-fixes branch from 6187a7c to d3945b4 Compare September 8, 2026 23:36

renovate Bot changed the title ~~chore(deps): update dependency wrangler to v4.125.0~~ chore(deps): update dependency wrangler to v4.126.0 Sep 8, 2026

renovate Bot force-pushed the renovate-external-dev-fixes branch from d3945b4 to 31e9add Compare September 10, 2026 12:38

renovate Bot changed the title ~~chore(deps): update dependency wrangler to v4.126.0~~ chore(deps): update external dev fixes Sep 10, 2026

renovate Bot force-pushed the renovate-external-dev-fixes branch 5 times, most recently from 4695d54 to c1a4a80 Compare September 17, 2026 22:12

renovate Bot force-pushed the renovate-external-dev-fixes branch 6 times, most recently from d159cdb to c3881e1 Compare September 25, 2026 18:11

renovate Bot force-pushed the renovate-external-dev-fixes branch 6 times, most recently from f8448b7 to 82deb4c Compare October 5, 2026 19:58

renovate Bot force-pushed the renovate-external-dev-fixes branch from 82deb4c to 3bdc9fe Compare October 6, 2026 12:10

renovate Bot force-pushed the renovate-external-dev-fixes branch 10 times, most recently from afd7f6a to 2684d73 Compare October 9, 2026 20:11

chore(deps): update external dev fixes

1d37731

renovate Bot force-pushed the renovate-external-dev-fixes branch from 2684d73 to 1d37731 Compare October 10, 2026 06:40

Navigation Menu

Repository navigation

chore(deps): update external dev fixes - #195

chore(deps): update external dev fixes#195
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-external-dev-fixes

renovate Bot commented Aug 31, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Aug 31, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Dependency	From	To
@cloudflare/workers-types	^5.20260923.1	^5.20260925.1
workerd	1.20260923.1	1.20260925.1

Dependency	From	To
@cloudflare/workers-types	^5.20260921.1	^5.20260923.1
workerd	1.20260921.1	1.20260923.1

Dependency	From	To
@cloudflare/workers-types	^5.20260918.1	^5.20260921.1
workerd	1.20260918.1	1.20260921.1

Dependency	From	To
@cloudflare/workers-types	^5.20260917.1	^5.20260918.1
workerd	1.20260917.1	1.20260918.1

Dependency	From	To
@cloudflare/workers-types	^5.20260916.1	^5.20260917.1
workerd	1.20260916.1	1.20260917.1

Dependency	From	To
@cloudflare/workers-types	^5.20260915.1	^5.20260916.1
workerd	1.20260915.1	1.20260916.1

Conversation

renovate Bot commented Aug 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

renovate Bot commented Aug 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Aug 31, 2026 •

edited

Loading

renovate Bot commented Aug 31, 2026 •

edited

Loading