3 commits

Author	SHA1	Message	Date
Claude	30cc95c0a6	migrate --list is now read-only ... pending() and applied() no longer create the _sqlite_migrations table or perform the one-way legacy schema upgrade - that now only happens in apply(). The CLI --list path no longer creates the database file when it does not exist. applied() results are now explicitly ordered by insertion. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UnLnhsH25Nnv7LHhekUfPd	2026-07-04 19:10:56 +00:00
Claude	0bad21280f	migrate --stop-before: validate names and fix legacy compatibility ... An unknown --stop-before value previously matched nothing and every migration was silently applied, including the one the user meant to stop before. The CLI now errors unless each value matches a known migration. The CLI also always passed stop_before as a list, but older duck-typed sqlite-migrate Migrations objects compare it against a single string name - so the flag was silently ignored for exactly the migration files the compatibility shim exists to support. Legacy sets now receive a single string, with an error if multiple values target one legacy set. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UnLnhsH25Nnv7LHhekUfPd	2026-07-04 19:08:53 +00:00
Simon Willison	3cc27d69bc	New migrations system, ported from sqlite-migrate (#754) ... Closes #752	2026-06-21 09:40:21 -07:00