build(deps-dev): bump wrangler from 4.45.0 to 4.46.0 in the patch-versions group

[dependabot]

Bumps the patch-versions group with 1 update: wrangler.

Updates wrangler from 4.45.0 to 4.46.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #11183 240ebeb Thanks @​dario-piotrowicz! - expose experimental_getDetailsForAutoConfig and experimental_runAutoConfig APIs that provide respectively the autoconfig detection and execution functionalities

• #11180 53b0fce Thanks @​penalosa! - Detect non-framework static sites

• #11162 c3ed531 Thanks @​dario-piotrowicz! - add a remoteBindings option to getPlatformProxy to allow the disabling of remote bindings

• #11164 305d7bf Thanks @​penalosa! - Implement experimental autoconfig flow for static sites

• #10605 b55a3c7 Thanks @​emily-shen! - Add command to configure credentials for non-Cloudflare container registries

  Note this is a closed/experimental command that will not work without the appropriate account-level capabilities.

• #11078 5d7c4c2 Thanks @​simonha9! - Add jurisdiction support to d1 db creation via command-line argument

Patch Changes

• #11160 05440a1 Thanks @​dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when running wrangler deploy --env <TARGET_ENV>

  When running wrangler deploy, with --x-remote-diff-check and after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the --env|-e flag). Now this will also apply when an environment is targeted.

• #11162 c3ed531 Thanks @​dario-piotrowicz! - Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it

• #11162 c3ed531 Thanks @​dario-piotrowicz! - Fix bindings with remote: true being logged as remote when run via wrangler dev --local

• Updated dependencies [1ae020d]:

  • [email protected]

[email protected]

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

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.46.0

Minor Changes

• #11183 240ebeb Thanks @​dario-piotrowicz! - expose experimental_getDetailsForAutoConfig and experimental_runAutoConfig APIs that provide respectively the autoconfig detection and execution functionalities

• #11180 53b0fce Thanks @​penalosa! - Detect non-framework static sites

• #11162 c3ed531 Thanks @​dario-piotrowicz! - add a remoteBindings option to getPlatformProxy to allow the disabling of remote bindings

• #11164 305d7bf Thanks @​penalosa! - Implement experimental autoconfig flow for static sites

• #10605 b55a3c7 Thanks @​emily-shen! - Add command to configure credentials for non-Cloudflare container registries

  Note this is a closed/experimental command that will not work without the appropriate account-level capabilities.

• #11078 5d7c4c2 Thanks @​simonha9! - Add jurisdiction support to d1 db creation via command-line argument

Patch Changes

• #11160 05440a1 Thanks @​dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when running wrangler deploy --env <TARGET_ENV>

  When running wrangler deploy, with --x-remote-diff-check and after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the --env|-e flag). Now this will also apply when an environment is targeted.

• #11162 c3ed531 Thanks @​dario-piotrowicz! - Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it

• #11162 c3ed531 Thanks @​dario-piotrowicz! - Fix bindings with remote: true being logged as remote when run via wrangler dev --local

• Updated dependencies [1ae020d]:

  • [email protected]

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.

... (truncated)

Commits

• cabbaf1 Version Packages (#11175)
• 240ebeb autoconfig small refactoring (#11183)
• 1ae020d Bump the workerd-and-workers-types group with 2 updates (#11185)
• 53b0fce Detect non-framework static sites (#11180)
• 5d7c4c2 Add jurisdiction support in wrangler for d1 (#11078)
• c3ed531 Various fixes/improvements around remote bindings being used as local (#11162)
• 05440a1 enable environment targeting in config patching with `wrangler deploy --x-rem...
• 305d7bf Full autoconfig flow for some projects (#11164)
• b55a3c7 add npx wrangler containers registry commands (#10605)
• a586c03 Version Packages (#11141)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by CodeRabbit

• Chores
  • Updated development dependency version. No changes to application functionality or public interfaces.

[coderabbitai]

Walkthrough

Updates the wrangler devDependency from version ^4.45.0 to ^4.46.0 in package.json, maintaining compatibility constraints and introducing no changes to code logic, public APIs, or configuration scripts.

Changes

Cohort / File(s)	Change Summary
Dependency version bump package.json	Bumps wrangler devDependency from ^4.45.0 to ^4.46.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• build(deps-dev): bump wrangler from 4.43.0 to 4.45.0 in the patch-versions group #339 — Modifies the same wrangler devDependency, bumping from ^4.45.0 which is the baseline for this update.
• build(deps-dev): bump wrangler from 4.42.0 to 4.42.2 in the patch-versions group #325 — Updates wrangler devDependency to a different target version, part of the same dependency maintenance pattern.
• build(deps-dev): bump wrangler from 4.33.1 to 4.34.0 in the patch-versions group #305 — Sequential wrangler version bump in package.json representing iterative dependency updates.

Suggested reviewers

• hanabi1224
• LesnyRumcajs

Poem

🐰 A carrot to Wrangler, version forth it hops!
From 4.45 to 4.46, the bumping never stops.
No logic harmed, just digits dance,
A minor leap in dev-dependency's prance! 📦✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping the wrangler dev dependency from version 4.45.0 to 4.46.0, with context about the dependency group.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/npm_and_yarn/patch-versions-ff24d1ed53

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b8dba2f and 80b3f53.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: deploy
• GitHub Check: E2E API Tests
• GitHub Check: E2E Browser Tests
• GitHub Check: E2E Claim Token API CORS Tests
• GitHub Check: codedov

🔇 Additional comments (1)

package.json (1)

10-10: Dependency update looks good.

The wrangler bump from 4.45.0 to 4.46.0 is a straightforward minor version update with backward-compatible improvements and no reported breaking changes. The caret constraint (^4.46.0) correctly allows compatible versions within the 4.x range.

Before merging, please verify that the project's existing wrangler workflows (build, dev, and start scripts) continue to function correctly with 4.46.0. You may want to run a quick sanity check on these commands locally if this PR is not already validated by CI.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.09%. Comparing base (b8dba2f) to head (80b3f53).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #351   +/-   ##
=======================================
  Coverage   41.09%   41.09%           
=======================================
  Files          40       40           
  Lines        2667     2667           
=======================================
  Hits         1096     1096           
  Misses       1571     1571           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.