build(deps-dev): bump wrangler from 4.38.0 to 4.45.4

[dependabot]

Bumps wrangler from 4.38.0 to 4.45.4.

Release notes

Sourced from wrangler's releases.

wrangler@4.45.4

Patch Changes

• #11133 8ffbd17 Thanks @​petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.

  Now the argument values that are captured come from an allow list, and can be marked as ALLOW (capture the real value) or REDACT (capture as "").

• #11033 77ed7e2 Thanks @​dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when running wrangler deploy

  When running wrangler deploy, with --x-remote-diff-check, Wrangler will display the difference between local and remote configuration. If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment. In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.

• #11139 bb00f9d Thanks @​devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally

• #11135 ed666a1 Thanks @​penalosa! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.

• #11149 22f25fd Thanks @​penalosa! - Add no-op autoconfig logic behind an experimental flag

• Updated dependencies [90a2566, 14f60e8]:

  • @​cloudflare/unenv-preset@​2.7.9
  • miniflare@4.20251011.2

wrangler@4.45.3

Patch Changes

• #11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

  D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

• #11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

  The object that holds the environment variables in process.env does not care about the case of its keys in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

  Previously, when merging fields from .env files we were replacing this native object with a vanilla JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing when in reality they just had different casing.

wrangler@4.45.1

Patch Changes

• #10959 d0208fe Thanks @​devin-ai-integration! - Fixed conflict between --env and --expires flags in wrangler r2 object put.

  --e now aliases --env only, and NOT --expires.

• #10915 dbe51c1 Thanks @​devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.

• #10913 d4f2daf Thanks @​devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.45.4

Patch Changes

• #11133 8ffbd17 Thanks @​petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.

  Now the argument values that are captured come from an allow list, and can be marked as ALLOW (capture the real value) or REDACT (capture as "").

• #11033 77ed7e2 Thanks @​dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when running wrangler deploy

  When running wrangler deploy, with --x-remote-diff-check, Wrangler will display the difference between local and remote configuration. If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment. In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.

• #11139 bb00f9d Thanks @​devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally

• #11135 ed666a1 Thanks @​penalosa! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.

• #11149 22f25fd Thanks @​penalosa! - Add no-op autoconfig logic behind an experimental flag

• Updated dependencies [90a2566, 14f60e8]:

  • @​cloudflare/unenv-preset@​2.7.9
  • miniflare@4.20251011.2

4.45.3

Patch Changes

• #11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

  D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

• #11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

  The object that holds the environment variables in process.env does not care about the case of its keys in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

  Previously, when merging fields from .env files we were replacing this native object with a vanilla JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing when in reality they just had different casing.

4.45.2

Patch Changes

• #11097 55657eb Thanks @​penalosa! - Extract internal APIs into a new @cloudflare/workers-utils package

• #11118 d47f166 Thanks @​zebp! - Fix validation of the persist field of observability logs and traces configuration

... (truncated)

Commits

• a586c03 Version Packages (#11141)
• 90a2566 Bump unenv to 2.0.0-rc.24 (#11080)
• 22f25fd Initial autoconfig scaffolding (#11149)
• 77ed7e2 Potentially update local config on wrangler deploy --x-remote-diff-check in...
• bb00f9d Fix cron trigger documentation links and inline testing instructions (#11139)
• 8ffbd17 Reduce the amount of arguments being passed in metrics capture. (#11133)
• ed666a1 Implement tail-based logging for realish preview (#11135)
• 8445f29 Version Packages (#11131)
• 6822aaf print d1 resource locations take 2 (#11117)
• bce8142 Ensure that process.env is case-insensitive on Windows (#11077)
• 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)

[cloudflare-workers-and-pages]

Deploying cloudflare-functions-demo with    Cloudflare Pages

Latest commit:	2734f33
Status:	🚫  Build failed.

View logs

[dependabot]

Superseded by #547.