build(deps-dev): bump wrangler from 4.25.0 to 4.26.0 in the patch-versions group

[dependabot]

Bumps the patch-versions group with 1 update: wrangler.

Updates wrangler from 4.25.0 to 4.26.0

Release notes

Sourced from wrangler's releases.

wrangler@4.26.0

Minor Changes

• #10016 c5b291d Thanks @​emily-shen! - Interactively handle wrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.

  For example:

  npx wrangler deploy ./public will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

  npx wrangler deploy --assets=./public will now ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

  In non-interactive contexts, Wrangler will error as it currently does.

• #9971 19794bf Thanks @​edmundhung! - Improved script source display on the pretty error screen

Patch Changes

• #9800 3d4f946 Thanks @​helloimalastair! - remove banner from r2 getobject in pipe mode

• #9910 7245101 Thanks @​dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is ready

  fix the fact that when starting a local (or remote) dev session the log saying Ready on http://localhost:xxxx could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)

• #10031 823cba8 Thanks @​vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

• #10032 154acf7 Thanks @​dario-piotrowicz! - add support for containers in wrangler multiworker dev

  currently when running wrangler dev with different workers (meaning that the -c|--config flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.

• #9988 7fb0bfd Thanks @​penalosa! - Correctly label mtls remote bindings warning

• Updated dependencies [823cba8, 19794bf, 059a39e]:

  • @​cloudflare/unenv-preset@​2.4.1
  • miniflare@4.20250712.2

wrangler@4.25.1

Patch Changes

• #10000 c02b067 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.

• #9996 b0217f9 Thanks @​nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry

• #10009 e87198a Thanks @​gpanders! - Fix containers diff output when using JSONC config files

• #9976 ad02ad3 Thanks @​dario-piotrowicz! - add warning for when users run wrangler dev --remote with (enabled) containers

• #9819 0c4008c Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite dev

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.26.0

Minor Changes

• #10016 c5b291d Thanks @​emily-shen! - Interactively handle wrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.

  For example:

  npx wrangler deploy ./public will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

  npx wrangler deploy --assets=./public will now ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

  In non-interactive contexts, Wrangler will error as it currently does.

• #9971 19794bf Thanks @​edmundhung! - Improved script source display on the pretty error screen

Patch Changes

• #9800 3d4f946 Thanks @​helloimalastair! - remove banner from r2 getobject in pipe mode

• #9910 7245101 Thanks @​dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is ready

  fix the fact that when starting a local (or remote) dev session the log saying Ready on http://localhost:xxxx could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)

• #10031 823cba8 Thanks @​vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

• #10032 154acf7 Thanks @​dario-piotrowicz! - add support for containers in wrangler multiworker dev

  currently when running wrangler dev with different workers (meaning that the -c|--config flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.

• #9988 7fb0bfd Thanks @​penalosa! - Correctly label mtls remote bindings warning

• Updated dependencies [823cba8, 19794bf, 059a39e]:

  • @​cloudflare/unenv-preset@​2.4.1
  • miniflare@4.20250712.2

4.25.1

Patch Changes

• #10000 c02b067 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.

• #9996 b0217f9 Thanks @​nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry

• #10009 e87198a Thanks @​gpanders! - Fix containers diff output when using JSONC config files

• #9976 ad02ad3 Thanks @​dario-piotrowicz! - add warning for when users run wrangler dev --remote with (enabled) containers

... (truncated)

Commits

• e424eb4 Version Packages (#10042)
• 1e92dd8 refactor containers config handling (#9961)
• 7245101 [wrangler] make sure that the ready-on message is printed after the appropria...
• 3d4f946 R2-3182: Remove wrangler Banner from R2 GetObject in Pipe Mode (#9800)
• c5b291d feat: interactively handle wonky asset deploy commands (#10016)
• 823cba8 Move the unenv tests from the preset to wrangler e2e (#10031)
• 7fb0bfd Fix mtls remtote binding warning (#9988)
• 19794bf feat(wrangler): improve script source display on pretty error screen (#9971)
• 154acf7 add support for containers in wrangler multiworker dev (#10032)
• 715ca2a add a util to format compatibility dates (#10043)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by CodeRabbit

• Chores
  • Updated the "wrangler" development tool to the latest version for improved stability and features.

[coderabbitai]

Walkthrough

The version of the "wrangler" package in the devDependencies section of the package.json file was updated from "^4.25.0" to "^4.26.0". No other changes were made to dependencies, scripts, or configuration.

Changes

Cohort / File(s)	Change Summary
DevDependency Version Bump package.json	Updated "wrangler" devDependency from "^4.25.0" to "^4.26.0".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• build(deps-dev): bump wrangler from 4.24.3 to 4.25.0 in the patch-versions group #284: Also updated the "wrangler" devDependency, advancing from 4.24.3 to 4.25.0.

Suggested reviewers

• sudo-shashank
• hanabi1224

Poem

A wrangler hops from old to new,
Just a version—nothing else to do!
The package.json’s neat and spry,
With numbers higher, spirits fly.
🐇✨
Now build and run, with glee and cheer,
For wrangler’s latest is finally here!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b69121d and 9c79f99.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

8-11: Double-check lock-file sync & CI against Wrangler 4.26.0

The bump is benign on paper (4.25 → 4.26) but remember to:

1. Commit the regenerated yarn.lock so CI and local dev resolve to 4.26.0 consistently.
2. Run wrangler build / wrangler dev locally (all envs: quick, default) to surface any API or CLI flag changes introduced in 4.26.0.
3. Skim the 4.26 release notes – a few minor behaviour tweaks (asset-only deploy flow, dev log timing) could affect scripted workflows.

If CI already passes and the lock-file diff accompanies the PR, you can disregard this note.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/npm_and_yarn/patch-versions-70a420f3ac

---

🪧 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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• 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.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 36.94%. Comparing base (b69121d) to head (9c79f99).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #290   +/-   ##
=======================================
  Coverage   36.94%   36.94%           
=======================================
  Files          40       40           
  Lines        2902     2902           
=======================================
  Hits         1072     1072           
  Misses       1830     1830           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.