Bump django-registration from 3.4 to 5.1.0

[dependabot]

Bumps django-registration from 3.4 to 5.1.0.

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

• b0a2e49 Release 5.1.0.
• c6c389c Add contributing guide.
• a85a848 More documentation updates.
• 4ee9804 Fix documentation spelling wordlist.
• 51bac30 Documentation updates.
• ae9b366 Rework CI/RTD dependencies.
• dc00718 Revert to GH upload-artifact.
• a1f3928 Adjust CI config.
• 224f79f Switch tests to HTTPStatus enum for status codes.
• f0710ac CI: Install full dependencies for pylint.
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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