Bump wrangler from 4.19.1 to 4.26.0

[dependabot]

Bumps wrangler from 4.19.1 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #146.