From 9ad7bcced0823172083426e605f1d7234b8e062f Mon Sep 17 00:00:00 2001 From: David Wobrock Date: Mon, 3 Oct 2022 15:47:19 +0200 Subject: [PATCH] Add release not for IgnoreMigration.elidable=True change. --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1a43836..63d24f6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,7 @@ Instead, the linter crashes and lets the `sqlmigrate` error raise, in order to a One common reason for such an error is the SQL generation which requires the database to be actually migrated in order to fetch actual constraint names from it. The crash is a sign to double-check the migration. But if you are certain the migration is safe, you can ignore it (issue #209) - Fixed `RunPython` model import check when using a `through` object like `MyModel.many_to_many.through.objects.filter(...)` (issue #218) +- Mark the `IgnoreMigration` operation as `elidable=True` ## 4.1.0