4.3

What's Changed

• Add disabled mode to avoid safemigrate's protections. by @tim-schilling in #49

Full Changelog: 4.2...4.3

4.2

What's Changed

• Fix example pre-commit hook by @ryanhiebert in #41
• Add support for Django 5.0 by @ryanhiebert in #43

Full Changelog: 4.1...4.2

4.1

What's Changed

• Add pre-commit hook by @ryanhiebert in #40

Full Changelog: 4.0...4.1

4.0

What's Changed

• Utilize pre-commit to manage lint and styles. by @tim-schilling in #35
• Upgrade GitHub test action to use latest action versions. by @tim-schilling in #36
• Drop support for Python 3.6, 3.7
• Drop support for Django 3.0, 3.1

Full Changelog: 3.1...4.0

3.1

Add support for Django 4.0

3.0

Drop support for Django 2

2.1

Add support for Django 3

2.0

• The valid values for safe are:
  • Safe.before_deploy
  • Safe.after_deploy
  • Safe.always
    Import with from django_safemigrate import Safe. True is now Safe.before_deploy, and False is now Safe.after_deploy.
• The default safety marking, when unspecified, is now Safe.after_deploy, instead of Safe.before_deploy.
• Safe.always allows for migrations that may be run either before or after deployment, because they don't require any database changes.
• Multiple dependent Safe.after_deploy migrations do not block deployment as long as there are no dependent Safe.before_deploy migrations.
• Enforce that any given value of safe is valid.

1.0

Prepare initial release