Change8

wrangler@4.107.0

📦 cloudflare-workersView on GitHub →
8 features🔧 13 symbols

Summary

This release introduces significant enhancements for managing Durable Object lifecycles declaratively via `wrangler.json` exports and adds optional OS keyring encryption for OAuth credentials. New `wrangler flagship` commands are also available for managing feature flags.

Migration Steps

  1. When defining Durable Object lifecycle changes, consider migrating from the legacy `migrations` array to the declarative `exports` map in `wrangler.json`. Wrangler will now suggest declarative `exports` entries if bindings are declared but no lifecycle configuration is present.
  2. If using multi-version deploys involving declarative exports changes, ensure the version that modifies `exports` is deployed at 100% traffic before attempting a percentage-split deploy involving other versions.
  3. To enable OS keyring storage for OAuth credentials, run `wrangler login --use-keyring`. Existing plaintext credentials will be migrated automatically on first use.

✨ New Features

  • Added support for setting cache options on WorkerEntrypoint exports and configuring cross-version cache behavior globally via wrangler.json.
  • Introduced declarative Durable Object exports in wrangler.json as an alternative to the legacy migrations array for managing DO lifecycle (creation, deletion, renaming, transfer).
  • wrangler deploy now surfaces detailed server reconciliation results for Durable Object lifecycle changes.
  • wrangler dev, vite dev, and unstable_startWorker now read Durable Object SQLite storage settings from the new declarative exports field.
  • @cloudflare/vitest-pool-workers now uses Durable Object configuration from exports for local testing.
  • wrangler types is now aware of exports, adding live DO entries to Cloudflare.GlobalProps.durableNamespaces for unbound DOs declared only via exports.
  • Added new `wrangler flagship` command groups for managing Flagship applications and feature flags via CLI (create, list, update, rollout, etc.).
  • Added an opt-in mechanism for storing OAuth credentials in the OS keyring (macOS Keychain, Linux libsecret, Windows Credential Manager) instead of plaintext files.

Affected Symbols