chore(deps): update dependency wrangler to v3.114.14

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	3.111.0 -> 3.114.14

---

Release Notes

cloudflare/workers-sdk (wrangler)

v3.114.14

Compare Source

Patch Changes

• #​10330 dab7683 Thanks @​petebacondarwin! - Do not attempt to update queue producer settings when deploying a Worker with a queue binding

  Previously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set different producer settings on a shared queue.

• #​10233 a00a124 Thanks @​veggiedefender! - Increase the maxBuffer size for capnp uploads

• #​10228 77a4364 Thanks @​dario-piotrowicz! - fix NonRetryableError thrown with an empty error message not stopping workflow retries locally

• Updated dependencies []:

  • miniflare@​3.20250718.1

v3.114.13

Compare Source

Patch Changes

• #​10015 b5d9bb0 Thanks @​dario-piotrowicz! - fix wrangler dev logs being logged on the incorrect level in some cases

  currently the way wrangler dev prints logs is faulty, for example the following code

  console.error("this is an error");
  console.warn("this is a warning");
  console.debug("this is a debug");

  inside a worker would cause the following logs:

  ✘ [ERROR] this is an error
  
  ✘ [ERROR] this is a warning
  
  this is a debug
  

  (note that the warning is printed as an error and the debug log is printed even if by default it should not)

  the changes here make sure that the logs are instead logged to their correct level, so for the code about the following will be logged instead:

  ✘ [ERROR] this is an error
  
  ▲ [WARNING] this is a warning
  

  (running wrangler dev with the --log-level=debug flag will also cause the debug log to be included as well)

• #​10187 f480ec7 Thanks @​workers-devprod! - Deleting when Pages project binds to worker requires confirmation

• #​10182 1f686ef Thanks @​devin-ai-integration! - fix: report startup errors before workerd profiling

• #​10226 989e17e Thanks @​petebacondarwin! - Enforce 64-character limit for Workflow binding names locally to match production validation

• #​10216 76d3002 Thanks @​devin-ai-integration! - Add macOS version validation to prevent EPIPE errors on unsupported macOS versions (below 13.5). Miniflare and C3 fail hard while Wrangler shows warnings but continues execution.

• #​10261 8c38b65 Thanks @​petebacondarwin! - fix: strip ANSI escape codes from log files to improve readability and parsing

• #​10171 0d73563 Thanks @​devin-ai-integration! - Handle UTF BOM in config files - detect and remove UTF-8 BOMs, error on unsupported BOMs (UTF-16, UTF-32)

• Updated dependencies [b5d9bb0, 76d3002]:

  • miniflare@​3.20250718.1

v3.114.12

Compare Source

Patch Changes

• #​10019 cce7f6f Thanks @​dario-piotrowicz! - chore: update workerd dependency to latest

• #​10050 ef003a2 Thanks @​emily-shen! - remove banner from r2 getobject in pipe mode

• #​10003 6940d39 Thanks @​emily-shen! - Include more (sanitised) user errors in telemetry.

  We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.

• #​9973 58c09cf Thanks @​penalosa! - Make Wrangler warn more loudly if you're missing auth scopes

• Updated dependencies [cce7f6f, 028f689]:

  • miniflare@​3.20250718.0

v3.114.11

Compare Source

Patch Changes

• #​9685 cbea64b Thanks @​WillTaylorDev! - Select only successfully deployed deployments when tailing.

• #​9776 6e09672 Thanks @​vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

• #​9694 dacfc35 Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

  this change makes sure that that getPlatformProxy, when the input configuration
  file contains an assets field, correctly returns the appropriate asset binding proxy

  example:

  // wrangler.jsonc
  {
  	"name": "my-worker",
  	"assets": {
  		"directory": "./public/",
  		"binding": "ASSETS",
  	},
  }

  import { getPlatformProxy } from "wrangler";
  
  const { env, dispose } = await getPlatformProxy();
  
  const text = await (await env.ASSETS.fetch("http://0.0.0.0/file.txt")).text();
  console.log(text); // logs the content of file.txt
  
  await dispose();

• #​9807 4dd026b Thanks @​penalosa! - Better messaging for account owned tokens in wrangler whoami

v3.114.10

Compare Source

Patch Changes

• #​9713 3ff9592 Thanks @​penalosa! - Support wrangler version upload for Python Workers

• #​9453 0e2949c Thanks @​emily-shen! - Point to the right location for docs on telemetry

• #​9594 0f2f75d Thanks @​vicb! - drop unused WRANGLER_UNENV_RESOLVE_PATHS env var

