chore(deps): update dependency wrangler to v4.114.0 - autoclosed#49
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
compatibility-fyi | d9ef00a | Commit Preview URL Branch Preview URL |
Jul 24 2026, 06:21 AM |
renovate
Bot
force-pushed
the
renovate/wrangler-4.x-lockfile
branch
from
July 24, 2026 06:19
ec2d4ba to
d9ef00a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.113.0→4.114.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.114.0Compare Source
Minor Changes
#14633
3203b5dThanks @nickpatt! - Add local-dev observabilitywrangler devand the Vite plugin now capture a trace for every local Worker invocation - spans, logs, andconsole.*output, including requests that cross worker or Durable Object boundaries.You can explore this data two ways:
/cdn-cgi/explorer/api/local/observability/query, discoverable via the Local Explorer's OpenAPI document, so coding agents and tools can query the samespansandlogstables.While this is in testing it's off by default; set
X_LOCAL_OBSERVABILITY=trueto turn it on. It will be on by default in the public release.Patch Changes
#14373
246ce92Thanks @Jacroney! - Improve the D1 database-limit error messageWhen 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 createand to the D1 database that is created during resource provisioning on deploy.#14796
c38a2c3Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#14788
8416b33Thanks @chinesepowered! - Fix grammar in the container image-too-large errorThe 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
4683ff8Thanks @jamesopstad! - Ignore the removedlegacy_envfield when reading a redirected configurationOlder versions of tools such as the Vite plugin can generate a redirected configuration (
.wrangler/deploy/config.json) that still includes the removedlegacy_envfield. Since these files are tool-generated, users could not easily remove the field themselves, and Wrangler would error out. Wrangler now silently stripslegacy_envfrom redirected configurations. User-authored configurations still report an error so that the field can be removed.#14593
02232f3Thanks @spk-ai! - Fix dev proxy silently hanging or returning a misleading 503 on network errors for non-root-path requestsDuring
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/HEADrequests would silently hang (with nothing logged) until the client timed out, and other methods would receive a misleadingYour worker restarted mid-request503. Such errors are now reported and surfaced immediately when the worker has not actually changed.#14797
f8a8c2cThanks @roerohan! - Explain how to provision Flagship bindings ifapp_idmissing in remote developmentWrangler now reports that a Flagship binding without an
app_idmust first be created withwrangler flagship apps create.Updated dependencies [
c38a2c3,c079ba3,95b026e,c4bacec,3203b5d]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.