Skip to content

Latest commit

 

History

History
1 lines (1 loc) · 774 Bytes

File metadata and controls

1 lines (1 loc) · 774 Bytes
  • CLI: migration failures now reach the exit code. A failed up()/down() step that migrateTo() folds into its output (e.g. Error migrating to <version>.) made wheels migrate latest|up|down print the error inside the green success block and still exit 0; wheels db reset --force exited 0 when it refused on a ServerNotRunning check; and wheels migrate forget|pretend refusals (not in tracking table, matching local file exists, already applied, no matching file) printed red but exited 0. All three now exit non-zero, so a wheels migrate latest && … CI gate no longer proceeds as if the schema moved. Informational dry-run output (missing <version> / missing --yes) still exits 0. The migrate-side sibling of the #2973/#2987 seeder honesty fix (#3081)