Django requires every change to model fields and meta classes to be reflected in database migrations. This applies even to things that don’t typically affect the database, such as Field.choices. When iterating on code, it’s easy to make a model change and forget to update the migrations accordingly. If you don’t have any protection, you might even deploy code that crashes due to out-of-date migrations!

AdamJ's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, AdamJ offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

Adam Johnson

The post explains how to safeguard against out-of-date migrations in Django by using the `makemigrations` command with `--dry-run` and `--check` flags. It provides an example of automating this check within a test case, ensuring pending migrations are caught before deployment. The test runs `makemigrations` and raises an `AssertionError` if migrations are pending, failing the test and alerting the developer.

Django: Test for pending migrations