---
title: "How to release Django"
version: 6.1
locale: zh-hans
source: https://docs.djangoproject.com/zh-hans/6.1/internals/howto-release-django/
canonical: https://djangodocs.dev/zh-hans/6.1/internals/howto-release-django/
---
# How to release Django

这份文档解释了如何发布 Django。

**请在进行更改时保持这些说明的最新状态！** 这里的重点是描述性的，而不是规范性的，所以请随意简化或进行其他更改，但 **相应地更新这份文档！**

## 概况

有三种类型的发布可能需要进行：

- 安全性发布：揭示和修复漏洞。这通常涉及到两个或三个同时发布的版本，例如 3.2.x、4.0.x，根据时间的安排，可能还包括 4.1.x。
- 常规版本发布：可以是最终发布（例如 4.1）或错误修复更新（例如 4.1.1）。
- 预发布版本：例如 4.2 alpha、beta 或 rc。

涉及的步骤的简短版本是：

1. 如果这是一个安全性发布，请在实际发布前一周预先通知安全性发布列表。
2. 校对发布说明，查找组织和写作错误。起草一篇博客文章和电子邮件公告。
3. Update version numbers and create the release artifacts.
4. Create the new `Release` in the admin on `djangoproject.com`.

   1. Set the proper date but ensure the flag `is_active` is disabled.
   2. Upload the artifacts (tarball, wheel, and checksums).
5. 验证包的签名，检查它们是否可以安装，并确保最小功能可用。
6. 将新版本上传到 PyPI。
7. Enable the `is_active` flag for each release in the admin on
   `djangoproject.com`.
8. 发布博客文章并发送电子邮件公告。
9. Update version numbers post-release in stable branch(es).
10. Add stub release notes for the next patch release in `main` and backport.

有很多细节，请继续阅读。

