[wrangler] Fix nested D1 migrations

[swalker326]

Fixes #13257.

Fix D1 migration discovery so wrangler d1 migrations list and wrangler d1 migrations apply recursively include nested .sql files under migrations_dir. Nested migrations are recorded using relative paths, and wrangler d1 migrations create now accounts for nested numeric prefixes when choosing the next migration number.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: this fixes existing Wrangler D1 migration behavior without changing public command usage.

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

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 873f35c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
wrangler	Patch
@cloudflare/vite-plugin	Patch
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[workers-devprod]

Codeowners approval required for this PR:

• @cloudflare/d1
• ✅ @cloudflare/wrangler

Show detailed file reviewers

• packages/wrangler/src/tests/d1/migrate.test.ts: [@cloudflare/d1]
• packages/wrangler/src/tests/d1/migrations/helpers.test.ts: [@cloudflare/d1]
• packages/wrangler/src/d1/execute.ts: [@cloudflare/d1]
• packages/wrangler/src/d1/migrations/apply.ts: [@cloudflare/d1]
• packages/wrangler/src/d1/migrations/helpers.ts: [@cloudflare/d1]

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 6 additional findings.

[NuroDev]

Great little fix. Thank you @swalker326!

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@13913

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@13913

miniflare

npm i https://pkg.pr.new/miniflare@13913

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@13913

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@13913

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@13913

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@13913

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@13913

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@13913

wrangler

npm i https://pkg.pr.new/wrangler@13913

commit: 873f35c

[k0d13]

A little concerned that this may break existing flows
I use drizzle and just have a script that copies the drizzle//migration.sql, modifies it, and writes it to drizzle/.sql
If nested support alone is added, how will it handle both the old drizzle/.sql and the "new" drizzle//migration.sql?

[swalker326]

A little concerned that this may break existing flows I use drizzle and just have a script that copies the drizzle//migration.sql, modifies it, and writes it to drizzle/.sql If nested support alone is added, how will it handle both the old drizzle/.sql and the "new" drizzle//migration.sql?

Nested directories are not required, they're just supported with this PR. You can put top level *.sql files OR folders with *.sql files in them. For your setup you would see no change, continue to copy the sql files over.