Update dependency wrangler to v4.62.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	4.61.1 → 4.62.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v4.62.0

Compare Source

Minor Changes

• #​12064 964a39d Thanks @​G4brym! - Add AI Search OAuth scopes to login

  Adds ai-search:write and ai-search:run OAuth scopes to the default login scopes, enabling wrangler to authenticate with AI Search APIs.

• #​11867 253a85d Thanks @​rahulsuresh-git! - Add wrangler r2 bucket local-uploads command to manage local uploads for R2 buckets

  When enabled, object data is written to the nearest region first, then asynchronously replicated to the bucket's primary region.

  Docs: https://developers.cloudflare.com/r2/buckets/local-uploads

  # Get local uploads status
  wrangler r2 bucket local-uploads get my-bucket
  
  # Enable local uploads (will prompt for confirmation)
  wrangler r2 bucket local-uploads enable my-bucket
  
  # Enable without confirmation prompt
  wrangler r2 bucket local-uploads enable my-bucket --force
  
  # Disable local uploads
  wrangler r2 bucket local-uploads disable my-bucket

• #​11803 1bd1488 Thanks @​dario-piotrowicz! - Add a new subrequests limit to the limits field of the Wrangler configuration file

  Before only the cpu_ms limit was supported in the limits field of the Wrangler configuration file, now a subrequests limit can be specified as well which enables the user to limit the number of fetch requests that a Worker's invocation can make.

  Example:

  {
  	"$schema": "./node_modules/wrangler/config-schema.json",
  	"limits": {
  		"cpu_ms": 1000,
  		"subrequests": 150 // newly added field
  	}
  }

• #​12185 f7aa8c7 Thanks @​penalosa! - Add timestamp field to the version metadata binding in local development. The version metadata binding now includes id, tag, and timestamp fields, making it easier to test version-aware logic locally.

Patch Changes

• #​12190 ce736b9 Thanks @​dario-piotrowicz! - Update autoconfig logic to handle Next.js projects by using the new @opennextjs/cloudflare migrate command

• #​12065 47944d1 Thanks @​langningchen! - Improve error message when d1 export --output points to a directory

• #​12292 4c4d5a5 Thanks @​dario-piotrowicz! - Add versionCommand to the autoconfig_summary field in the autoconfig output entry

  Add the version upload command to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY/WRANGLER_OUTPUT_FILE_PATH. This complements the existing buildCommand and deployCommand fields and allows CI systems to know how to upload new versions of Workers.

  For example, for a standard npm project this would be:

  • Version command: npx wrangler versions upload

  While for a Next.js project it would be:

  • Version command: npx @​opennextjs/cloudflare upload

• #​12050 b05b919 Thanks @​NuroDev! - Fixed Wrangler's error handling for both invalid commands with and without the --help flag, ensuring consistent and clear error messages.

  Additionally, it also ensures that if you provide an invalid argument to a valid command, Wrangler will now correctly display that specific commands help menu.

• #​12289 0aaf080 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260128.0	1.20260129.0

• #​12295 b981db5 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260129.0	1.20260130.0

• #​12355 a113c0d Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260130.0	1.20260131.0

• #​11971 fdd7a9f Thanks @​dario-piotrowicz! - Add framework id, build command, and deploy command to the autoconfig_summary field in the deploy output entry

  Add the framework id alongside the commands to build and deploy the project to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH.

  For example for an npm Astro project these would be:

  • Framework id: astro
  • Build command: npm run build
  • Deploy command: npx wrangler deploy

  While for a Next.js project they would instead be:

  • Framework id: next
  • Build command: npx @​opennextjs/cloudflare build
  • Deploy command: npx @​opennextjs/cloudflare deploy

• #​12211 a5fca2c Thanks @​elithrar! - Remove the 'pubsub' sub-command and related functionality

  The Pub/Sub product was never made publicly available and has been discontinued. This removes the wrangler pubsub command and all associated functionality.

• Updated dependencies [0c9625a, 0aaf080, b981db5, a113c0d, f7aa8c7]:

  • miniflare@​4.20260131.0
  • @​cloudflare/kv-asset-handler@​0.4.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	disclip	85afbc4	Commit Preview URL Branch Preview URL	Feb 03 2026, 02:52 PM