build(deps-dev): bump django-migration-linter from 4.1.0 to 5.0.0

[dependabot]

Bumps django-migration-linter from 4.1.0 to 5.0.0.

Release notes

Sourced from django-migration-linter's releases.

5.0.0

Breaking change: stop silently ignoring when the internal sqlmigrate call fails and the linter cannot analyse the migration. Instead, the linter crashes and lets the sqlmigrate error raise, in order to avoid letting a problematic migration pass. 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)

Features:

• 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
• Handle functools.partial functions in RunPython data migrations
• Add a new check, CREATE_INDEX_EXCLUSIVE to detect index creation while an exclusive lock is held

Bug:

• Don't detect not nullable field on partial index creation (issue #250)

Miscellaneous:

• Add support for Python 3.11
• Add support for Django 4.1
• Add support for Django 4.2
• Drop support for Django 2.2
• Internally rename "migration tests" to "migration checks"
• Add dataclasses internally instead of custom dicts
• Use pre-commit hooks for linting
• Add mypy and ruff usages

Changelog

Sourced from django-migration-linter's changelog.

5.0.0

• Breaking change: stop silently ignoring when the internal sqlmigrate call fails and the linter cannot analyse the migration. Instead, the linter crashes and lets the sqlmigrate error raise, in order to avoid letting a problematic migration pass. 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)

Features:

• 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
• Handle functools.partial functions in RunPython data migrations
• Add a new check, CREATE_INDEX_EXCLUSIVE to detect index creation while an exclusive lock is held

Bug:

• Don't detect not nullable field on partial index creation (issue #250)

Miscellaneous:

• Add support for Python 3.11
• Add support for Django 4.1
• Add support for Django 4.2
• Drop support for Django 2.2
• Internally rename "migration tests" to "migration checks"
• Add dataclasses internally instead of custom dicts
• Use pre-commit hooks for linting
• Add mypy and ruff usages

Commits

• 3503367 Bump to 5.0.0
• a856f0d Apply updated pre-commit hooks.
• 5695a95 Move CHANGELOG line to new features section.
• 86b660f Also flag concurrent index creation
• 15dbe22 Add a CHANGELOG entry for the new check
• 48fac88 Downgrade CREATE_INDEX_EXCLUSIVE to a warning
• 0c5519d Add new check for indexing with atomic=True
• 9fdfa06 Fix error output when warnings are found
• 2d15ea8 Support partial function inspection in data migrations
• 97a1f5c Fix #250 -- Don't consider partial index creation as making a column not null...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: poetry dependencies.