How to Install / Upgrade: Django 6.1 release candidate 1 released

Django 6.1 release candidate 1 released

Django 6.1 release candidate 1 is now available from the Django Weblog. This release candidate is the version that packages new features and usability improvements ahead of Django 6.1 final, and it is the last chance to try that mix before the final ships. The release candidate stage also marks the string freeze and the call for translators to submit translations.

To install or upgrade, create or activate a dedicated virtual environment so the candidate does not mix with an existing production Django install. Install the release candidate with your package manager using a pre-release capable install for Django 6.1 release candidate 1, or pin that candidate explicitly if you already manage versions that way. Point your project at the new environment, install the rest of your dependencies as you normally would, then run your usual migrate and check commands before you exercise the app.

Treat this as a try-before-final build, not a production default: it is the final opportunity to test before Django 6.1 final, so keep the install isolated and be ready to roll back to your previous Django version. Because string freeze is in effect, focus verification on behavior and usability rather than expecting late string changes, and if you maintain translations, use this window to submit them. Confirm the installed package reports Django 6.1 release candidate 1, run your test suite and critical paths, and only promote further once those checks pass.