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

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

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@redocly/cli	`2.44.1` → `2.54.2`
lint-staged	`17.3.0` → `17.5.1`
wrangler (source)	`4.119.0` → `4.136.3`

Release Notes

Redocly/redocly-cli (@redocly/cli)

`v2.54.2`

Compare Source

Patch Changes

Updated @redocly/config to v0.57.0.

Patch Changes

Added start and end line and column positions to each problem location in the --format=json lint output.

`v2.53.1`

Compare Source

`v2.53.0`

Compare Source

Minor Changes

Added a disallowDefault option to the operation-2xx-response rule, which requires an explicit 2xx response when enabled.
There is no change in current behavior.

`v2.52.1`

Compare Source

`v2.52.0`

Compare Source

Minor Changes

Added a strategy option to the component-name-unique rule, matching the --component-names-strategy option of the bundle command.

Patch Changes

Updated @redocly/config to v0.56.0.

`v2.51.2`

Compare Source

Patch Changes

Fixed an issue where Redocly config resolution failed when plugins used ESM syntax.

`v2.51.1`

Compare Source

`v2.51.0`

Compare Source

Patch Changes

Fixed an issue where respect and the x-security-scheme-required-values rule incorrectly rejected x-security HTTP schemes written with non-lowercase casing (such as Basic, Bearer, or Digest).
RFC 7235 scheme names are case-insensitive.

`v2.50.0`

Compare Source

Minor Changes

Added a new schema assertion for configurable rules.
The assertion validates a property value against a JSON Schema.

`v2.49.1`

Compare Source

Patch Changes

Updated @redocly/config to v0.55.0.
Fixed an issue where rule incorrectly reported a duplicate parameter when two or more $refs pointed to the same path item.
Updated @redocly/config to v0.54.0.

`v2.49.0`

Compare Source

Minor Changes

Added the no-illogical-composition-keywords rule.

Note: the rule is set to warn in the recommended ruleset and to error in recommended-strict. Existing API descriptions may report new problems.

`v2.48.0`

Compare Source

Patch Changes

Fixed an issue where the bundle command didn't resolve $refs inside an AsyncAPI 3 Multi Format Schema Object.

`v2.47.0`

Compare Source

Minor Changes

Added a Vendor Extensions metric to the stats command that reports how many distinct x- extensions a description file uses and how often each one occurs.

Patch Changes

Fixed the stats command reporting wrong parameter count for AsyncAPI descriptions.

`v2.46.2`

Compare Source

Patch Changes

Improved the error message raised when a configurable rule is missing the assertions block.
Fixed an issue where the no-duplicated-enum-values rule didn't report duplicated enum values that are objects or arrays.

Fixed an issue where the no-duplicated-enum-values rule printed [object Object] when reporting duplicate values.

`v2.46.1`

Compare Source

Patch Changes

Updated @redocly/ajv to ^8.18.3.

`v2.46.0`

Compare Source

Minor Changes

Added the spec-ref-siblings rule that reports properties placed next to a $ref which the specification does not allow.

`v2.45.0`

Compare Source

Minor Changes

Fixed the bundle command losing schema keywords (such as title, properties, or required) written next to a $ref when the referenced schemas started with their own $ref.

`v2.44.2`

Compare Source

Patch Changes

Changed the severity of the security-defined rule for AsyncAPI 2.x and 3.x in the recommended ruleset from error to warn.
AsyncAPI descriptions with undefined or unresolved security no longer fail linting by default.

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

`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.

cloudflare/workers-sdk (wrangler)

`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 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

`v4.131.2`

Compare Source

Patch Changes

Updated dependencies [8997652]:
- miniflare@5.20260911.1-alpha

`v4.131.1`

Compare Source

Patch Changes

#15592 945aaa3 Thanks @WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.
#15592 945aaa3 Thanks @WillTaylorDev! - Clarify production status labels for custom domain routes

Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.
#15602 47d906f Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260910.1 ^5.20260911.1

workerd 1.20260910.1 1.20260911.1
#15592 945aaa3 Thanks @WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.
#15592 945aaa3 Thanks @WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.
Updated dependencies [47d906f, c2699bf]:
- miniflare@5.20260911.0-alpha

`v4.131.0`

Compare Source

Minor Changes

#15480 36aed7f Thanks @skepticfx! - Add Durable Object-managed Containers to top-level container configuration

Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

Durable Object-managed entries accept class_name, scheduling_policy, an optional `

❗ 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:29:51Z

⚠️ 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.136.3
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.20260921.1" from wrangler@4.136.3
npm error node_modules/wrangler
npm error   dev wrangler@"4.136.3" from the root project
npm error
npm error Conflicting peer dependency: @cloudflare/workers-types@5.20260922.1
npm error node_modules/@cloudflare/workers-types
npm error   peerOptional @cloudflare/workers-types@"^5.20260921.1" from wrangler@4.136.3
npm error   node_modules/wrangler
npm error     dev wrangler@"4.136.3" 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-06T17_43_17_990Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-06T17_43_17_990Z-debug-0.log

renovate Bot force-pushed the renovate-external-dev-fixes branch 5 times, most recently from 682c314 to 7b78bc6 Compare September 8, 2026 09:29

renovate Bot force-pushed the renovate-external-dev-fixes branch 7 times, most recently from fda43e6 to 030c7ef Compare September 15, 2026 21:35

renovate Bot force-pushed the renovate-external-dev-fixes branch 7 times, most recently from 3288084 to ec1edf3 Compare September 23, 2026 02:29

renovate Bot force-pushed the renovate-external-dev-fixes branch 9 times, most recently from 6f8371e to 04ec941 Compare October 1, 2026 17:11

renovate Bot force-pushed the renovate-external-dev-fixes branch from 04ec941 to 306f4a8 Compare October 2, 2026 15:33

renovate Bot force-pushed the renovate-external-dev-fixes branch 2 times, most recently from 6c618c5 to 583bb29 Compare October 6, 2026 12:11

chore(deps): update external dev fixes

72b5978

renovate Bot force-pushed the renovate-external-dev-fixes branch from 583bb29 to 72b5978 Compare October 6, 2026 17:43

Navigation Menu

Repository navigation

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

chore(deps): update external dev fixes#317
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!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

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

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

Dependency	From	To
@cloudflare/workers-types	^5.20260910.1	^5.20260911.1
workerd	1.20260910.1	1.20260911.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

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch 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

Patch Changes

Patch Changes

Minor 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!

This branch has not been deployed

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