fix: remove django-linear-migrations#14571
Merged
mtesauro merged 1 commit intoDefectDojo:bugfixfrom Mar 27, 2026
Merged
Conversation
github-actions
bot
added
New Migration
valentijnscholten
added
affects_pro
Removes django-linear-migrations from requirements-dev.txt, INSTALLED_APPS, and deletes max_migration.txt. The tool caused startup failures when the package was not installed but DD_DEBUG=True.
valentijnscholten
force-pushed
the
remove-linear-migrations
branch
from
4e0f1a5 to
2dad4f7
Compare
github-actions
bot
added
the
New Migration
Maffooch
approved these changes
Mar 25, 2026
Jino-T
approved these changes
Mar 26, 2026
3 tasks
3 tasks
blakeaowens
approved these changes
Mar 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes
django-linear-migrationsfrom the project. The tool caused startup failures whenDD_DEBUG=Truebut the package was not installed (e.g. production images). Too much hassle with low gains. Any non-linear migration will be caught on startup by django anyway during unit tests.