• #​9631 e101451 Thanks @​CarmenPopoviciu! - Remove "Cloudchamber" from user facing error messages

v3.114.9

Compare Source

Patch Changes

• #​9262 2c3d8dd Thanks @​workers-devprod! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #​8681 7a57c14 Thanks @​workers-devprod! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests

• #​9128 c535845 Thanks @​dario-piotrowicz! - fix: remove outdated js-doc comment for unstable_startDevWorker's entrypoint

• #​9259 b742171 Thanks @​workers-devprod! - Relax R2 bucket validation for pages dev commands

• #​9172 4e943b1 Thanks @​vicb! - validate r2 bucket names

• #​9250 b2b5ee8 Thanks @​workers-devprod! - fix: strip CF-Connecting-IP header within fetch

  In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

• #​9267 8b4f24a Thanks @​workers-devprod! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

• #​9163 d67cd0d Thanks @​petebacondarwin! - Do not report "d1 execute" command file missing error to Sentry

• #​8957 9d4ff5b Thanks @​workers-devprod! - Make sure custom build logging output is more clearly signposted, and make sure it doesn't interfere with the interactive dev session output.

• #​9166 9b4c91d Thanks @​lambrospetrou! - Fix d1 info command showing read_replication: [object Object]

• Updated dependencies [7a57c14, b2b5ee8, 56a0d6e]:

  • miniflare@​3.20250408.2

v3.114.8

Compare Source

Patch Changes

• #​9086 a2a56c8 Thanks @​petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

  Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.

• #​9037 d0d0025 Thanks @​CarmenPopoviciu! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.

• #​9093 2f2f7ba Thanks @​CarmenPopoviciu! - fix: Validate input file for Vectorize inserts

• Updated dependencies [fc04292, a01adca]:

  • miniflare@​3.20250408.1

v3.114.7

Compare Source

Patch Changes

• #​8955 b7eba92 Thanks @​workers-devprod! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

• #​8928 8bcb257 Thanks @​dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

  a validation check has recently been introduced to make wrangler error on
  deploy commands when an environment is specified and a redirected configuration
  is in use (the reason being that redirected configurations should not include
  any environment), this check is problematic with pages commands where the
  "production" environment is anyways set by default, to address this the validation
  check is being relaxed here on pages commands

v3.114.6

Compare Source

Patch Changes

• #​8783 7bcf352 Thanks @​petebacondarwin! - Improve error message when request to obtain membership info fails

  Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.

• #​8866 db673d6 Thanks @​edmundhung! - improve error message when redirected config contains environments

  this change improves that validation error message that users see
  when a redirected config file contains environments, by:

  • cleaning the message formatting and displaying the
    offending environments in a list
  • prompting the user to report the issue to the author
    of the tool which has generated the config

• #​8600 91cf028 Thanks @​workers-devprod! - add validation to redirected configs in regards to environments

  add the following validation behaviors to wrangler deploy commands, that relate
  to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

  • redirected configs are supposed to be already flattened configurations without any
    environment (i.e. a build tool should generate redirected configs already targeting specific
    environments), so if wrangler encounters a redirected config with some environments defined
    it should error
  • given the point above, specifying an environment (--env=my-env) when using redirected
    configs is incorrect, so these environments should be ignored and a warning should be
    presented to the user

v3.114.5

Compare Source

Patch Changes

• Updated dependencies [dec7e2a, db2207a]:
  • miniflare@​3.20250408.0

v3.114.4

Compare Source

Patch Changes

• #​8758 04ba075 Thanks @​emily-shen! - fix: return actual error on wrangler secret bulk

• #​8703 ef89e6b Thanks @​CarmenPopoviciu! - Improve formatting of cache options for hyperdrive list command

• #​8751 e1ef298 Thanks @​emily-shen! - fix: include documentation_url in API Errors if provided

• #​8713 47bf369 Thanks @​CarmenPopoviciu! - fix: stop getPlatformProxy crashing when internal DOs are present

  Internal DOs still do not work with getPlatformProxy, but warn instead of crashing.

• #​8683 90d93c9 Thanks @​CarmenPopoviciu! - Remove NodeJSCompatModule. This was never fully supported, and never worked for deploying Workers from Wrangler.

• Updated dependencies [90d93c9]:

  • miniflare@​3.20250310.2

v3.114.3

Compare Source

Patch Changes

• #​8662 5e57717 Thanks @​workers-devprod! - Amend pages dev error message when an environment is requested

• #​8535 6f8e892 Thanks @​workers-devprod! - improve the error messaging when the user provides neither an entry point nor an asset directory

v3.114.2

Compare Source

Patch Changes

