7.0b0: Add `MaxLengthValidator` to `Url.pattern`

What's Changed

• Url.pattern: Add MaxLengthValidator

  Fix compatibility issue with long Url.pattern from model_bakery and admin by @PetrDlouhy in #133

New Contributors

• @PetrDlouhy made their first contribution in #133

Full Changelog: 6.1...7.0b0

6.1 - Python 3.11+ compatibility fixes

What's Changed

• Fix pkg_resource deprecation warning, expand CI test matrix by @blag in #146

• Fix typos via typos

  • Special thanks to typo fix from @apoorvaeternity (Apoorva Pandey) in #145

New Contributors

• @blag made their first contribution in #146
• @apoorvaeternity should be credited for their find, while unmerged in #145

Full Changelog: 6.0...6.1

6.0 - Fix missing migration

Breaking change: Missing DEFAULT_AUTO_FIELD

This sets a DEFAULT_AUTO_FIELD to BigAutoField for robots in AppConfig. Previously, there was no app configuration or setting for this. (thank you @jan-szejko-steelseries in #134)

Robots 5.0 included a BigAutoField migration file for django 3.2 support (see #112), however, this caused an extra migration to be created to set django.db.models.AutoField for certain users (see #124).

Breaking: Migration issues

New django sites should work fine.

Existing sites that manually created migrations for robots 5.0:

If you ran ./manage.py makemigrations to bypass the #112 issue, you may need to resolve this manually if a custom migration you made for robots was applied in django_migrations.

Resources:
- https://docs.djangoproject.com/en/4.1/releases/3.2/#customizing-type-of-auto-created-primary-keys
- https://docs.djangoproject.com/en/3.2/ref/settings/#std-setting-DEFAULT_AUTO_FIELD

Packaging

• build: Remove django south migrations by @tony in #138

New Contributors

• @jan-szejko-steelseries made their first contribution in #134

Full Changelog: 5.0...6.0

6.0b0 - Add missing `DEFAULT_AUTO_FIELD`

Breaking change: Missing DEFAULT_AUTO_FIELD

This sets a DEFAULT_AUTO_FIELD to BigAutoField for robots in AppConfig. Previously, there was no app configuration or setting for this. (thank you @jan-szejko-steelseries in #134)

Robots 5.0 included a BigAutoField migration file for django 3.2 support (see #112), however, this caused an extra migration to be created to set django.db.models.AutoField for certain users (see #124).

Breaking: Migration issues

New django sites should work fine.

Existing sites that manually created migrations for robots 5.0:

If you ran ./manage.py makemigrations to bypass the #112 issue, you may need to resolve this manually if a custom migration you made for robots was applied in django_migrations.

Resources:
- https://docs.djangoproject.com/en/4.1/releases/3.2/#customizing-type-of-auto-created-primary-keys
- https://docs.djangoproject.com/en/3.2/ref/settings/#std-setting-DEFAULT_AUTO_FIELD

Packaging

• build: Remove django south migrations by @tony in #138

New Contributors

• @pre-commit-ci made their first contribution in #126
• @jan-szejko-steelseries made their first contribution in #134

Full Changelog: 5.0...6.0b0

5.0 - including django 4 support

This may be the only prerelease. Will have shareholders from our django 4.0 threads give this a try first

What's Changed

• Use gettext_lazy for Python 3 code by @noisecapella in #99
• Updated code style for isort v5 and black 20.8b1 by @smithdc1 in #104
• Dropped support for Python 2.7 and 3.5 by @smithdc1 in #105
• Migrate to GitHub Actions. by @jezdez in #106
• Updated supported versions. Added Django 3.1 and Python 3.9. Dropped Django 2.2 and below. by @smithdc1 in #107
• Rename Django's dev branch to main. by @jezdez in #110
• add django 3.2 and 4.0 support by @umarmughal824 in #112
• Add Python 3.10 support by @Andrew-Chen-Wang in #113
• Jazzband: Synced file(s) with jazzband/.github by @jazzband-bot in #115
• Update Django 4 documentation by @sergioisidoro in #119
• Deprecate python 3.6 by @tony in #120
• Add .pre-commit-config.yaml by @tony in #122
• docs(CHANGES): Update for next release by @tony in #121

New Contributors

• @noisecapella made their first contribution in #99
• @smithdc1 made their first contribution in #104
• @jezdez made their first contribution in #106
• @umarmughal824 made their first contribution in #112
• @Andrew-Chen-Wang made their first contribution in #113
• @sergioisidoro made their first contribution in #119

Full Changelog: 4.0...5.0b1

5.0 beta 1

This may be the only prerelease. Will have shareholders from our django 4.0 threads give this a try first

What's Changed

• Use gettext_lazy for Python 3 code by @noisecapella in #99
• Updated code style for isort v5 and black 20.8b1 by @smithdc1 in #104
• Dropped support for Python 2.7 and 3.5 by @smithdc1 in #105
• Migrate to GitHub Actions. by @jezdez in #106
• Updated supported versions. Added Django 3.1 and Python 3.9. Dropped Django 2.2 and below. by @smithdc1 in #107
• Rename Django's dev branch to main. by @jezdez in #110
• add django 3.2 and 4.0 support by @umarmughal824 in #112
• Add Python 3.10 support by @Andrew-Chen-Wang in #113
• Jazzband: Synced file(s) with jazzband/.github by @jazzband-bot in #115
• Update Django 4 documentation by @sergioisidoro in #119
• Deprecate python 3.6 by @tony in #120
• Add .pre-commit-config.yaml by @tony in #122
• docs(CHANGES): Update for next release by @tony in #121

New Contributors

• @noisecapella made their first contribution in #99
• @smithdc1 made their first contribution in #104
• @jezdez made their first contribution in #106
• @umarmughal824 made their first contribution in #112
• @Andrew-Chen-Wang made their first contribution in #113
• @sergioisidoro made their first contribution in #119

Full Changelog: 4.0...5.0b1

Support for Django 2.1, 2.2 and 3.0 and Python 3.7 and 3.8.

• Support for Django 2.1, 2.2, 3.0 and Python 3.7 and 3.8.
• Updated the requirements for dropped support of six in Django 3.
• Restructure test setup to use setuptools-scm and more modern Python
  patterns.