Repository navigation
chore(deps): update dependency wrangler to v4.154.0 - #69
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
userscripts | 15020f2 | Commit Preview URL Branch Preview URL |
Oct 29 2026, 05:11 AM |
gameroman
approved these changes
Oct 29, 2026
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.153.0→4.154.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.154.0Compare Source
Minor Changes
#16494
0968b08Thanks @petebacondarwin! - Enable Miniflare's development registry by default and centralize path resolutionIn Miniflare v5 beta, resolve the registry from
CLOUDFLARE_DEV_REGISTRY_PATH, then theunsafeDevRegistryPathconstructor option, then<Cloudflare config directory>/dev-registry/v5. The default is independent of legacy Wrangler directories and is scoped to the Miniflare major version. The Vite v2 beta plugin follows this new default, while current Wrangler andgetPlatformProxy()retain Wrangler's legacy default for compatibility with existing Wrangler sessions. Vite v2 and Wrangler therefore require the sameCLOUDFLARE_DEV_REGISTRY_PATHto discover each other; set it for both processes when mixing these tools.Add
enableDevRegistry: falseto disable registration and discovery explicitly. Shared storage now uses the resolved default without requiring an explicit path. As before, shared storage requires an enabled registry to elect a storage owner, so combiningunsafeEnableSharedStorage: truewithenableDevRegistry: falseis rejected. Miniflare no longer readsMINIFLARE_REGISTRY_PATH; useCLOUDFLARE_DEV_REGISTRY_PATHinstead. ExposeresolveDevRegistryPath()for integrations that also read registry files. Wrangler uses the effective path for its runtime configuration, initial bindings display, and Flagship active-session check, so the canonical override cannot bypass that check. An explicitly disabled Wrangler registry remains disabled.Patch Changes
#16499
f3c13b3Thanks @dinasaur404! - Preserve binding error codes and names in local developmentErrors from remote bindings and from Node.js binding proxies (
getPlatformProxy()andMiniflare#getBindings()) now keep their machine-readable properties, such as Artifacts'codeandnumericCode. Previously these properties were dropped and the error name was folded into the message (for example"ArtifactsError: Repository not found"), so code could only branch on error text during local development.Node.js callers also keep custom error names such as
ArtifactsError. Errors from remote bindings received inside a Worker keep their properties but are still namedError.Updated dependencies [
0968b08,f3c13b3]: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.