Sourced from wrangler's releases.

[email protected]

Patch Changes

• #10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

  Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

  In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

• #10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

• #10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

• #9897 755a249 Thanks @​edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

  • [email protected]
  • @​cloudflare/unenv-preset@​2.5.0

[email protected]

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

... (truncated)

Sourced from wrangler's changelog.

4.26.1

Patch Changes

• #10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

  Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

  In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

• #10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

• #10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

• #9897 755a249 Thanks @​edmundhung! - fix: wrangler types should infer the types of the default worker entrypoint

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, dbdbb8c, 5991a9c, 687655f]:

  • [email protected]
  • @​cloudflare/unenv-preset@​2.5.0

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.

... (truncated)

• c070c77 Version Packages (#10059)
• 75640c1 recommend DOCKER_HOST instead (#10097)
• 687655f bump unenv to 2.0.0-rc.19 (#10096)
• 755a249 fix(wrangler): default worker entrypoint suport with wrangler types (#9897)
• 0595018 import debug instead of the alias (#10093)
• 5991a9c [preset] add support for the native http modules (#10078)
• 2df1d06 Bump the workerd-and-workers-types group with 2 updates (#9968)
• dbdbb8c pass the compatibility date and flags to the unenv preset (#10048)
• f8a80a8 Automatically get docker socket path (and fix socket path config in vite plug...
• f8f7352 fix(miniflare): service binding fetch over dev registry should work without h...
• Additional commits viewable in compare view

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)