chore(deps-dev): bump wrangler from 4.35.0 to 4.44.0

[dependabot]

Bumps wrangler from 4.35.0 to 4.44.0.

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #10939 d4b4c90 Thanks @​danielrs! - Config preview_urls defaults to workers_dev value.

  Originally, we were defaulting config.preview_urls to true, but we were accidentally enabling Preview URLs for users that only had config.workers_dev=false.

  Then, we set the default value of config.preview_urls to false, but we were accidentally disabling Preview URLs for users that only had config.workers_dev=true.

  Rather than defaulting config.preview_urls to true or false, we default to the resolved value of config.workers_dev. Should result in a clearer user experience.

• #11027 1a2bbf8 Thanks @​jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

• #9705 0ee1a68 Thanks @​hiendv! - Add params type to Workflow type generation. E.g.

  interface Env {
  	MY_WORKFLOW: Workflow<
  		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
  	>;
  }

• #10867 dd5f769 Thanks @​austin-mc! - Add media binding support

Patch Changes

• #11018 5124818 Thanks @​dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information

• #11019 6643bd4 Thanks @​dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

• #10768 8211bc9 Thanks @​dario-piotrowicz! - Update logs handling to use the new handleStructuredLogs miniflare option

• #10997 3bb034f Thanks @​nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are set in the environment, then command failures will append a line to the output file encoding the error code and message, if present.

• #10986 43503c7 Thanks @​emily-shen! - fix: cleanup any running containers again on wrangler dev exit

• #11000 a6de9db Thanks @​jonboulle! - always load container image into local store during build

  BuildKit supports different build drivers. When using the more modern docker-container driver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when calling getImageRepoTags), it will thus fail, e.g.:

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.44.0

Minor Changes

• #10939 d4b4c90 Thanks @​danielrs! - Config preview_urls defaults to workers_dev value.

  Originally, we were defaulting config.preview_urls to true, but we were accidentally enabling Preview URLs for users that only had config.workers_dev=false.

  Then, we set the default value of config.preview_urls to false, but we were accidentally disabling Preview URLs for users that only had config.workers_dev=true.

  Rather than defaulting config.preview_urls to true or false, we default to the resolved value of config.workers_dev. Should result in a clearer user experience.

• #11027 1a2bbf8 Thanks @​jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

• #9705 0ee1a68 Thanks @​hiendv! - Add params type to Workflow type generation. E.g.

  interface Env {
  	MY_WORKFLOW: Workflow<
  		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
  	>;
  }

• #10867 dd5f769 Thanks @​austin-mc! - Add media binding support

Patch Changes

• #11018 5124818 Thanks @​dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information

• #11019 6643bd4 Thanks @​dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

• #10768 8211bc9 Thanks @​dario-piotrowicz! - Update logs handling to use the new handleStructuredLogs miniflare option

• #10997 3bb034f Thanks @​nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are set in the environment, then command failures will append a line to the output file encoding the error code and message, if present.

• #10986 43503c7 Thanks @​emily-shen! - fix: cleanup any running containers again on wrangler dev exit

• #11000 a6de9db Thanks @​jonboulle! - always load container image into local store during build

  BuildKit supports different build drivers. When using the more modern docker-container driver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when calling getImageRepoTags), it will thus fail, e.g.:

... (truncated)

Commits

• 0bfbfa0 Version Packages (#10980)
• 1a2bbf8 Set default values when statically replacing process.env.NODE_ENV (#11027)
• daa3529 Change AI model in tests (#11035)
• cf16deb CC-6280: Correctly handle image names that contain a slash (#11007)
• 6643bd4 Fix observability.logs.persist being flagged as an unexpected field during ...
• d39c8b5 Make Workflows instance list command cursor based (#10994)
• 5124818 Improve potential errors thrown by startRemoteProxySession by including mor...
• ee640d4 further attempts to reducde configcontroller test flakes (#11001)
• 06918b9 if the CLOUDFLARE_ACCOUNT_ID was an empty string it caused e2e tests to fail ...
• 3bb034f write to output file on command failure (#10997)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for wrangler since your current version.

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 #28.