Data catalog errors are difficult to recover from, and users sometimes aren't aware that an action could delete or overwrite files from their buckets that could cause them. This change ensures R2 object and lifecycle commands now validate by default on actions that could leave data catalog-enabled buckets in an invalid state. By default, Wrangler will perform the catalog check with the header set, handle a 409 with an interactive prompt, and then if the user confirms, the request will be executed without the header/if user cancels, the request will be cancelled. Wrangler also has a --force flag to override any checks in interactive mode.

Proxy environment variables detected. We'll use your proxy for fetch requests.

 ⛅️ wrangler 4.73.0 (update available 4.75.0)
─────────────────────────────────────────────
Resource location: remote 

Creating object "meow.jpg" in bucket "bucket-1".
✔ Data catalog is enabled for this bucket. Proceeding may leave the data catalog in an invalid state. Continue? … yes
Upload complete.

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
    • built a local instance of wrangler and ran commands on that binary through a proxy that returns the real request format that R2 Gateway will return
  • Additional testing not necessary because:
    • local tests have been written
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: This is a flag addition to a few R2 commands, and has been added to the --help description

A picture of a cute animal (not mandatory, but encouraged)

   |\---/|
   | ,_, |
    \_`_/-..----.
 ___/ `   ' ,""+ \  sk
(__...'   __\    |`.___.';
  (_,...'(_,.`__)/'.....+