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

Dokumen ini menjelaskan bagaimana menerbitkan Django.

**Harap, jaga petunjuk-petunjuk ini terbaru jika anda membuat perubahan!** Titiknya disini adalah menjadi lebih menggambarkan, bukan memberi petunjuk, jadi silahkan untuk mempersingkat atau jika tidak buat perubahan, tetapi **perbaharui dokumen ini sesuai dengan itu!**

## Ikhtisar

Terdapat tiga jenis terbitan yang anda mungkin butuh untuk dibuat:

- Terbitan keamanan: mengungkap dan memperbaiki kerentanan. Ini umumnya melibatkan dua atau lebih terbitan beruntun -- misalnya 3.2.x, 4.0.x, dan, tergatung dari waktu, mungkin 4.1.x.
- Terbitan versi umum: salah satu terbitan akhir (misalnya 4.1) atau pembaharuan perbaikan kesalahan (misalnya 4.1.1).
- Pra-terbitan: misalnya 4.2 alpha, beta, atau rc.

Versi pendek dari langkah-langkah bersangkutan adalah:

1. Jika ini adalah terbitan keamanan, beritahu daftar penyebaran keamanan satu minggu sebelum terbitan sebenarnya.
2. Proofread catatan terbitan, menacri kesalahan organisasi dan penulisan. Konsep sebuah penempatan blog dan pengumuman surel.
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. Veridikasi tanda tangan paket, periksa jika mereka dapat dipasang, dan dan pastikan kegunaan minimal.
6. Unggah versi terbaru ke PyPI.
7. Enable the `is_active` flag for each release in the admin on
   `djangoproject.com`.
8. Tempatkan masukan blog dan kirim pengumuman surel.
9. Update version numbers post-release in stable branch(es).
10. Add stub release notes for the next patch release in `main` and backport.

Ada banyak rincian, jadi silahkan lanjutkan membaca.

> **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/).

## Prasyarat

You'll need a few things before getting started. If this is your first release,
you'll need to coordinate with another releaser to get all these things lined
up, and write to the Ops mailing list requesting the required access and
permissions.

- Lingkungan Unix dengan alat alat ini terpasang (dalam urutan abjad):

  - bash
  - git
  - GPG
  - membuat
  - pria
  - alat hashing (typically `md5sum`, `sha1sum`, dan `sha256sum` pada Linux, atau `md5` dan `shasum` pada macOS)
  - python
- A GPG key pair. Ensure that the private part of this key is securely stored.
  The public part needs to be uploaded to your GitHub account, and also to the
  Jenkins server running the "confirm release" job.

  > **Lebih dari satu kunci GPG**
  >
  > If the key you want to use is not your default signing key, you'll need to
  > add `-u you@example.com` to every GPG signing command shown below, where
  > `you@example.com` is the email address associated with the key you want
  > to use.
- A clean Python virtual environment (Python 3.9+) to build artifacts, with
  these required Python packages installed:

  ```shell
  $ python -m pip install build twine
  ```
- 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. Create a project-scoped 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
  ```
- Access to the Django admin on `djangoproject.com` as a "Site maintainer".
- 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.
- Access to the `django-security` repo in GitHub. Among other things, this
  provides access to the pre-notification distribution list (needed for
  security release preparation tasks).
- Access to the Django project on [Read the Docs](https://readthedocs.org/projects/django/).

## Tugas-tugas pra terbitan

A few items need to be taken care of before even beginning the release process.
This stuff starts about a week before the release; most of it can be done
any time leading up to the actual release.

### 10 (atau lebih) hari sebelum terbitan keamanan

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. Generate the relevant (private) patch(es) using `git format-patch`, one
   for the `main` branch and one for each stable branch being patched.

### Seminggu sebelum terbitan keamanan

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. [Notify django-announce](/id/6.0/internals/security/#security-disclosure) dari terbitan keamanan yang akan datang dengan pesan umum seperti:

   ```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

### Beberapa hari sebelum terbitan

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. Check with the other mergers to make sure they don't have any uncommitted
   changes for the release.
