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
..
__init__.py	New migrations system, ported from sqlite-migrate (#754)	2026-06-21 09:40:21 -07:00
__main__.py	Support 'python -m sqlite_utils', closes #368	2022-01-08 18:33:22 -08:00
cli.py	migrate --stop-before: validate names and fix legacy compatibility	2026-07-04 19:08:53 +00:00
db.py	enable_wal() and disable_wal() refuse to run inside a transaction	2026-07-04 18:46:09 +00:00
hookspecs.py	More type annotations (#697)	2025-12-16 22:11:47 -08:00
migrations.py	Correct applied_at type annotation to str	2026-07-04 18:47:08 +00:00
plugins.py	fix: Plugins are still loaded when running tests (#719)	2026-06-21 16:14:45 -07:00
py.typed	py.typed file so mypy picks up the types, closes #331	2021-11-14 15:21:04 -08:00
recipes.py	More type annotations (#697)	2025-12-16 22:11:47 -08:00
utils.py	Test against Python 3.15-dev, bump ty and Black (#738)	2026-05-17 16:52:48 -07:00