> **Use the checklists app**
>
> To generate a checklist compiling the tasks described below as relevant to
> the specific release(s) you are issuing, use the checklists app in the
> [project admin](https://www.djangoproject.com/admin/checklists/). This
> 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. See [example checklist](https://www.djangoproject.com/checklists/release/5.2.4/).

## 先决条件

在开始之前，你需要准备一些东西。如果这是你第一次发布，你需要与另一位发布者协调，确保所有事项都准备妥当，并写信给 Ops 邮件列表，请求所需的访问权限和许可。

- 一个安装了以下工具的 Unix 环境（按字母顺序排列）：

  - bash (version 4.0+)
  - git
  - GPG
  - make
  - man
  - 哈希工具（通常在 Linux 上是 `md5sum`、`sha1sum` 和 `sha256sum`，在 macOS 上是 `md5` 和 `shasum`）
  - python
- A GPG key pair. Securely store the private part, and protect it with a
  passphrase. The public part needs to be uploaded to your GitHub account.

  > **多个 GPG 密钥**
  >
  > 如果你想使用的密钥不是你的默认签名密钥，你需要在下面显示的每个 GPG 签名命令中添加 `-u you@example.com`，其中 `you@example.com` 是与你想要使用的密钥关联的电子邮件地址。
- A clean Python virtual environment (Python 3.10+, pip 26.1+) to build
  artifacts.
- Access to [Django's project on PyPI](https://pypi.org/project/Django/) to
  upload binaries, ideally with extra permissions to [yank a release](https://pypi.org/help/#yanked) if necessary. Ensure your PyPI account
  only uses WebAuthn-based authentication factors, not TOTP (one-time codes).
  Create an API token following the [official documentation](https://pypi.org/help/#apitoken), and set up your `$HOME/.pypirc` file
  like this:

  *`~/.pypirc`*

  ```ini
  [distutils]
    index-servers =
      pypi
      django

  [pypi]
    username = __token__
    password = # User-scoped or project-scoped token, to set as the default.

  [django]
    repository = https://upload.pypi.org/legacy/
    username = __token__
    password = # A project token.
  ```
- Access to [Django's project on Transifex](https://app.transifex.com/django/django/), with a Manager role. Generate
  an API Token in the [user setting section](https://app.transifex.com/user/settings/api/) and set up your
  `$HOME/.transifexrc` file like this:

  *`~/.transifexrc`*

  ```ini
  [https://www.transifex.com]
    rest_hostname = https://rest.api.transifex.com
    token = # API token
  ```
- 作为“站点维护者”访问 `djangoproject.com` 上的 Django 管理界面。
- Access to create a post in the [Django Forum - Announcements category](https://forum.djangoproject.com/c/announcements/7) and to send emails to
  the [django-announce](https://groups.google.com/g/django-announce/)
  mailing list.
- 访问 GitHub 中的 `django-security` 仓库。除其他事项外，这提供了对预通知分发列表的访问权限（安全发布准备任务所需）。
- Access to the Django project on [Read the Docs](https://readthedocs.org/projects/django/).

## 发布前的任务

在开始发布过程之前，需要处理一些事项。这些工作大约在发布前一周开始；大部分工作可以在实际发布前的任何时间完成。

### 安全发布前 10 天（或更早）

1. Reserve one [CVE ID](https://www.cve.org/About/Overview/) per security
   issue as follows. (Or, if you lack CNA credentials, email
   `cna@djangoproject.com` with a request.)

   - Enable virtual environment with [cvelib](https://pypi.org/project/cvelib/) installed.
   - Export user information:

     ```shell
     $ export CVE_USER=<user-email>@djangoproject.com CVE_ORG=DSF
     ```
   - Reserve:

     ```shell
     $ cve --interactive reserve <quantity>
     ```
2. 使用 `git format-patch` 生成相关的（私有）补丁，一个用于 `main` 分支，一个用于每个正在修补的稳定分支。

### 安全发布前一周

1. Send out pre-notification exactly **one week** before the security release.
   The template for that email and a list of the recipients are in the private
   `django-security` GitHub wiki. BCC the pre-notification recipients, and be
   sure to include the relevant CVE IDs. Attach all the relevant patches
   (targeting `main` and the stable branches), and sign the email text with
   the key you'll use for the release, with a command like:

   ```shell
   $ gpg --clearsign --digest-algo SHA256 prenotification-email.txt
   ```
2. [通知 django-announce](/zh-hans/6.1/internals/security/#security-disclosure) 即将发布的安全版本，使用如下一般消息：

   ```text
   Notice of upcoming Django security releases (3.2.24, 4.2.10 and 5.0.2)

   Django versions 5.0.2, 4.2.10, and 3.2.24 will be released on Tuesday,
   February 6th, 2024 around 1500 UTC. They will fix one security defect
   with severity "moderate".

   For details of severity levels, see:
   https://docs.djangoproject.com/en/dev/internals/security/#how-django-discloses-security-issues
   ```
3. Prepare issue metadata:
   \* Severity
   \* Short description
   \* Reporter
   \* Remediator
   \* Reported at
   \* Confirmed at (usually date CVE reserved)
   \* CWE Problem Type
   \* CAPEC Impact Type
   \* CVSS (4.0) Score & Vector

### 任何发布前几天

1. As the release approaches, watch Trac to make sure no release blockers are
   left for the upcoming release. Under exceptional circumstances, such as to
   meet a pre-determined security release date, a release could still go ahead
   with an open release blocker. The releaser is trusted with the decision to
   release with an open release blocker or to postpone the release date of a
   non-security release if required.
2. 与其他合并人员核对，确保他们没有为发布而提交的未提交更改。
3. 校对发布说明，包括查看在线版本以 [捕捉任何损坏的链接](/zh-hans/6.1/internals/contributing/writing-documentation/#documentation-link-check) 或 reST 错误，并确保发布说明包含正确的日期。
4. 再次确认发布说明中提到了任何已经标记为弃用的 API 的弃用时间表，并且提到了对 Python 版本支持的任何更改。
5. 再次检查发布说明索引中是否有指向新发布版本说明的链接；这将在 `docs/releases/index.txt` 中。
6. If this is a [feature release](/zh-hans/6.1/internals/release-process/#term-Feature-release), ensure translations from Transifex
   have been integrated.

   In addition to having a configured Transifex account, ensure that the [tx
   CLI](https://developers.transifex.com/docs/cli) is available in your
   `PATH`. You can then fetch all translations since a given date by running:

   ```shell
   $ python scripts/manage_translations.py fetch -v 1 --since=<some date>
   ```

   To determine a good value for `--since`, check the date of the most recent
   commit with wording similar to `Updated translations from Transifex` and
   use a date a few days prior.

   此命令需要一些时间运行。完成后，仔细检查输出以查找潜在的错误和/或警告。如果有，你需要逐个调试并解决它们。

   最近获取的翻译需要一些手动调整。首先，`PO-Revision-Date` 值必须手动更新为晚于 `POT-Creation-Date`。你可以使用类似于以下的命令批量更新所有 `.po` 文件（与相关稳定分支进行比较）：

   ```shell
   $ git diff --name-only stable/5.0.x | grep "\.po"  | xargs sed -ri "s/PO-Revision-Date: [0-9\-]+ /PO-Revision-Date: $(date -I) /g"
   ```

   Lastly, commit the changed/added files (both `.po` and `.mo`) and create
   a new PR targeting the stable branch of the corresponding release (example
   [PR updating translations for 4.2](https://github.com/django/django/pull/16715)).

   Once merged, forward port the changes into `main` ([example commit](https://github.com/django/django/commit/cb27e5b9c0703fb0edd70b2138e3e53a78c9551d)).
7. [更新 django-admin 手册页面](/zh-hans/6.1/internals/contributing/writing-documentation/#django-admin-manpage)：

   ```shell
   $ cd docs
   $ make man
   $ man _build/man/django-admin.1  # do a quick sanity check
   $ cp _build/man/django-admin.1 man/django-admin.1
   ```

   然后提交已更改的手册页面。
8. If this is the "dot zero" release of a new series, create a new branch from
   the current stable branch in the [django-docs-translations](https://github.com/django/django-docs-translations) repository. For
   example, when releasing Django 4.2:

   ```shell
   $ git checkout -b stable/4.2.x origin/stable/4.1.x
   $ git push origin stable/4.2.x:stable/4.2.x
   ```
9. 为发布撰写公告博客文章。你可以随时输入它到管理员界面并将其标记为非活动状态。以下是一些示例：[示例安全发布公告](https://www.djangoproject.com/weblog/2013/feb/19/security/)、[示例常规发布公告](https://www.djangoproject.com/weblog/2012/mar/23/14/)、[示例预发布公告](https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/)。

#### A few days before a feature freeze

In preparation for the alpha release, the directory
`/home/www/www/media/releases/A.B` must be created on the djangoproject
server.

Before the feature freeze, a branch targeting `main` must be created to
prepare for the next feature release. It should be reviewed and approved a few
days before the freeze, allowing it to be merged after the stable branch is
cut. The following items should be addressed in this branch:

1. Update the `VERSION` tuple in `django/__init__.py`, incrementing to the
   next expected release ([example commit](https://github.com/django/django/commit/96700c7b378c592f0b1732302c22af2fd2c87fc6)).
2. Create a stub release note for the next feature release. Use the stub from
   the previous feature release or copy the contents from the current version
   and delete most of the contents leaving only the headings
   ([example commit](https://github.com/django/django/commit/9b5ad4056ccf9ff7ea548f72d28eb66c1b4f84cc)).
3. Remove `.. versionadded::` and `.. versionchanged::` annotations in the
   documentation from two releases ago, as well as any remaining older
   annotations. For example, in Django 5.1, notes for 4.2 will be removed
   ([example commit](https://github.com/django/django/commit/9edb7833b89e811eefd94974fb987f4605b0c0d7)).
4. Remove features that have reached the end of their deprecation cycle,
   including their docs and the `.. deprecated::` annotation. Each removal
   should be done in a separate commit for clarity. In the commit message, add
   a `Refs #XXXXX --` prefix linking to the original ticket where the
   deprecation began if possible. Make sure this gets noted in the removed
   features section in the release notes ([example commit](https://github.com/django/django/commit/f2d9c76aa7096ef3eed675b9eb824858f9dd81e5)).
5. Advance the deprecation warnings ([example commit](https://github.com/django/django/commit/0c0bda7f79a2de89a55cfcc8e60467d6588f406f)).
6. Increase the default PBKDF2 iterations in
   `django.contrib.auth.hashers.PBKDF2PasswordHasher` by about 20%
   (pick a round number). Run the tests, and update the 3 failing
   hasher tests with the new values. Make sure this gets noted in the
   release notes ([example commit](https://github.com/django/django/commit/7288866da4dddf3705148c703421858ec19cdb78)).

Concrete examples for past feature release bootstrap branches: [5.2 bootstrap](https://github.com/django/django/pull/18127), [5.1 bootstrap](https://github.com/django/django/pull/17246), [5.0 bootstrap](https://github.com/django/django/pull/16432).

## Feature freeze tasks

1. Remove empty sections from the release notes ([example commit](https://github.com/django/django/commit/9e6e58bad237a80ddd5e3ab8b834cecdaad8455e)).
2. Build the release notes locally and read them. Make any necessary change
   to improve flow or fix grammar ([example commit](https://github.com/django/django/commit/435bdab93889dae01e71c79598edab10627cc1f9)).
3. Create a new stable branch from `main`. Be sure to fetch and update
   `upstream` to latest. For example, when feature freezing Django 5.2:

   ```shell
   $ git fetch upstream
   $ git checkout -b stable/5.2.x upstream/main
   $ git push upstream -u stable/5.2.x:stable/5.2.x
   ```

   At the same time, update the `django_next_version` variable in
   `docs/conf.py` on the stable release branch to point to the new
   development version. For example, when creating `stable/5.2.x`, set
   `django_next_version` to `'6.0'` on the new stable branch
   ([example commit](https://github.com/django/django/commit/1eb62e5b622ef7fd6e0123d8bbf6662d893d5d08)).
4. Create `Release` entries for the next version in the [admin](https://www.djangoproject.com/admin/releases/release/add/) on
   `djangoproject.com`. Add one for each milestone (alpha, beta, rc, and
   final), leaving *is active* unset to mark them as unreleased. Set target
   dates per the agreed schedule, and set the LTS flag if applicable. The
   `X.Y` roadmap page will be available at `/download/X.Y/roadmap/`.

   For example, when creating `stable/5.2.x`, add `Release` entries for
   `6.0a1`, `6.0b1`, `6.0rc1`, and `6.0`. The `6.0` roadmap can be
   then reviewed at <https://www.djangoproject.com/download/6.0/roadmap/>.
5. Go to the [Add document release page in the admin](https://www.djangoproject.com/admin/docs/documentrelease/add/), create a new
   `DocumentRelease` object for the English language for the newly created
   `Release` object. Do not mark this as default.
6. Add the new branch to [Read the Docs](https://readthedocs.org/projects/django/). Since the automatically
   generated version names ("stable-A.B.x") differ from the version names used
   in Read the Docs ("A.B.x"), update the Read the Docs config for the version
   to point to the slug `A.B.x` and set it as active. [See more details](https://github.com/readthedocs/readthedocs.org/issues/12483).
7. [Create a PR on PyPI proposing the new Trove classifier](https://github.com/pypa/trove-classifiers/pulls?q=is%3Apr+django+trove+classifier).
   For example `Framework :: Django :: 5.2`.
8. Update the current branch under active development and add pre-release
   branch in the [Django release process](https://code.djangoproject.com/#Djangoreleaseprocess) on Trac.
9. Update the `docs/fixtures/doc_releases.json` JSON fixture for
   djangoproject.com, so people without access to the production DB can still
   run an up-to-date copy of the docs site
   ([example PR](https://github.com/django/djangoproject.com/pull/1446)).
   This will be merged after the final release.

## 实际发布版本

好的，这是有趣的部分，我们实际上要发布一个版本！如果你要发布 **多个版本**，请为每个版本重复这些步骤。

1. 检查 [Jenkins](https://djangoci.com) 是否为你要发布的版本显示绿色。在它变绿之前，你可能不应该发布版本，并且你应该确保最新的绿色运行包括你要发布的更改。
2. 清理此版本的发布说明。在 `main` 中进行这些更改，并向后移植到特定版本发布说明所在的所有分支。

   1. 对于功能发布，删除发布说明顶部的 `UNDER DEVELOPMENT` 标题，删除 `Expected` 前缀，并在必要时更新发布日期（[示例提交](https://github.com/django/django/commit/1994a2643881a9e3f9fa8d3e0794c1a9933a1831)）。
   2. 对于补丁发布，删除所有版本的 `Expected` 前缀，并在必要时更新发布日期（[示例提交](https://github.com/django/django/commit/34a503162fe222033a1cd3249bccad014fcd1d20)）。
3. Regenerate a fresh, dedicated virtual environment for the release tools
   using a cooldown:

   ```shell
   $ python -m pip install build twine --uploaded-prior-to=P7D
   ```
4. A release always begins from a release branch, so you should make sure
   you're on an up-to-date stable branch. For example:

   ```shell
   $ git checkout stable/4.1.x
   $ git pull
   ```
5. 如果这是一个安全发布，请从 `django-security` 合并适当的补丁。根据需要重新基于这些补丁，使每个补丁都成为发布分支上的普通提交，而不是合并提交。为了确保这一点，使用 `--ff-only` 标志合并它们，例如：

   ```shell
   $ git checkout stable/4.1.x
   $ git merge --ff-only security/4.1.x
   ```

   （这假设 `security/4.1.x` 是 `django-security` 存储库中包含下一个 4.1 系列发布所需的安全补丁的分支。）

   如果 git 拒绝使用 `--ff-only` 合并，请切换到 security-patch 分支，并在你将要合并的分支上重新基于它（`git checkout security/4.1.x; git rebase stable/4.1.x`），然后切换回来并执行合并操作。确保每个安全修复的提交消息解释了这个提交是一个安全修复，并且会有一个公告随后发布（[示例安全提交](https://github.com/django/django/commit/bf39978a53f117ca02e9a0c78b76664a41a54745)）。
6. 在 `django/__init__.py` 中更新发布版本的版本号。有关 `VERSION` 的详细信息，请参阅下面的 设置 VERSION 元组的注意事项\`\_（:commit:\`示例提交 \<2719a7f8c161233f45d34b624a9df9392c86cc1b\>）。

   1. If this is a pre-release package also update the "Development Status"
      trove classifier in `pyproject.toml` to reflect this. An `rc`
      pre-release should not change the trove classifier ([example
      commit for alpha release](https://github.com/django/django/commit/759921c8e9ad151932fc913ab429fef0a6112ef8),
      [example commit for beta release](https://github.com/django/django/commit/25fec8940b24107e21314ab6616e18ce8dec1c1c)).
   2. 否则，确保分类器设置为 `Development Status :: 5 - Production/Stable`。

### Building the artifacts

> **Optionally use helper scripts**
>
> You can streamline some of the steps below using helper scripts from the
> `scripts` folder:
>
> - Release script example run:
>
> ```shell
> $ PGP_KEY_ID=<key-id> PGP_KEY_URL=<key-url> DEST_FOLDER=~/releases scripts/do_django_release.py
> ```
>
> - Verify the release (after artifacts were uploaded):
>
> ```shell
> $ VERSION=5.2.1 scripts/verify_release.sh
> ```

1. 使用 `git tag` 标记发布。例如：

   ```shell
   $ git tag --sign --message="Tag 4.1.1" 4.1.1
   ```

   你可以通过运行 `git tag --verify <tag>` 来检查你的工作。
2. 确保你的代码库是绝对干净的，通过运行 `git clean -dfx`。
3. Run `python -m build` to generate the release packages. This will create
   the release artifacts (tarball and wheel) in a `dist/` directory.
4. 生成发布包的哈希值：

   ```shell
   $ cd dist
   $ md5sum *
   $ sha1sum *
   $ sha256sum *
   ```
5. 创建一个名为 `Django-<<VERSION>>.checksum.txt` 的 "checksums" 文件，其中包含哈希值和发布信息。使用以下模板，并插入正确的版本、日期、GPG 密钥 ID（从 `gpg --list-keys --keyid-format LONG` 获取）、发布管理器的 GitHub 用户名、发布 URL 和哈希值：

   ```text
   This file contains MD5, SHA1, and SHA256 checksums for the source-code
   tarball and wheel files of Django <<VERSION>>, released <<DATE>>.

   To use this file, you will need a working install of PGP or other
   compatible public-key encryption software. You will also need to have
   the Django release manager's public key in your keyring. This key has
   the ID ``XXXXXXXXXXXXXXXX`` and can be imported from GitHub, for example,
   if using the open-source GNU Privacy Guard implementation of PGP:

       curl https://github.com/<<RELEASE MANAGER GITHUB USERNAME>>.gpg | gpg --import -

   Once the key is imported, verify this file:

       gpg --verify <<THIS FILENAME>>

   Once you have verified this file, you can use normal MD5, SHA1, or SHA256
   checksumming applications to generate the checksums of the Django
   package and compare them to the checksums listed below.

   Release packages
   ================

   https://www.djangoproject.com/download/<<VERSION>>/tarball/
   https://www.djangoproject.com/download/<<VERSION>>/wheel/

   MD5 checksums
   =============

   <<MD5SUM>>  <<RELEASE TAR.GZ FILENAME>>
   <<MD5SUM>>  <<RELEASE WHL FILENAME>>

   SHA1 checksums
   ==============

   <<SHA1SUM>>  <<RELEASE TAR.GZ FILENAME>>
   <<SHA1SUM>>  <<RELEASE WHL FILENAME>>

   SHA256 checksums
   ================

   <<SHA256SUM>>  <<RELEASE TAR.GZ FILENAME>>
   <<SHA256SUM>>  <<RELEASE WHL FILENAME>>
   ```
6. 签名 "checksum" 文件（`gpg --clearsign --digest-algo SHA256 Django-<version>.checksum.txt`）。这将生成一个已签名的文档，`Django-<version>.checksum.txt.asc`，你可以使用 `gpg --verify Django-<version>.checksum.txt.asc` 来验证它。

## 将发布版本提供给公众

现在，你准备好将发布版本发布出去了。为了做到这一点：

1. Create a new `Release` entry in the [djangoproject.com's admin](https://www.djangoproject.com/admin/releases/release/add/). If this is a
   security release, this should be done 15 minutes before the announced
   release time, no sooner:

   **版本**

     Must match the version number as defined in the tarball
     (`django-<version>.tar.gz`). For example: "5.2", "4.1.1", or "4.2rc1".

   **Is active**

     Set to False until the release is fully published (last step).

   **LTS**

     Enable if the release is part of an LTS (Long Term Support)
     branch.

   **Dates**

     Set the release date to today. This release will not be published until
     `is_active` is enabled.

   **Artifacts**

     Upload the tarball (`django-<version>.tar.gz`), wheel
     (`django-<version>-py3-none-any.whl`), and checksum
     (`django-<version>.checksum.txt.asc`) files created earlier.
2. Test that the release packages install correctly using `pip`. Here's one
   simple method (this just tests that the binaries are available, that they
   install correctly, and that migrations and the development server start, but
   it'll catch silly mistakes):
   <https://code.djangoproject.com/wiki/ReleaseTestNewVersion>.
3. 在 Jenkins 上运行 [confirm-release](https://djangoci.com/job/confirm-release/) 构建，以验证 checksum 文件（例如，对于 <https://media.djangoproject.com/pgp/Django-4.2rc1.checksum.txt>，使用 `4.2rc1`）。
4. Generate a new token for this release on PyPI, and store it in `.pypirc`
   as shown above.
5. Upload the release packages to PyPI:

   ```shell
   $ twine upload --repository django dist/*
   ```
6. On PyPI, revoke the token you just created.
7. Update the newly created `Release` in the admin in `djangoproject.com`
   and enable the `is_active` flag.
8. 推送你的工作和新标签：

   ```shell
   $ git push
   $ git push --tags
   ```
9. 发布公告发布的博客文章。
10. 对于新版本发布（例如 4.1、4.2），通过将 `docs.djangoproject.com` 数据库中适当的 `DocumentRelease` 对象上的 `is_default` 标志设置为 `True` 来更新文档的默认稳定版本（这将自动将其设置为 `False`，对于所有其他版本）；你可以使用站点的管理员界面来完成这个操作。

    为每种语言创建新的 `DocumentRelease` 对象，这些语言在之前的发布中有条目。通过从 [django-docs-translations 仓库](https://github.com/django/djangoproject.com/blob/main/djangoproject/static/robots.docs.txt) 的当前稳定分支运行命令 `manage_translations.py robots_txt` 生成的结果，更新 djangoproject.com 的 [robots.docs.txt](https://github.com/django/django-docs-translations) 文件。例如，当发布 Django 4.2 时：

    ```shell
    $ git checkout stable/4.2.x
    $ git pull
    $ python manage_translations.py robots_txt
    ```
11. Post the release announcement to the [django-announce](/zh-hans/6.1/internals/mailing-lists/#django-announce-mailing-list) mailing list and the
    Django Forum. This should include a link to the announcement blog post.
12. If this is a security release, publish the CVE metadata. (The
    [checklist app](#checklist-generator) generates JSON for this.):

    ```shell
    $ cve publish <cve-number> --cve-json-file <path-to-file>
    ```
13. If this is a security release, send a separate email to
    `oss-security@lists.openwall.com`. Provide "Django" plus the CVE IDs in
    the subject line. The message body should include the vulnerability details,
    for example, the announcement blog post text. Include a link to the
    announcement blog post.

## 发布后

你差不多完成了！现在剩下要做的只有：

1. If this is not a pre-release, update the `VERSION` tuple in
   `django/__init__.py` again, incrementing to whatever the next expected
   release will be. For example, after releasing 4.1.1, update `VERSION` to
   `VERSION = (4, 1, 2, 'alpha', 0)` ([example commit](https://github.com/django/django/commit/a4d19953d46247ee1992b3427fe652e941524272)).
2. If this was an alpha release:

   1. Add the feature release version in [Trac's versions list](https://code.djangoproject.com/admin/ticket/versions).
   2. Create a new security branch from the freshly cut stable branch. Be sure
      to fetch and update `upstream` to latest. For example, after the 5.2
      alpha release:

      ```shell
      $ git fetch upstream
      $ git checkout -b security/5.2.x upstream/stable/5.2.x
      $ git push origin -u security/5.2.x:security/5.2.x
      ```
3. 如果这是一个最终发布：

   1. Update the `default_version` setting in the code.djangoproject.com's
      `trac.ini` file ([example PR](https://github.com/django/code.djangoproject.com/pull/268)).
   2. Update the current stable branch and remove the pre-release branch in the
      [Django release process](https://code.djangoproject.com/#Djangoreleaseprocess) on Trac.
   3. 更新 djangoproject.com 的下载页面（[示例 PR](https://github.com/django/djangoproject.com/pull/1444)）。
   4. Process the older versions that will reach End-Of-Mainstream and/or
      End-Of-Life support when this final release is published:

      1. 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/).
      2. Create a tag for the EOL stable branch and delete the stable branch.
         Inspect and use the `scripts/archive_eol_stable_branches.py` helper.
4. 如果这是一个安全发布，请更新 [安全问题档案](/zh-hans/6.1/releases/security/)，提供解决问题的详细信息。
5. If this was a pre-release, the translation catalogs need to be updated:

   1. Make a new branch from the recently released stable branch:

      ```shell
      $ git checkout stable/A.B.x
      $ git checkout -b update-translations-catalog-A.B.x
      ```
   2. Ensure that the release's dedicated virtual environment is enabled and
      run the following:

      ```shell
      $ cd django
      $ django-admin makemessages -l en --domain=django
      processing locale en
      $ django-admin makemessages -l en --domain=djangojs
      processing locale en
      ```
   3. Make a pull request against the corresponding stable branch and merge
      once approved.
   4. Forward port the updated source translations to the `main` branch
      ([example commit](https://github.com/django/django/commit/aed303aff57ac990894b6354af001b0e8ea55f71)).
6. If this was an `alpha` pre-release, coordinate with the maintainer of
   [asgiref](https://pypi.org/project/asgiref/) to determine when to raise the minimum version before the
   final release. For the backport, add an upper bound on the next major
   version (example commits:
   [main](https://github.com/django/django/commit/df35cf578f99522dd1ba864d513be95d47bab7a5),
   [backport](https://github.com/django/django/commit/e5d2664908164d51d2daa46e375da8b6a93def03)).
7. If this was an `rc` pre-release, call for translations for the upcoming
   release in the [Django Forum - Internationalization category](https://forum.djangoproject.com/c/internals/i18n/14).

## 关于设置 VERSION 元组的注意事项

Django 的版本报告受控于 `django/__init__.py` 中的 `VERSION` 元组。这是一个包含五个元素的元组，其元素分别是：

1. 主要版本。
2. 次要版本。
3. 微版本。
4. 状态 -- 可以是 "alpha"、"beta"、"rc" 或 "final" 中的一个。
5. 系列号，用于按顺序运行的 alpha/beta/RC 包（例如，"beta 1"、"beta 2" 等）。

对于最终发布，状态始终为 "final"，系列号始终为 0。状态为 "alpha" 的系列号为 0 将被报告为 "pre-alpha"。

一些示例：

- `(4, 1, 1, "final", 0)` → "4.1.1"
- `(4, 2, 0, "alpha", 0)` → "4.2 pre-alpha"
- `(4, 2, 0, "beta", 1)` → "4.2 beta 1"