chore(deps): update cloudflare by renovate[bot] · Pull Request #46 · sleeyax/world-time-api

renovate · 2026-07-01T23:14:24Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	`4.20260613.1` → `4.20260702.1`
wrangler (source)	`4.100.0` → `4.120.0`

Release Notes

cloudflare/workerd (@cloudflare/workers-types)

cloudflare/workers-sdk (wrangler)

`v4.120.0`

Compare Source

Minor Changes

#15008 35c87e9 Thanks @skepticfx! - Adds the ability to find container instances by exact ID or name

wrangler containers instances <application_id> --search <instance_id_or_name> now searches every page and returns exact matches in human-readable or JSON output. JSON returns a top-level array, including an empty array when there is no match, while human-readable output prints a no-match message. If multiple instances have the same exact name, every matching instance is returned.
#15008 35c87e9 Thanks @skepticfx! - Add explicit pagination to container instance JSON output

Use wrangler containers instances <application_id> --json --per-page <size> to return one page with machine-readable result_info, then pass its next_page_token to --page-token to retrieve the next page. Plain --json remains backward-compatible: it requests the complete list and returns the existing top-level array.

Patch Changes

#15013 8cf78c8 Thanks @dario-piotrowicz! - Update undici from 7.28.0 to 7.29.0
#15015 a60ff4d Thanks @nickpatt! - Cut the per-request cost of local observability capture

Every tail event was written to the trace store as its own Durable Object call, so a request paid two or three round-trips per span. On a module-heavy app under the Vite plugin that dominated dev request latency. Rows are now buffered and written in batches, taking a request from roughly thirty calls to three.

Work in progress still shows up as it happens: the root span is written immediately, console logs and exceptions as they arrive, and a span's completion is written on the next event once 100ms has passed. An invocation that goes completely quiet writes nothing further until it ends, since the flush is driven by tail events rather than a timer.

The Vite plugin's own router, asset and proxy workers are also no longer captured. Their traces were noise the Observability views already hid, and skipping them cuts the spans recorded per request — a side benefit being that a trace's root is now your Worker rather than __router-worker__.
Updated dependencies [b4f0c97, 8cf78c8, a60ff4d, 99eb50c]:
- miniflare@5.20260801.1-alpha

`v4.119.0`

Compare Source

Minor Changes

#14952 20470fa Thanks @nelsonjsduarte! - Add --parse-type flag to wrangler ai-search create

wrangler ai-search create now accepts --parse-type to control how a website data source discovers URLs. sitemap (the default) reads XML sitemaps; discover follows links recursively.

Previously the parse type could only be chosen through the interactive wizard, which was skipped whenever --source was supplied — so it was impossible to create a discover instance from a script.
```
wrangler ai-search create my-instance \
  --type web-crawler \
  --source https://example.com \
  --parse-type discover
```
The interactive wizard now offers Discover alongside Sitemap. --parse-type is only valid with --type web-crawler; passing it with --type builtin or --type r2 is rejected, since the API stores the value for those source types but never reads it. When the flag is omitted in non-interactive mode the field is left unset and the API default (sitemap) applies.
#14941 266172b Thanks @nickpatt! - Improve the Local Explorer's Observability views

console.log messages now render the way the console would (JSON-encoded strings are unwrapped and multi-argument logs are joined), traces and events can be looked up by trace or span id from the search bar, and an event's "View trace" button jumps to the exact invocation that emitted it — even when a trace_id spans several invocations (e.g. a subrequest or self fetch).
#14064 a9e5abb Thanks @petebacondarwin! - Add support for OAuth 2.0 Device Authorization Grant to wrangler login

Run wrangler login --device to authenticate without a local callback server. Useful in containers, remote SSH sessions, Codespaces, and any other environment where localhost:8976 is unreachable from your browser.

The new flow:
- prints the verification URL and user code to the terminal,
- attempts to open the verification URL in your default browser automatically (suppressed via --browser=false),
- and polls the token endpoint until you approve the request (with a 5-minute hard cap).
The verification URL is supplied by the authorization server, so it is rejected unless it is an https URL on the same auth domain the device code was requested from — it is never printed or opened otherwise.

