chore(deps-dev): bump wrangler from 4.114.0 to 4.115.0

[dependabot]

Bumps wrangler from 4.114.0 to 4.115.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.115.0

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

... (truncated)

Commits

• 760a85b Version Packages (#14824)
• ee4472a [wrangler] Remove jurisdiction field from kv_namespaces in wrangler config (#...
• 552bcfc [wrangler] Respect and surface 429 errors from HTTP requests (#14877)
• e353367 fix output comparisons for e2e tests (#14884)
• 4dfb96e [wrangler] Support jurisdictions for KV namespaces (#14807)
• 09b8a44 [wrangler] Split cloudchamber curl headers on the first colon only (#14815)
• 465c0fb [miniflare] Expose R2 via an S3-compatible API locally (#14280)
• b737676 [wrangler] Derive old log file age from filename timestamp (#14801)
• See full diff in compare view

[cloudflare-workers-and-pages]

Deploying devdocs with    Cloudflare Pages

Latest commit:	970605a
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	devdocs	970605a	Aug 01 2026, 09:56 PM

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	wrangler@​4.115.0

View full report

[GildedRoach]

@dependabot recreate