Diego Imbert e896506ae6 fix(cli): run deployed datatable migrations after workspace merge ...

The merge command upserted datatable_migration definitions into the target
workspace and reported the item as successfully deployed, but never ran the
migrations. For forked datatables backed by separate databases, this left the
target schema unchanged until someone manually ran `wmill datatable migrate up`,
while the CLI reported a successful merge.

Collect the datatable migrations deployed (not deleted) into the target and,
after the deploy loop, offer to run them via the existing offerToRunNewMigrations
helper — the same post-deploy run prompt the push/sync path uses (interactive
only; `--yes`/non-TTY skip the mutating run, matching push behavior). Export
parseDatatableMigrationDeployPath so the merge path can parse the deployed items.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-06 14:17:23 +02:00

..

commands

fix(cli): run deployed datatable migrations after workspace merge

2026-07-06 14:17:23 +02:00

core

chore(main): release 1.749.0 (#9938)

2026-07-06 01:40:42 +02:00

guidance

fix(cli): datatable migrate up/down default to main datatable, not all

2026-07-06 09:58:13 +02:00

utils

fix(cli): pipeline + workspace UX batch (init/bind stub, run errors, macro libs, lock-job report, upgrade errors) (#9929)

2026-07-05 16:24:04 +02:00

main.ts

feat: Data Pipelines alpha (#9193)

2026-06-18 18:09:02 +02:00

types.ts

nit

2026-07-03 21:15:48 +02:00