Bump wrangler from 3.99.0 to 3.101.0

[dependabot]

Bumps wrangler from 3.99.0 to 3.101.0.

Release notes

Sourced from wrangler's releases.

wrangler@3.101.0

Minor Changes

• #7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

• #7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

  Run wrangler secret bulk .dev.vars to add the env file

  //.dev.vars
  KEY=VALUE
  KEY_2=VALUE

  This will upload the secrets KEY and KEY_2 to your worker

• #7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

  This new feature is designed for build tools and frameworks to provide a deploy-specific configuration, which Wrangler can use instead of user configuration when running deploy-related commands. It is not expected that developers of Workers will need to use this feature directly.

  Affected commands

  The commands that use this feature are:

  • wrangler deploy
  • wrangler dev
  • wrangler versions upload
  • wrangler versions deploy
  • wrangler pages deploy
  • wrangler pages build
  • wrangler pages build-env

  Config redirect file

  When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

  { "configPath": "../../path/to/wrangler.json" }

  When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

  When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

  Custom build tool example

  A common approach that a build tool might choose to implement.

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.101.0

Minor Changes

• #7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

• #7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

  Run wrangler secret bulk .dev.vars to add the env file

  //.dev.vars
  KEY=VALUE
  KEY_2=VALUE

  This will upload the secrets KEY and KEY_2 to your worker

• #7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

  This new feature is designed for build tools and frameworks to provide a deploy-specific configuration, which Wrangler can use instead of user configuration when running deploy-related commands. It is not expected that developers of Workers will need to use this feature directly.

  Affected commands

  The commands that use this feature are:

  • wrangler deploy
  • wrangler dev
  • wrangler versions upload
  • wrangler versions deploy
  • wrangler pages deploy
  • wrangler pages build
  • wrangler pages build-env

  Config redirect file

  When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

  { "configPath": "../../path/to/wrangler.json" }

  When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

  When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

  Custom build tool example

... (truncated)

Commits

• 45f45c3 Version Packages (#7692)
• 6439347 Remove CF-Connecting-IP for requests to the edge preview (#7712)
• 45d1d1e add dotenv support to wrangler secret bulk (#7674)
• 7c8ae1c feat: Use OAuth flow to generate R2 tokens for Pipelines (#7534)
• f3c2f69 Default D1 export to --local (#7694)
• 773bda8 Remove defaults for batch-max-* pipeline parameters and define value ranges...
• e771fe9 include the top level Worker name in the parsed config structure (#7703)
• ff4e77e Remove --experimental-versions (and related flags) as it is now GA (#7456)
• e4716cc feat: add support for redirecting Wrangler to a generated config when running...
• 9d2740a test(wrangler): allow overriding the unenv preset (#7685)
• 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)

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	100%	47 / 47
🔵	Statements	100%	47 / 47
🔵	Functions	100%	5 / 5
🔵	Branches	100%	32 / 32

File Coverage

No changed files found.

Generated in workflow #11 for commit 5e51788 by the Vitest Coverage Report Action