Shift with red gradient lettering

Upgrade Django 4.0 to Django 4.1

The Django 4.1 Shift automates the upgrade of your Django application from Django 4.0 to Django 4.1. Using the Django 4.1 Shift to automatically upgrade your Django application has an estimated time savings of 1 hour.

Django 4.1 is the latest stable release. This means both Django and the Django 4.1 Shift will continue to receive updates.

Screenshot of a pull request with automated changes from the Django 4.1 Shift


  • A Django application running Django 4.0.
  • A server running Python 3.8 or higher.

Automated Upgrades

The Django 4.1 Shift automates many of the backwards incompatible changes and deprecations for Django 4.1, including:

  • Updating dependencies for Django 4.1.
  • Renaming core methods and variables.
  • Updating deprecated values for nulls_first and nulls_last.
  • Renaming whitelist variables within EmailValidator.
  • Removing default_app_config variables.
  • Detecting backward incompatibilities within your application code.

Manual Upgrades

There are some upgrades the Django 4.1 Shift can not perform automatically. When Shift detects these it adds a detailed comment to the Pull Request to guide any additional steps you may need to do manually.

While Shift attempts to detect and automate the updates for popular community dependencies, you may need to update some of your dependencies manually. Always review the changelog for your dependencies for any additional changes.

Sign in with any of the following services to connect Shift with your Laravel project.

Don't use one of these services?

Temporarily push your project to a free, private repository on one of these cloud-based services or upgrade your project locally with Shift for Docker.