chore: bump wrangler from 4.15.2 to 4.16.1

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps wrangler from 4.15.2 to 4.16.1.

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

• #9268 7344344 Thanks @​gabivlj! - wrangler containers delete handles API errors correctly

[email protected]

Minor Changes

• #9288 3b8f7f1 Thanks @​petebacondarwin! - allow --name and --env args on wrangler deploy

  Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment. Now specifying --name is supported and will override any names set in the Wrangler config:

  wrangler.json

  {
  	"name": "config-worker"
  	"env": {
  		"staging": { "name": "config-worker-env" }
  	}
  }

  Command	Previous (Worker name)	Proposed (Worker name)	Comment
  wrangler deploy --name=args-worker	"args-worker"	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=staging	Error	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=prod	Error	"args-worker"	CLI arg used
  wrangler deploy	"config-worker"	"config-worker"	Top-level config used
  wrangler deploy --env=staging	"config-worker-env"	"config-worker-env"	Named env config used
  wrangler deploy --env=prod	"config-worker-prod"	"config-worker-prod"	CLI arg and top-level config combined

• #9265 16de0d5 Thanks @​edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

• #9234 2fe6219 Thanks @​emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #9269 66d975e Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #9151 5ab035d Thanks @​gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

• #9231 02d40ed Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.16.1

Patch Changes

• #9268 7344344 Thanks @​gabivlj! - wrangler containers delete handles API errors correctly

4.16.0

Minor Changes

• #9288 3b8f7f1 Thanks @​petebacondarwin! - allow --name and --env args on wrangler deploy

  Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment. Now specifying --name is supported and will override any names set in the Wrangler config:

  wrangler.json

  {
  	"name": "config-worker"
  	"env": {
  		"staging": { "name": "config-worker-env" }
  	}
  }

  Command	Previous (Worker name)	Proposed (Worker name)	Comment
  wrangler deploy --name=args-worker	"args-worker"	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=staging	Error	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=prod	Error	"args-worker"	CLI arg used
  wrangler deploy	"config-worker"	"config-worker"	Top-level config used
  wrangler deploy --env=staging	"config-worker-env"	"config-worker-env"	Named env config used
  wrangler deploy --env=prod	"config-worker-prod"	"config-worker-prod"	CLI arg and top-level config combined

• #9265 16de0d5 Thanks @​edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

• #9234 2fe6219 Thanks @​emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #9269 66d975e Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #9151 5ab035d Thanks @​gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

• #9231 02d40ed Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

... (truncated)

Commits

• 9cee4b0 Version Packages (#9315)
• 7344344 wrangler containers: Delete should have better error handling (#9268)
• 9707408 Version Packages (#9278)
• 5ab035d containers: allow users to specify the kind of container rollout they want (#...
• e34d198 test: simplify docs test (#9303)
• db5ea8f Support Mixed Mode for more binding types (#9277)
• 66d975e Wire up mixed-mode remote bindings for multi-worker wrangler dev (#9269)
• 2ef31a9 bump @cloudflare/unenv-preset (#9221)
• 3b8f7f1 allow --name and --env args on wrangler deploy (#9288)
• f2a16f1 fix: setting triggers.crons:[] in Wrangler config should delete deployed cron...
• 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)