chore(deps-dev): Bump wrangler from 3.114.1 to 4.9.0

[dependabot]

Bumps wrangler from 3.114.1 to 4.9.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.9.0

Minor Changes

• #8375 930ebb2 Thanks @​penalosa! - Add support for email local dev and send_email binding

Patch Changes

• #8809 09464a6 Thanks @​dario-piotrowicz! - improve error message when redirected config contains environments

  this change improves that validation error message that users see when a redirected config file contains environments, by:

  • cleaning the message formatting and displaying the offending environments in a list
  • prompting the user to report the issue to the author of the tool which has generated the config

• #8829 62df08a Thanks @​cmackenzie1! - Add option --cors-origin none to remove CORS settings on a pipeline

• Updated dependencies [afd93b9, 930ebb2]:

  • miniflare@4.20250405.1

wrangler@4.8.0

Minor Changes

• #8394 93267cf Thanks @​edmundhung! - Support Secrets Store Secret bindings

Patch Changes

• #8780 4e69fb6 Thanks @​cmackenzie1! - - Rename wrangler pipelines show to wrangler pipelines get

  • Replace --enable-worker-binding and --enable-http with --source worker and --source http (or --source http worker for both)
  • Remove --file-template and --partition-template flags from wrangler pipelines create|update
  • Add pretty output for wrangler pipelines get <pipeline>. Existing output is available using --format=json.
  • Clarify the minimums, maximums, and defaults (if unset) for wrangler pipelines create commands.

• #8596 75b454c Thanks @​dario-piotrowicz! - add validation to redirected configs in regards to environments

  add the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

  • redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
  • given the point above, specifying an environment (--env=my-env) when using redirected configs is incorrect, so these environments should be ignored and a warning should be presented to the user

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.9.0

Minor Changes

• #8375 930ebb2 Thanks @​penalosa! - Add support for email local dev and send_email binding

Patch Changes

• #8809 09464a6 Thanks @​dario-piotrowicz! - improve error message when redirected config contains environments

  this change improves that validation error message that users see when a redirected config file contains environments, by:

  • cleaning the message formatting and displaying the offending environments in a list
  • prompting the user to report the issue to the author of the tool which has generated the config

• #8829 62df08a Thanks @​cmackenzie1! - Add option --cors-origin none to remove CORS settings on a pipeline

• Updated dependencies [afd93b9, 930ebb2]:

  • miniflare@4.20250405.1

4.8.0

Minor Changes

• #8394 93267cf Thanks @​edmundhung! - Support Secrets Store Secret bindings

Patch Changes

• #8780 4e69fb6 Thanks @​cmackenzie1! - - Rename wrangler pipelines show to wrangler pipelines get

  • Replace --enable-worker-binding and --enable-http with --source worker and --source http (or --source http worker for both)
  • Remove --file-template and --partition-template flags from wrangler pipelines create|update
  • Add pretty output for wrangler pipelines get <pipeline>. Existing output is available using --format=json.
  • Clarify the minimums, maximums, and defaults (if unset) for wrangler pipelines create commands.

• #8596 75b454c Thanks @​dario-piotrowicz! - add validation to redirected configs in regards to environments

  add the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

  • redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
  • given the point above, specifying an environment (--env=my-env) when using redirected configs is incorrect, so these environments should be ignored and a warning should be

... (truncated)

Commits

• 562ce1d Version Packages (#8833)
• 62df08a Add options to update pipelines to remove CORS (#8829)
• 09464a6 Improve error message displayed when a redirected config includes multiple en...
• 930ebb2 Email Workers local dev and send_email binding (#8375)
• f6b84b7 Version Packages (#8796)
• ec7e621 feat: add waitForEvent and sendEvent support for local dev (#8775)
• 93267cf Secrets Store Secret binding local dev (#8394)
• 75b454c [wrangler] add validation to redirected configs in regards to environments (#...
• 4e69fb6 Pipelines CLI Improvements (#8780)
• d4c1171 Unhide 'wrangler pages functions build' (#8795)
• 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 #387.