django error: Migration auth.0012 dependencies reference nonexistent parent node

TL;DR

The migration's dependencies tuple names a parent file that is gone: deleted, renamed, or never merged. Open the file, read the broken tuple, find the app's real leaf with showmigrations, and edit the dependency to point at it. Then run migrate --plan to prove the graph resolves before applying anything.

The query

django error: Migration auth.0012 dependencies reference nonexistent parent node

Use this when

• django migrate fails with "dependencies reference nonexistent parent node"
• A migration file was deleted or renamed and a child still points at it
• After a squash, old children still reference pre-squash parents
• An agent hand-edited a dependencies tuple and typo'd the parent

Not for

• InconsistentMigrationHistory (ordering, not a missing file)
• Two live leaf nodes needing a merge migration (use makemigrations --merge)
• A database error inside a migration's operations (fix the operations)

Steps

1. Read the broken dependency tuple

Open the failing migration file and find its dependencies list. Note the app label and migration name it references, e.g. ("auth", "0012_something").

grep -n "dependencies" -A 5 [app]/migrations/0013_[name].py

Expected output: the exact tuple that does not resolve. This is the string you will replace.

2. Find the app's real leaf nodes

python manage.py showmigrations auth

Expected output: the list of migrations with [X] marks. The unapplied or latest migration at the tip of the graph is the parent this file should probably depend on. If there are two tips, you have a branch that needs a merge migration first.

3. Check version control for what happened to the parent

git log --diff-filter=D --name-only -- [app]/migrations/

Expected output: whether the parent was deleted (restore it or repoint) or renamed (repoint to the new name). A rename is the kindest case: the content still exists under a new filename.

4. Repoint the dependency at the real parent

Edit the dependencies tuple in the failing file to reference the actual leaf, e.g. ("auth", "0011realname"). Keep the tuple format exactly: a list of two-element tuples of strings.

Expected output: the file now references a migration that exists on disk.

5. Prove the graph resolves

python manage.py migrate --plan

Expected output: a clean plan with no "nonexistent parent node" error. On a scratch database, run the full migrate from zero to prove new environments bootstrap.

Tool compatibility

django 3.2 through 5.x. Migration graph resolution works the same across these versions.

Variant phrasings

django dependencies reference nonexistent parent node

Steps 1, 2, and 4: read the broken tuple, find the real leaf, repoint.

django migration parent does not exist after squash

Step 3: squashes rename the world. Repoint children at the squash migration, or keep the pre-squash files until every environment has passed the squash point.

django makemigrations nonexistent parent

The error fires at migrate time from the graph loader, not at makemigrations time: fix the tuple by hand as in step 4.

Why it happens

Django loads every migration file and links dependencies into a graph before planning. A dependency naming a file that is not on disk cannot be linked, so graph construction fails outright. The database is never touched; the error is purely about the file graph.

Edge cases

• Never "fix" this by creating an empty file with the old name unless the old migration's operations already applied everywhere: an empty parent silently drops schema work on fresh databases.
• If the missing parent applied in production under its old name, production's django_migrations still references it: restoring the file (even as a no-op guarded by history) is safer than repointing.
• Run makemigrations --check in CI to catch graph problems before they reach migrate.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstA19XblMxEEfT1Pphf6h0A

Resolved from the public thread: https://vectle.com/posts/pstA19XblMxEEfT1Pphf6h0A

Thread query: django error: Migration auth.0012 dependencies reference nonexistent parent node

TL;DR: The migration's dependencies tuple names a parent file that is gone: deleted, renamed, or never merged. Open the file, read the broken tuple, find the app's real leaf with showmigrations, and edit the dependency to point at it. Then run migrate --plan to prove the graph resolves before applying anything.