• #​8453 f90a669 Thanks @​workers-devprod! - trigger dummy v3 maintenance release for testing

• #​8500 80bbee3 Thanks @​workers-devprod! - Support no_bundle config in Pages for both dev and deploy.

  This was already supported via a command line arg (--no-bundle).

• #​8521 5cd32b1 Thanks @​emily-shen! - fix: throw explicit error for unknown mimetype during wrangler check startup

• #​8504 0192aae Thanks @​workers-devprod! - Fix Workers Assets metafiles (_headers and _redirects) resolution when running Wrangler from a different directory

• Updated dependencies [f90a669]:

  • miniflare@​3.20250310.1

v3.114.1

Compare Source

Patch Changes

• #​8383 8d6d722 Thanks @​matthewdavidrodgers! - Make kv bulk put --local respect base64:true

  The bulk put api has an optional "base64" boolean property for each key.
  Before storing the key, the value should be decoded from base64.

  For real (remote) kv, this is handled by the rest api. For local kv, it
  seems the base64 field was ignored, meaning encoded base64 content was
  stored locally rather than the raw values.

  To fix, we need to decode each value before putting to the local
  miniflare namespace when base64 is true.

• #​8273 e3efd68 Thanks @​penalosa! - Support AI, Vectorize, and Images bindings when using @cloudflare/vite-plugin

• #​8427 a352798 Thanks @​vicb! - update unenv-preset dependency to fix bug with Performance global

  Fixes #​8407
  Fixes #​8409
  Fixes #​8411

• #​8390 53e6323 Thanks @​GregBrimble! - Parse and apply metafiles (_headers and _redirects) in wrangler dev for Workers Assets

• #​8392 4d9d9e6 Thanks @​jahands! - fix: retry zone and route lookup API calls

  In rare cases, looking up Zone or Route API calls may fail due to transient errors. This change improves the reliability of wrangler deploy when these errors occur.

  Also fixes a rare issue where concurrent API requests may fail without correctly throwing an error which may cause a deployment to incorrectly appear successful.

• Updated dependencies [8242e07, 53e6323]:

  • miniflare@​3.20250310.0

v3.114.0

Compare Source

Minor Changes

• #​8367 7b6b0c2 Thanks @​jonesphillip! - Deprecated --id parameter in favor of --name for both the wrangler r2 bucket lifecycle and wrangler r2 bucket lock commands

v3.113.0

Compare Source

Minor Changes

• #​8300 bca1fb5 Thanks @​vicb! - Use the unenv preset for Cloudflare from @cloudflare/unenv-preset

Patch Changes

• #​8338 2d40989 Thanks @​GregBrimble! - feat: Upload _headers and _redirects if present with Workers Assets as part of wrangler deploy and wrangler versions upload.

• #​8288 cf14e17 Thanks @​CarmenPopoviciu! - feat: Add assets Proxy Worker skeleton in miniflare

  This commit implements a very basic Proxy Worker skeleton, and wires it in the "pipeline" miniflare creates for assets. This Worker will be incrementally worked on, but for now, the current implementation will forward all incoming requests to the Router Worker, thus leaving the current assets behaviour in local dev, the same.

  This is an experimental feature available under the --x-assets-rpc flag: wrangler dev --x-assets-rpc.

• #​8216 af9a57a Thanks @​ns476! - Support Images binding in wrangler types

• #​8304 fbba583 Thanks @​jahands! - chore: add concurrency and caching for Zone IDs and Workers routes lookups

  Workers with many routes can result in duplicate Zone lookups during deployments, making deployments unnecessarily slow. This compounded by the lack of concurrency when making these API requests.

  This change deduplicates these requests and adds concurrency to help speed up deployments.

• Updated dependencies [2d40989, da568e5, cf14e17, 79c7810]:

  • miniflare@​3.20250224.0

v3.112.0

Compare Source

Minor Changes

• #​8256 f59d95b Thanks @​jbwcloudflare! - Add two new Queues commands: pause-delivery and resume-delivery

  These new commands allow users to pause and resume the delivery of messages to Queue Consumers

Patch Changes

• #​8274 fce642d Thanks @​emily-shen! - fix bindings to entrypoints on the same worker in workers with assets

• #​8201 2cad136 Thanks @​ichernetsky-cf! - fix: interactively list Cloudchamber deployments using labels

• #​8289 a4909cb Thanks @​penalosa! - Add the experimental --x-assets-rpc flag to gate feature work to support JSRPC with Workers + Assets projects.

• Updated dependencies [fce642d, a4909cb]:

  • miniflare@​3.20250214.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/wrangler-3.x-lockfile

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.