cloudflare-d1-migrations

To prevent schema drift in Cloudflare D1 migrations, coordinate creation, validation, and promotion across local, preview, and remote environments by reading Wrangler config and applying explicit ledger and schema checks before deployment.

Safe D1 migration promotion uses a preview-first approach, validating local state and respecting Wrangler D1 inventory bindings like database_name and migrations_dir before applying migrations to the remote environment.

Validating local D1 migration state involves reading the Wrangler D1 contract from config to check binding names, migrations_dir, and migrations_table, ensuring local files match the expected ledger state before promotion.

Recovering or baselining Cloudflare D1 migrations requires inspecting the current ledger and schema state, then using targeted import or recovery operations to realign migration files with the expected Wrangler D1 inventory.

Yes, D1 migration coordination adapts to custom Wrangler settings by reading the migrations_dir and migrations_table directly from the configuration contract, ensuring validation and promotion respect your specific inventory setup.