--callback-host and --callback-port cannot be combined with --device, since this flow does not start a local callback server.

Patch Changes

#14984 9c74538 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260730.1 ^5.20260731.1

workerd 1.20260730.1 1.20260731.1
#15012 0d33cb8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260731.1 ^5.20260801.1

workerd 1.20260731.1 1.20260801.1
Updated dependencies [9c74538, 0d33cb8, a88d169, a88d169, daf65f2]:
- miniflare@5.20260801.0-alpha

`v4.118.0`

Compare Source

Minor Changes

#14057 cc63aae Thanks @matingathani! - Add --json flag to wrangler containers info for consistent JSON output with sibling commands list and instances
#14944 a249591 Thanks @nickpatt! - Enable local observability capture by default in dev

wrangler dev and the Vite plugin now capture request traces and console logs into the Local Explorer's Observability tab out of the box — previously this was opt-in behind X_LOCAL_OBSERVABILITY=true. Set X_LOCAL_OBSERVABILITY=false to opt out (for example if the extra per-worker collector/streaming-tail services cause trouble in a multi-process dev-registry setup).

#14919 e0bbf55 Thanks @avenceslau! - Add additional triggers to Workflows

Workers can now declaratively start a locally defined Workflow. Configure event subscriptions under triggers.events; Wrangler validates each target and updates the script's event triggers during deployment.

{
  "triggers": {
    "events": [
      {
        "type": "cf.artifacts.repo.pushed",
        "filter": {
          "namespace": "my-namespace",
          "repo_name": "my-repo"
        },
        "targets": [
          {
            "type": "workflow",
            "workflow_name": "my-workflow"
          }
        ]
      }
    ]
  }
}

Patch Changes

#14936 f92d1fc Thanks @petebacondarwin! - Fix jsx_fragment being ignored when wrangler dev runs a custom build

If your project uses a custom build and sets both jsx_factory and jsx_fragment, wrangler dev used your jsx_factory value for JSX fragments as well, so fragments compiled incorrectly. Your jsx_fragment value is now used.
#14936 f92d1fc Thanks @petebacondarwin! - Stop wrangler dev starting new work after you stop it or it reloads

Stopping wrangler dev, or having it reload after a configuration change, could still leave it starting work for the state it had just left behind: your custom build command could run once more after dev had stopped, a change to a file in your assets directory could be reported against configuration that had already been replaced, and in some cases the process could stay alive instead of exiting.

That work is now discarded, so stopping or reloading wrangler dev leaves nothing running behind it.
#14936 f92d1fc Thanks @petebacondarwin! - Stop wrangler dev from running custom builds concurrently

When several watched files changed at once — for example during a git pull or a "save all" — wrangler dev started a custom build for every file that changed, so multiple copies of your build command ran at the same time and fought over the same output files.

A burst of file changes now results in a single build, and a build only starts once the previous one has finished.
#13746 cec9d88 Thanks @edmundhung! - Report a clear error for account IDs that can't be used in a Cloudflare API request

Account IDs are substituted straight into Cloudflare API URL paths, so a value containing non-ASCII characters previously failed deep inside the request layer with an opaque Cannot convert argument to a ByteString error that gave no hint about which setting was at fault. Account IDs read from CLOUDFLARE_ACCOUNT_ID and from the account_id configuration field are now validated up front, and an invalid value fails with a message naming both the offending value and where it came from.

`v4.117.0`

Compare Source

Minor Changes

#14586 5a56dda Thanks @emily-shen! - Remove containerEngine from the worker options returned by unstable_getMiniflareWorkerOptions

unstable_getMiniflareWorkerOptions no longer includes containerEngine in the returned workerOptions, since the container engine is a Miniflare instance-wide setting rather than a per-worker one. Callers that build a Miniflare instance from these options should set containerEngine at the top level instead.

