From 2b300f8c846c4bba4c8e76129848abdc71e110b9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Bidoul?= Date: Sun, 26 Jan 2025 15:47:12 +0100 Subject: [PATCH] Update the release process docs To mention the required approval step. --- docs/html/development/release-process.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/html/development/release-process.rst b/docs/html/development/release-process.rst index 77ee9b5d46b..8b56c5e3a8f 100644 --- a/docs/html/development/release-process.rst +++ b/docs/html/development/release-process.rst @@ -147,7 +147,12 @@ Creating a new release #. Submit the ``release/YY.N`` branch as a pull request and ensure CI passes. Merge the changes back into ``main`` and pull them back locally. #. Push the tag created by ``prepare-release``. This will trigger the release - workflow on GitHub and publish to PyPI. + workflow on GitHub. +#. Go to https://github.com/pypa/pip/actions, find the latest ``Publish Python + 🐍 distribution 📦 to PyPI`` workflow run, open it, wait for the build step + to complete, then approve the PyPI environment to let the publishing step + run. If you desire, you have the possibility to download and inspect the + artifacts before approving. #. Regenerate the ``get-pip.py`` script in the `get-pip repository`_ (as documented there) and commit the results. #. Submit a Pull Request to `CPython`_ adding the new version of pip