3. Proofread the release notes, including looking at the online version to
   [catch any broken links](/id/6.0/internals/contributing/writing-documentation/#documentation-link-check) or reST errors, and
   make sure the release notes contain the correct date.
4. Periksa kembali itu catatan terbitan menyebutkan linimasa pengusangan untuk setiap API dicatat sebagai diusangkan, dan mereka menyebut bahwa tiap perubahan di Python versi dukungan.
5. Periksa kembali itu catatan terbitan index mempunyai sebuah tautan ke catatan untuk terbitan baru; ini akan ada di `docs/releases/index.txt`.
6. If this is a [feature release](/id/6.0/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.

   This command takes some time to run. When done, carefully inspect the output
   for potential errors and/or warnings. If there are some, you will need to
   debug and resolve them on a case by case basis.

   The recently fetched translations need some manual adjusting. First of all,
   the `PO-Revision-Date` values must be manually bumped to be later than
   `POT-Creation-Date`. You can use a command similar to this to bulk update
   all the `.po` files (compare the diff against the relevant stable branch):

   ```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. [Update the django-admin manual page](/id/6.0/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
   ```

   dan kemudian perbaiki perubahan halaman panduan.
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. Tulis penempatan blog pengumuman untuk terbitan. Anda dapat memasukkannya kedalam admin kapan pun dan menandainya sebagai tidak aktif. Ini adalah beberapa contoh: [example security release announcement](https://www.djangoproject.com/weblog/2013/feb/19/security/), [example regular release announcement](https://www.djangoproject.com/weblog/2012/mar/23/14/), [example pre-release announcement](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. Perbaharui `VERSION` tuple di `django/__init__.py`, menaik ke terbitan yang diharapkan selanjutnya ([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. 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.

## Sebenarnya menggulir terbitan

OK, this is the fun part, where we actually push out a release! If you're
issuing **multiple releases**, repeat these steps for each release.

1. Check [Jenkins](https://djangoci.com) is green for the version(s) you're putting out. You
   probably shouldn't issue a release until it's green, and you should make
   sure that the latest green run includes the changes that you are releasing.
2. Cleanup the release notes for this release. Make these changes in `main`
   and backport to all branches where the release notes for a particular
   version are located.

   1. For a feature release, remove the `UNDER DEVELOPMENT` header at the top
      of the release notes, remove the `Expected` prefix and update the
      release date, if necessary ([example commit](https://github.com/django/django/commit/1994a2643881a9e3f9fa8d3e0794c1a9933a1831)).
   2. For a patch release, remove the `Expected` prefix and update the
      release date for all releases, if necessary ([example commit](https://github.com/django/django/commit/34a503162fe222033a1cd3249bccad014fcd1d20)).
3. A release always begins from a release branch, so you should make sure
   you're on an up-to-date stable branch. Also, you should have available a
   clean and dedicated virtual environment per version being released. For
   example:

   ```shell
   $ git checkout stable/4.1.x
   $ git pull
   ```
4. If this is a security release, merge the appropriate patches from
   `django-security`. Rebase these patches as necessary to make each one a
   plain commit on the release branch rather than a merge commit. To ensure
   this, merge them with the `--ff-only` flag; for example:

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

   (This assumes `security/4.1.x` is a branch in the `django-security` repo
   containing the necessary security patches for the next release in the 4.1
   series.)

   If git refuses to merge with `--ff-only`, switch to the security-patch
   branch and rebase it on the branch you are about to merge it into (`git
   checkout security/4.1.x; git rebase stable/4.1.x`) and then switch back and
   do the merge. Make sure the commit message for each security fix explains
   that the commit is a security fix and that an announcement will follow
   ([example security commit](https://github.com/django/django/commit/bf39978a53f117ca02e9a0c78b76664a41a54745)).
5. Angka versi pembaharuan di `django/__init__.py` untuk terbitan. Silahkan lihat [notes on setting the VERSION tuple](#notes-on-setting-the-version-tuple) dibawah untuk rincian pada `VERSION` ([example commit](https://github.com/django/django/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. Sebaliknya, pastikan penggolong disetel ke `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. Etiket terbitan menggunakan `git tag`. Sebagai contoh:

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

   Anda dapat memeriksa pekerjaan berjalan anda `git tag --verify <tag>`.
2. Pastikan anda mempunyai pohon sepenuhnya bersih dengan menjalankan `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. For
   Django 5.0 or older, you need to run `make -f extras/Makefile` instead.
4. Bangkitkan hash dari paket terbitan:

   ```shell
   $ cd dist
   $ md5sum *
   $ sha1sum *
   $ sha256sum *
   ```
5. Create a "checksums" file, `Django-<<VERSION>>.checksum.txt` containing
   the hashes and release information. Start with this template and insert the
   correct version, date, GPG key ID (from
   `gpg --list-keys --keyid-format LONG`), release manager's GitHub username,
   release URL, and checksums:

   ```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. Tandatangi berkas checksum (`gpg --clearsign --digest-algo SHA256 Django-<version>.checksum.txt`). Ini membangkitkan dokumen ditandatangi, `Django-<version>.checksum.txt.asc` yang anda dapat kemudian memeriksa menggunakan `gpg --verify Django-<version>.checksum.txt.asc`.

## Membuat terbitan tesedia ke umum

Sekarang anda siap benar-benar menaruh terbitan diluar sana. Untuk melakukan ini:

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:

   **Versi**

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

   **Aktif**

     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.

   **Tanggal**

     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. Jalankan bangun [confirm-release](https://djangoci.com/job/confirm-release/) pada Jenkins untuk verifikasi berkas checksum (misalnya gunakan `4.2rc1` untuk <https://media.djangoproject.com/pgp/Django-4.2rc1.checksum.txt>).
4. Upload the release packages to PyPI:

   ```shell
   $ twine upload --repository django dist/*
   ```
5. Update the newly created `Release` in the admin in `djangoproject.com`
   and enable the `is_active` flag.
6. Dorong pekerjaan anda dan tambah etiket baru:

   ```shell
   $ git push
   $ git push --tags
   ```
7. Buat blog menempatkan pengumuman terbitan langsung.
8. Untuk terbitan versi baru (misalnya 4.1, 4.2), perbaharui versi stabil awal dari dokumen dengan membalikkan bendera `is_default` menjadi `True` pada obyek `DocumentRelease` yang sesuai di basisdata `docs.djangoproject.com` (ini akan otomatis menggantinya menjadi `False` untuk semua lainnya); anda dapat melakukan ini menggunakan admin situs.

   Create new `DocumentRelease` objects for each language that has an entry
   for the previous release. Update djangoproject.com's [robots.docs.txt](https://github.com/django/djangoproject.com/blob/main/djangoproject/static/robots.docs.txt)
   file by copying the result generated from running the command
   `manage_translations.py robots_txt` in the current stable branch from the
   [django-docs-translations repository](https://github.com/django/django-docs-translations). For example, when releasing Django
   4.2:

   ```shell
   $ git checkout stable/4.2.x
   $ git pull
   $ python manage_translations.py robots_txt
   ```
9. Post the release announcement to the [django-announce](/id/6.0/internals/mailing-lists/#django-announce-mailing-list) mailing list and the
   Django Forum. This should include a link to the announcement blog post.
10. 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>
    ```
11. 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.

## Pasca-terbitan

Anda hampir selesai! Semua yang tersisa untuk dilakukan sekarang adalah:

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. Jika ini adalah terbitan akhir:

   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. Perbaharui halaman unduh ([example 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. Jika ini adalah terbitan keamanan, perbaharui [Arsip dari masalah keamanan](/id/6.0/releases/security/) dengan rincian dari masalah-masalah yang dialamatkan.
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=djangojs --domain=django
      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).

## Catatan pada pengaturan tuple VERSION

Pelaporan versi Django dikendalikan oleh tuple `VERSION` di `django/__init__.py`. Ini adalah lima-unsur tuple, yang unsurnya adalah:

1. Versi utama.
2. Versi kecil.
3. Versi mikro.
4. Keadaan -- dapat menjadi satu dari "alpha", "beta", "rc" atau "final".
5. Rangkaian angka, untuk paket alpha/beta/RC yang berjalan dalam urutan (mengizinkan, sebagai contoh, "beta 1", "beta 2", etc.).

Untuk terbitan akhir, keadaan selalu "final" dan rangkaian angka selalu 0. Rangkaian angka dari 0 dengan keadaan "alpha" akan dilaporkan sebagai "pre-alpha".

Beberapa contoh:

- `(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"