Patch Changes

#14586 5a56dda Thanks @emily-shen! - Rewrite local testing paths (/cdn-cgi/*)

Miniflare v5 moved its internal local testing endpoints to /cdn-cgi/local/* (and /__cf_local/* for endpoints that must remain reachable over tunnels) to prevent any potential collision with production routes. wrangler dev and the Vite plugin now transparently rewrite the old paths to the new ones, meaning you can continue to use the old paths without issue.

These are the new paths:
- /cdn-cgi/handler/scheduled → /cdn-cgi/local/scheduled
- /cdn-cgi/handler/email → /cdn-cgi/local/email
- /cdn-cgi/explorer/* → /cdn-cgi/local/explorer/*
- /cdn-cgi/mf/scheduled → /cdn-cgi/local/scheduled (Note /cdn-cgi/mf/scheduled is already deprecated)
- /cdn-cgi/mf/stream/* → /__cf_local/stream/*
- /cdn-cgi/mf/imagedelivery/* → /__cf_local/imagedelivery/*
Updated dependencies [5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda]:
- miniflare@5.20260730.0-alpha

`v4.116.0`

Compare Source

Minor Changes

#14907 beec0fb Thanks @NuroDev! - Avoid Worker and workers.dev naming prompts in agent-driven deploys

Wrangler now derives the Worker name from the project and automatically registers the same project-derived workers.dev account subdomain on a first deploy when running in a detected agent environment. The deploy output explains how to change both names.
#14905 b21eac2 Thanks @jamesopstad! - The experimental build output directory now includes the Worker's configuration at .cloudflare/output/v0/workers/default/config.json instead of .cloudflare/output/v0/workers/<worker-name>/worker.config.json
#14893 bb09f1b Thanks @apeacock1991! - Graduate wrangler check startup from alpha and show bundle size and a local timing summary

The command no longer prints an alpha warning. It now reports its local profile window, sampled active, garbage collection, and idle time alongside the raw and compressed bundle sizes. The existing measurement warning continues to distinguish these local measurements from startup time measured on Cloudflare.

#14685 01d7020 Thanks @edmundhung! - Add support for dispatching email handlers with createTestHarness

You can now call server.getWorker().email({ from, to, raw }) to dispatch directly to a Worker's email() handler and inspect its outcome, rejection reason, forwarded messages, and replies.

const result = await server.getWorker().email({
  from: "sender@example.com",
  to: "inbox@example.com",
  raw: [
    "From: Sender <sender@example.com>",
    "To: Inbox <inbox@example.com>",
    "Message-ID: <test@example.com>",
    "Subject: Test email",
    "",
    "Hello from the test harness",
  ].join("\r\n"),
});

expect(result).toMatchObject({
  outcome: "ok",
  forwards: [{ recipient: "archive@example.com" }],
  replies: [
    {
      sender: "inbox@example.com",
      raw: expect.stringContaining("Thanks for your email"),
    },
  ],
});

Patch Changes

#14929 48f0c6c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260722.1 ^5.20260730.1

workerd 1.20260722.1 1.20260730.1
#14838 8049ca4 Thanks @TheSaiEaranti! - Fix ctrl+c not being able to interrupt wrangler while waiting for Cloudflare Access authorization

When a domain is behind Cloudflare Access (for example during remote bindings startup), wrangler runs cloudflared access login, which only returns once the user completes the authorization flow in the browser. This was invoked synchronously, blocking Node's event loop, so wrangler could not react to ctrl+c (or anything else) until the authorization completed — abandoning the browser flow left a hung wrangler process that had to be killed externally. cloudflared is now spawned asynchronously, keeping wrangler responsive while it waits. The remote runtime passes its abort signal through to the spawn, so tearing down the session kills a still-pending cloudflared immediately, with process exit as a last-resort cleanup.
#14871 1394867 Thanks @nickpatt! - Include the local observability query endpoint in the agent-facing Local Explorer hint

The hint wrangler dev prints for AI-agent sessions now lists POST /cdn-cgi/explorer/api/local/observability/query, so agents can discover the read-only SQL endpoint for captured request traces and console logs (the spans and logs tables) alongside the existing binding and storage routes.
#14918 cc54478 Thanks @nickpatt! - Improve the agent-facing Local Explorer hint for the observability query endpoint

When a wrangler dev session is detected as running inside an AI agent, the hint for POST /local/observability/query now explains that the endpoint takes a read-only SQL query (SELECT/WITH only) over the captured spans and logs tables, notes that attributes is JSON (read via json(attributes)), and includes a copy-pasteable curl example. The full OpenAPI schema is demoted to a last-resort footer so agents reach for the small, actionable example first instead of fetching the large schema.
#14897 e31ab0f Thanks @ericclemmons! - Fix wrangler triggers deploy to use Vite-generated redirected configuration

The command now reads .wrangler/deploy/config.json, matching wrangler deploy and wrangler versions upload, so generated Worker names and trigger settings are applied.
Updated dependencies [01d7020, 48f0c6c, d7f38c3, 5c25cfe, 1f61001]:
- miniflare@4.20260730.0

`v4.115.0`

Compare Source

Minor Changes

#14807 4dfb96e Thanks @oOPa! - Add hidden --jurisdiction option to wrangler kv namespace create for internal testing

This option creates a KV namespace within a specific jurisdiction (for example us, eu, or fedramp), backing it with jurisdiction-scoped storage. It is experimental and currently gated to allow-listed accounts, so it is hidden from --help until the feature is generally available.
#14280 465c0fb Thanks @tahmid-23! - Add experimental local_dev.experimental_s3_credentials to r2_buckets config

When set, the R2 bucket is served over a local S3-compatible API at /cdn-cgi/local/r2/s3/<bucket-id> during local development, authenticated with the configured AWS SigV4 credentials. <bucket-id> is the bucket's bucket_name, or the binding name if bucket_name is not set:
```
{
  "r2_buckets": [
    {
      "binding": "BUCKET",
      "bucket_name": "my-bucket",
      "local_dev": {
        "experimental_s3_credentials": {
          "accessKeyId": "local-access-key-id",
          "secretAccessKey": "local-secret-access-key"
        }
      }
    }
  ]
}
```
#14877 552bcfc Thanks @jasoncabot! - Respect and surface the Retry-After header on Cloudflare API responses

Previously, if a Wrangler command (e.g. wrangler versions upload, wrangler deploy) hit the Cloudflare API's rate limit, the resulting error gave no indication of how long to wait before trying again, and 429 responses weren't retried at all (only 5xx errors were, with a fixed linear backoff).

Now:
- 429 Too Many Requests responses are automatically retried, alongside the existing 5xx retry behaviour.
- If a retried response includes a Retry-After header, Wrangler waits for that duration instead of the default backoff, and logs a message indicating how long it's waiting. To avoid blocking for an excessive amount of time, waits longer than 60 seconds fail fast instead — the surfaced Retry-After value lets the caller schedule its own retry.
- If a retryable error is ultimately surfaced to the user (e.g. because retries were exhausted), the error message includes a note with the Retry-After duration, and the command-failed entry written to the Wrangler output file (WRANGLER_OUTPUT_FILE_PATH/WRANGLER_OUTPUT_FILE_DIRECTORY) gains a retry_after_ms field. This lets scripts and CI/CD pipelines calling Wrangler repeatedly (for example, wrangler versions upload on every commit) read the wait duration directly instead of regex-parsing stderr.
APIError.isRetryable() is unchanged (still 5xx only); retryOnAPIFailure() separately retries 429s. retryAfterMs, when present, is honoured for any retried error, not just 429s.

retryAfterMs is also now populated on APIErrors raised from direct R2 object requests, the Browser Rendering API, and errors surfaced from commands using the official cloudflare SDK client.
#14712 6e0bf6e Thanks @mack-erel! - Support connect() on remote VPC Network and VPC Service bindings in local development

Remote VPC Network and VPC Service bindings previously only supported HTTP and JSRPC, so calling binding.connect(address) against a private TCP service (for example a database) failed in local dev with Incoming CONNECT on a worker not supported. Raw TCP connections through remote VPC Network and VPC Service bindings now work in local development.

This feature is experimental. Existing HTTP and JSRPC usage of remote VPC Network and VPC Service bindings is unaffected, and no new configuration is required.

Patch Changes

#14833 773ead4 Thanks @DiogoSantoss! - Color Email Routing plan change markers

Wrangler now highlights additions in green, updates in yellow, and deletions and conflicts in red so Email Routing deployment plans are easier to scan before confirmation.
#14833 773ead4 Thanks @DiogoSantoss! - Apply Email Routing changes across independent zones concurrently

Wrangler now limits concurrent zone updates while preserving the Email Routing plan order within each zone. Deployments that configure addresses across multiple zones complete faster without breaking delete-before-add transitions at a zone's rule limit.
#14815 09b8a44 Thanks @chinesepowered! - Fix wrangler cloudchamber curl mangling header values that contain a colon

Header values were split on every colon and only the segment between the first and second was sent, so --header location:https://example.com/x arrived as https. Headers are now split on the first colon only. A header that is not in the documented --header <name>:<value> form previously threw an unhandled TypeError, and now reports a clear error.
#14806 e8b3a9d Thanks @akim136! - Handle and explain authentication failures from remote bindings during local development

Wrangler now recognizes authentication failures from remote preview sessions and reports that bindings which need to run remotely require Cloudflare authentication even when the rest of the Worker is developed locally.
#14801 b737676 Thanks @emily-shen! - Speed up old debug log cleanup by reading each log file's date from its filename instead of stat-ing every file

Wrangler periodically deletes debug log files older than 30 days from its logs directory. Previously it made a filesystem stat call for each file to read its modification time; it now derives the age from the timestamp already encoded in the log filename, avoiding that extra work.
Updated dependencies [1035f74, e426cb9, 3a22ae5, 465c0fb, 6e0bf6e]:
- miniflare@4.20260722.1

`v4.114.0`

Compare Source

Minor Changes

#14633 3203b5d Thanks @nickpatt! - Add local-dev observability

wrangler dev and the Vite plugin now capture a trace for every local Worker invocation - spans, logs, and console.* output, including requests that cross worker or Durable Object boundaries.

You can explore this data two ways:
- A new Observability tab in the Local Explorer, with a Traces view (recent invocations, an inline timeline waterfall, and filters) and an Events view.
- A read-only SQL endpoint at /cdn-cgi/explorer/api/local/observability/query, discoverable via the Local Explorer's OpenAPI document, so coding agents and tools can query the same spans and logs tables.
While this is in testing it's off by default; set X_LOCAL_OBSERVABILITY=true to turn it on. It will be on by default in the public release.

Patch Changes

#14373 246ce92 Thanks @Jacroney! - Improve the D1 database-limit error message

When creating a D1 database fails because the account has hit its database limit, the error now points to the relevant next steps — upgrading on the Workers Free plan or requesting a higher limit on a paid plan — alongside the existing commands to list and delete databases. Previously it only suggested deleting unused databases. This applies both to wrangler d1 create and to the D1 database that is created during resource provisioning on deploy.
#14796 c38a2c3 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260721.1 ^5.20260722.1

workerd 1.20260721.1 1.20260722.1
#14788 8416b33 Thanks @chinesepowered! - Fix grammar in the container image-too-large error

The error thrown when a container image exceeds the available disk size ended with "Your need more disk for this image." It now reads "You need more disk for this image."
#14809 4683ff8 Thanks @jamesopstad! - Ignore the removed legacy_env field when reading a redirected configuration

Older versions of tools such as the Vite plugin can generate a redirected configuration (.wrangler/deploy/config.json) that still includes the removed legacy_env field. Since these files are tool-generated, users could not easily remove the field themselves, and Wrangler would error out. Wrangler now silently strips legacy_env from redirected configurations. User-authored configurations still report an error so that the field can be removed.
#14593 02232f3 Thanks @spk-ai! - Fix dev proxy silently hanging or returning a misleading 503 on network errors for non-root-path requests

During wrangler dev, a transient network error on any request path other than / could be misclassified as the worker being reloaded, even when it wasn't: GET/HEAD requests would silently hang (with nothing logged) until the client timed out, and other methods would receive a misleading Your worker restarted mid-request 503. Such errors are now reported and surfaced immediately when the worker has not actually changed.
#14797 f8a8c2c Thanks @roerohan! - Explain how to provision Flagship bindings if app_id missing in remote development

Wrangler now reports that a Flagship binding without an app_id must first be created with wrangler flagship apps create.
Updated dependencies [c38a2c3, c079ba3, 95b026e, c4bacec, 3203b5d]:
- miniflare@4.20260722.0

`v4.113.0`

Compare Source

Minor Changes

#14471 f03b108 Thanks @DiogoSantoss! - Apply Email Routing addresses during Worker trigger deployment

Worker trigger deployment now reconciles the Worker's Email Routing rules with the top-level addresses config. This runs for wrangler deploy, wrangler triggers deploy, and clients of @cloudflare/deploy-helpers. After the Worker uploads, or when wrangler triggers deploy runs after a version promotion, the deploy helper asks the Email Routing API for a plan, renders the changes grouped by zone (+ added, ~ updated, - deleted, ! conflict), prompts once for destructive changes in interactive mode, and applies accepted changes through the per-zone rule endpoints. Purely additive plans apply without a prompt, while non-interactive destructive plans fail without modifying rules.
#14679 deae171 Thanks @dario-piotrowicz! - Add exclude_packages option to dependencies_instrumentation configuration

The dependencies_instrumentation config object now accepts an optional exclude_packages field — an array of package name patterns (with glob-style * wildcards) to exclude from the dependency metadata collected during deploy and version uploads.
```
// wrangler.json
{
  "dependencies_instrumentation": {
    "exclude_packages": ["@internal/*", "secret-tool"]
  }
}
```
#14721 4e92e32 Thanks @dmmulroy! - Support Artifacts sources when creating Queue event subscriptions

wrangler queues subscription create now accepts the artifacts and artifacts.repo source types supported by the Cloudflare API.
#13352 d1d6945 Thanks @penalosa! - Expand automatic resource provisioning to Queue, Dispatch Namespace, and Flagship bindings

Deployments can now omit the resource name or ID for these bindings. Wrangler will inherit the existing binding on subsequent deploys, create a deterministically named resource automatically, or offer existing resources during an interactive deploy with automatic creation disabled.
#14688 a0c8bb1 Thanks @NuroDev! - Print Local Explorer API details for headless agent-driven wrangler dev sessions

When wrangler dev is started in a headless AI agent environment, Wrangler now prints the Local Explorer API URL and basic resource routes so agents can inspect local Workers and bindings without relying on the interactive UI.
#14724 a50f73a Thanks @jamesopstad! - Add a settings export to the experimental cloudflare.config.ts config

Account-level settings (accountId, complianceRegion) now live in a dedicated, named settings export authored via defineSettings, rather than on the Worker config. A cloudflare.config.ts can export at most one settings object; the Worker itself is the default export.
```
// cloudflare.config.ts
import { defineSettings, defineWorker } from "wrangler/experimental-config";
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };

export const settings = defineSettings({
	accountId: "<your-account-id>",
});

export default defineWorker({
	name: "my-worker",
	entrypoint,
	compatibilityDate: "2026-05-18",
});
```
This is only used behind the experimental new-config path (wrangler --experimental-new-config and the @cloudflare/vite-plugin experimental.newConfig option).
#14595 2b390d7 Thanks @colinhacks! - Recognise nub as a package manager

wrangler now detects nub — from its npm_config_user_agent and an installed nub binary — and autoconfig detects nub projects by their nub.lock, alongside npm, pnpm, yarn, and bun.
#14742 34430b3 Thanks @pombosilva! - Add support for redacting sensitive Workflows step output in local dev.

Steps configured with sensitive: "output" now have their output redacted to [REDACTED] in step logs and step-output responses when running Workflows locally, matching production behavior. The real value is still passed to downstream steps, and step errors are never redacted.

Patch Changes

#14715 42af66d Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

@cloudflare/workers-types ^5.20260714.1 ^5.20260721.1

workerd 1.20260714.1 1.20260721.1
#14744 a0a091b Thanks @penalosa! - Drop the "Experimental:" prefix from the resource provisioning header now that automatic provisioning is generally available. The deploy output now reads The following bindings need to be provisioned:.
#14720 0df3d43 Thanks @penalosa! - Fix remote binding previews for accounts without a workers.dev subdomain

Wrangler now automatically registers a workers.dev subdomain when one is required to start a remote binding preview.
#14773 d83a476 Thanks @chinesepowered! - Fix stray characters in the Workers Sites asset-key-too-long error

The error thrown when an asset path key exceeds the 512-character limit ended with a stray ", copy-paste artifact, so the message printed to users terminated with ...#kv-limits", and the trailing documentation URL was malformed. The message now ends cleanly at the URL.
#14766 4815711 Thanks @gianghungtien! - Report the Worker's error for HEAD requests instead of an internal JSON parse error

A Worker that threw on a HEAD request (for example curl -I) logged SyntaxError: Unexpected end of JSON input from miniflare's internals rather than the actual error, and dispatchFetch() rejected with that same misleading error. workerd drops response bodies for HEAD requests, so the serialised error never reached the code that revives it.

The error is now also carried in a header, which survives HEAD, so the original message and source-mapped stack are reported for every method. When no payload is available the reporting degrades to a plain error rather than surfacing a parse failure.
#14448 c82d96b Thanks [@GregBrimble](http

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- "on the first day of the month"
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.

👻 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 Bot force-pushed the renovate/cloudflare branch 4 times, most recently from 574e1c3 to cee20e1 Compare July 8, 2026 23:58

renovate Bot force-pushed the renovate/cloudflare branch 2 times, most recently from e4ae188 to f1f0d63 Compare July 15, 2026 11:15

renovate Bot force-pushed the renovate/cloudflare branch 4 times, most recently from 5de9db6 to 2417d35 Compare July 23, 2026 17:46

renovate Bot force-pushed the renovate/cloudflare branch 3 times, most recently from 31f6b51 to a63fb8c Compare July 31, 2026 15:40

renovate Bot force-pushed the renovate/cloudflare branch from a63fb8c to ecc592a Compare August 5, 2026 14:10

chore(deps): update cloudflare

0912b1c

renovate Bot force-pushed the renovate/cloudflare branch from ecc592a to 0912b1c Compare August 7, 2026 13:09

Navigation Menu

chore(deps): update cloudflare - #46

chore(deps): update cloudflare#46
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cloudflare

renovate Bot commented Jul 1, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Dependency	From	To
@cloudflare/workers-types	^5.20260730.1	^5.20260731.1
workerd	1.20260730.1	1.20260731.1

Dependency	From	To
@cloudflare/workers-types	^5.20260731.1	^5.20260801.1
workerd	1.20260731.1	1.20260801.1

Dependency	From	To
@cloudflare/workers-types	^5.20260722.1	^5.20260730.1
workerd	1.20260722.1	1.20260730.1

Dependency	From	To
@cloudflare/workers-types	^5.20260721.1	^5.20260722.1
workerd	1.20260721.1	1.20260722.1

Dependency	From	To
@cloudflare/workers-types	^5.20260714.1	^5.20260721.1
workerd	1.20260714.1	1.20260721.1

Conversation

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

Uh oh!

Release Notes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

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

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Jul 1, 2026 •

edited

Loading