Bump django-registration from 3.4 to 5.2.1

[dependabot]

Bumps django-registration from 3.4 to 5.2.1.

Changelog

Sourced from django-registration's changelog.

.. _changelog:

Changelog

This document lists changes between released versions of django-registration.

Version numbering

django-registration uses "DjangoVer", a version number system based on the corresponding supported Django versions. The format of a django-registration version number is A.B.C, where A.B is the version number of the latest Django feature release supported by that version of django-registration, and C is an incrementing value for releases of django-registration paired to that Django feature release.

The policy of django-registration is to support the Django feature release indicated in the version number, along with any other lower-numbered Django feature releases receiving support from the Django project at the time of release.

For example, consider a hypothetical django-registration version 5.0.2. This indicates that the most recent supported Django feature release is 5.0, and that it is the third release of django-registration to support Django 5.0 (after 5.0.0 and 5.0.1). Since the Django project at the time was supporting Django 5.0 and 4.2, that version of django-registration would also support Django 5.0 and 4.2.

API stability and deprecations

The API stability/deprecation policy for django-registration is as follows:

• The supported stable public API is the set of symbols which are documented in this documentation. For classes, the supported stable public API is the set of methods and attributes of those classes whose names do not begin with one or more underscore (_) characters and which are documented in this documentation.

• When a public API is to be removed, or undergo a backwards-incompatible change, it will emit a deprecation warning which serves as notice of the intended removal or change. This warning will be emitted for at least two releases, after which the removal or change may occur without further warning. This is different from Django's own deprecation policy, which avoids completing a removal/change in "LTS"-designated releases. Since django-registration does not have "LTS" releases, it does not need that

... (truncated)

Commits

• ee9458a Release 5.2.1.
• fdec00d Release 5.2.0.
• 9502b84 Merge pull request #253 from rafsaf/fix_pl_translation
• 906912a use more gender-neutral language in few phrases
• 2fd922d add missing translations for PL
• 9c42ebf Add label to activation-key form field. Refs #250.
• a397174 Restore nox to test dependency group.
• 60ef7e5 Bump version to make it clear we're in 5.1.1 prerelease.
• 9033b91 Add regression checks on email validator.
• d217015 Revert since now RTD is picking up the 5.1.0 tag.
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[ndittren]

@dependabot rebase

[nikolas]

@dependabot rebase