id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
25231	Incomplete Fix for #24628 - Squashed Migration Still Not Marked as Applied	Mark Lavin	nobody	I'm still seeing this behavior in 1.8.3 so I believe that this fix is incomplete. The  problem with the original fix is that it relies on the {{{executor.migrate}}} method being called. While that is done by the tests, it isn't when following the workflow described in the docs. When you call the {{{migrate}}} management command, it first checks the migration plan to see if any migrations need to be run. Since the migration plan sees the replacement migration as already applied there is no plan (assuming there are no other unapplied migrations) and the {{{executor.migrate}}} is never called. In this case the replacement migration is never recorded as applied. Then when the old migrations are removed and the {{{replaces}}} attribute is removed, the {{{migrate}}} command attempts to run the squashed migration which fails since the tables, etc already exist.	Bug	closed	Migrations	1.8	Normal	fixed		Simon Charette	Ready for checkin	1	0	0	0	0	0