chore(deps-dev): bump wrangler from 3.102.0 to 3.103.1

[dependabot]

Bumps wrangler from 3.102.0 to 3.103.1.

Release notes

Sourced from wrangler's releases.

wrangler@3.103.1

Patch Changes

• #7798 a1ff045 Thanks @​CarmenPopoviciu! - Reverts #7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)

wrangler@3.103.0

Minor Changes

• #5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

  add a new --strict-vars option to wrangler types that developers can (by setting the flag to false) use to disable the default strict/literal types generation for their variables

  opting out of strict variables can be useful when developers change often their vars values, even more so when multiple environments are involved

  Example

  With a toml containing:

  [vars]
  MY_VARIABLE = "production_value"
  MY_NUMBERS = [1, 2, 3]
  [env.staging.vars]
  MY_VARIABLE = "staging_value"
  MY_NUMBERS = [7, 8, 9]

  the wrangler types command would generate the following interface:

  interface Env {
          MY_VARIABLE: "production_value" | "staging_value";
          MY_NUMBERS: [1,2,3] | [7,8,9];
  }
  

  while wrangler types --strict-vars=false would instead generate:

  interface Env {
          MY_VARIABLE: string;
          MY_NUMBERS: number[];
  }
  

  (allowing the developer to easily change their toml variables without the risk of breaking typescript types)

Patch Changes

• #7720 902e3af Thanks @​vicb! - chore(wrangler): use the unenv preset from @cloudflare/unenv-preset

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.103.1

Patch Changes

• #7798 a1ff045 Thanks @​CarmenPopoviciu! - Reverts #7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)

3.103.0

Minor Changes

• #5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

  add a new --strict-vars option to wrangler types that developers can (by setting the flag to false) use to disable the default strict/literal types generation for their variables

  opting out of strict variables can be useful when developers change often their vars values, even more so when multiple environments are involved

  Example

  With a toml containing:

  [vars]
  MY_VARIABLE = "production_value"
  MY_NUMBERS = [1, 2, 3]
  [env.staging.vars]
  MY_VARIABLE = "staging_value"
  MY_NUMBERS = [7, 8, 9]

  the wrangler types command would generate the following interface:

  interface Env {
          MY_VARIABLE: "production_value" | "staging_value";
          MY_NUMBERS: [1,2,3] | [7,8,9];
  }
  

  while wrangler types --strict-vars=false would instead generate:

  interface Env {
          MY_VARIABLE: string;
          MY_NUMBERS: number[];
  }
  

... (truncated)

Commits

• 9b519cc Version Packages (#7792)
• 7c1c90e Revert "chore(wrangler): use the unenv preset from @cloudflare/unenv-preset...
• cc4af98 Version Packages (#7766)
• 902e3af chore(wrangler): use the unenv preset from @cloudflare/unenv-preset (#7720)
• 8faf2c0 widen multi-env vars types in wrangler types and add --strict-vars opti...
• e8aaa39 Unwrap SDW errors before sending to Sentry (#7735)
• dceb196 feat: pull resource names for provisioning from config if provided (#7733)
• 19228e5 chore: update unenv depency version (#7760)
• See full diff 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)