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
34935	makemigrations --check no longer reports missing migrations	Adam Johnson	nobody	"Before #34051 (Django 4.2), you’d use this invocation to check for pending migrations:

{{{
$ ./manage.py makemigrations --dry-run --check
Migrations for 'example':
  example/migrations/0002_alter_author_name.py
    - Alter field name on author

$ echo $?
1
}}}


The to-be-generated migrations were reported.

#34051 changed so that migratinos aren’t generated when using only `--check`. But that means, with or without `--dry-run`, the migration operations are no longer output:

{{{
$ ./manage.py makemigrations --dry-run --check

$ echo $?
1
}}}

Thus, to see the pending migrations, the only option is to run again without `--check` and actually write them out. If you run `makemigrations --check` in CI, a failure requires an extra run, perhaps locally, before you can start to debug.

`-v 0` can (and could) always be used to mute the output if desired."	Bug	new	Migrations	4.2	Release blocker				Unreviewed	0	0	0	0	0	0