Skip to content

[pull] main from django:main #481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pull merged 1 commit into from
Jul 2, 2026
+4 −3
Merged

[pull] main from django:main #481

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/internals/howto-release-django.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,8 @@ There are a lot of details, so please read on.
populates a lot of boilerplate you will need for announcements, CVE
publication, and hashes for commit messages. By using this app for preparing
security issue metadata, your peer releasers can check your entries and
consult them again in the future.
(`Example <https://www.djangoproject.com/checklists/release/5.2.4/>`_)
consult them again in the future. See `example checklist
<https://www.djangoproject.com/checklists/release/5.2.4/>`_.

Prerequisites
=============
Expand Down Expand Up @@ -742,7 +742,8 @@ You're almost done! All that's left to do now is:
#. Process the older versions that will reach End-Of-Mainstream and/or
End-Of-Life support when this final release is published:

#. Ensure that the EOL versions are mentioned in the blog post. `Example
#. Ensure that the EOL versions are mentioned in the blog post. See
`example announcement
<https://www.djangoproject.com/weblog/2025/apr/02/django-52-released/>`_.

#. Create a tag for the EOL stable branch and delete the stable branch.
Expand Down
Loading