chore(deps-dev): bump @opennextjs/cloudflare from 1.19.11 to 1.20.1

[dependabot]

Bumps @opennextjs/cloudflare from 1.19.11 to 1.20.1.

Release notes

Sourced from @​opennextjs/cloudflare's releases.

@​opennextjs/cloudflare@​1.20.1

Patch Changes

• #1297 780a21c Thanks @​james-elicx! - fix: disable response compression for skew protection API requests

  Avoid truncated compressed Cloudflare API responses causing worker version lookups to fail during deployment.

@​opennextjs/cloudflare@​1.20.0

Minor Changes

• #1290 46c50fc Thanks @​james-elicx! - feature: add opt-in batch upload via rclone for fast R2 cache population.

  Key Changes:

  1. Optional rclone Upload: Install the optional rclone.js peer dependency and pass --rclone to opt in to rclone based batch uploads.

     • R2_ACCESS_KEY_ID
     • R2_SECRET_ACCESS_KEY
     • CF_ACCOUNT_ID

  2. Explicit Opt-in: The existing worker-based population path remains the default. rclone is only loaded when --rclone is used for a remote cache.

  3. Clear Errors: The CLI reports missing credentials or a missing rclone.js installation when the option is used.

  Usage:

  Install rclone.js, then add the secrets in a .env/.dev.vars file in your project root:

  pnpm add rclone.js
  pnpm approve-builds # select rclone.js
  pnpm rebuild rclone.js
  R2_ACCESS_KEY_ID=your_key
  R2_SECRET_ACCESS_KEY=your_secret
  CF_ACCOUNT_ID=your_account
  opennextjs-cloudflare deploy --rclone

  You can also set the environment variables for CI builds.

  Notes:

  • You can follow documentation https://developers.cloudflare.com/r2/api/tokens/ for creating API tokens with appropriate permissions for R2 access.
  • rclone may not be supported on all platforms.

Patch Changes

• #1289 eef243f Thanks @​thatssoheil! - fix: spread SQLite bindings in BucketCachePurge alarm so tag purges run

  BucketCachePurge.alarm() passed its tag bindings to SqlStorage.exec as a

... (truncated)

Changelog

Sourced from @​opennextjs/cloudflare's changelog.

1.20.1

Patch Changes

• #1297 780a21c Thanks @​james-elicx! - fix: disable response compression for skew protection API requests

  Avoid truncated compressed Cloudflare API responses causing worker version lookups to fail during deployment.

1.20.0

Minor Changes

• #1290 46c50fc Thanks @​james-elicx! - feature: add opt-in batch upload via rclone for fast R2 cache population.

  Key Changes:

  1. Optional rclone Upload: Install the optional rclone.js peer dependency and pass --rclone to opt in to rclone based batch uploads.

     • R2_ACCESS_KEY_ID
     • R2_SECRET_ACCESS_KEY
     • CF_ACCOUNT_ID

  2. Explicit Opt-in: The existing worker-based population path remains the default. rclone is only loaded when --rclone is used for a remote cache.

  3. Clear Errors: The CLI reports missing credentials or a missing rclone.js installation when the option is used.

  Usage:

  Install rclone.js, then add the secrets in a .env/.dev.vars file in your project root:

  pnpm add rclone.js
  pnpm approve-builds # select rclone.js
  pnpm rebuild rclone.js
  R2_ACCESS_KEY_ID=your_key
  R2_SECRET_ACCESS_KEY=your_secret
  CF_ACCOUNT_ID=your_account
  opennextjs-cloudflare deploy --rclone

  You can also set the environment variables for CI builds.

  Notes:

  • You can follow documentation https://developers.cloudflare.com/r2/api/tokens/ for creating API tokens with appropriate permissions for R2 access.
  • rclone may not be supported on all platforms.

Patch Changes

• #1289 eef243f Thanks @​thatssoheil! - fix: spread SQLite bindings in BucketCachePurge alarm so tag purges run

... (truncated)

Commits

• 1a70b33 Version Packages (#1298)
• 780a21c fix: disable compression for worker version requests (#1297)
• 127942d Version Packages (#1292)
• 46c50fc feat: add opt-in rclone cache population (#1290)
• eef243f fix(cache-purge): spread SQLite bindings in BucketCachePurge alarm so tag pur...
• 51439b1 fix: disable compression for R2 provisioning (#1291)
• See full diff in compare view

You can trigger a rebase of this PR 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 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[os-project-manager]

Held — not merged in this pass, and the reason is specific to this PR

Reviewed by the repo:objectos PM seat (objectstack#9831), round 1, 2026-08-22, under a maintainer instruction to land the Dependabot PRs that should land. Five of the seven are moving. This one is held, and it is the only one held on its own merits.

Why this one is different from the other four npm bumps. They upgrade libraries whose output the required build job actually exercises — turbo run build runs next build against the new React / Tailwind. This PR upgrades the deploy adapter, and the command it changes is opennextjs-cloudflare build && opennextjs-cloudflare deploy (apps/docs/package.json). No required check runs that command. next build loads the adapter's config import, so an outright broken export would surface — but the adapter's own build-and-deploy CLI, which is the part being upgraded, is not covered.

And the blast radius is immediate, not deferred. deploy-docs.yml triggers on push to main with pnpm-lock.yaml in its paths: filter, deploying to the cloudflare-docs environment at https://docs-objectos.objectstack.workers.dev. So merging this PR does not merely change a version — it ships a production docs deploy through an untested toolchain in the same motion. If it breaks, the first evidence is the live site.

Two secondary observations, neither decisive on its own:

• The declared floor moves ^1.13.0 → ^1.20.1, a seven-minor jump in what the manifest claims, even though the installed version only moves 1.19.11 → 1.20.1.
• The lockfile churn is 661 insertions / 729 deletions — by a wide margin the largest of the five (the others are 25/20, 110/88, 137/137, 365/365). Checked for the interaction that would matter most: it does not move wrangler, which stays at 4.95.0, so the yargs ranges that objectos#137 reasons about are untouched. But a 1390-line rewrite for one devDependency bump deserves a human glance rather than a seat's rubber stamp.

What would unblock it: a pnpm run deploy dry run (or opennextjs-cloudflare build alone, which needs no Cloudflare credentials) against this branch. If that passes, the PR is fine and I will land it.

This is a judgement call the seat is declaring rather than making silently — if you would rather take the bump and watch the deploy, say so and I will merge it. It is a docs site with a revert path, not a one-way door.

---

Generated by Claude Code

[dependabot]

Superseded by #162.