Oct 14, 2023 · Oct 13, 2023 · Oct 13, 2023 · Oct 13, 2023
diff --git a/README.md b/README.md

 ### How to make a new release

 - Update/verify the **version** in the `VERSION` file.
 - Update/verify that the `doc/source/changes.rst` changelog file was updated.
 - Commit everything.
 - Run `git tag -s <version>` to tag the version in Git.
 - _Optionally_ create and activate a [virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment) using `venv` or `virtualenv`.\
 (When run in a virtual environment, the next step will automatically take care of installing `build` and `twine` in it.)
 - Run `make release`.
 - Close the milestone mentioned in the _changelog_ and create a new one. _Do not reuse milestones by renaming them_.
 - Go to [GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.
 1. Update/verify the **version** in the `VERSION` file.
 2. Update/verify that the `doc/source/changes.rst` changelog file was updated. It should include a link to the forthcoming release page: `https://github.com/gitpython-developers/GitPython/releases/tag/<version>`
 3. Commit everything.
 4. Run `git tag -s <version>` to tag the version in Git.
 5. _Optionally_ create and activate a [virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment). (Then the next step can install `build` and `twine`.)
 6. Run `make release`.
 7. Go to [GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.

 ### How to verify a release (DEPRECATED)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -198,15 +198,13 @@ Please have a look at the [contributions file][contributing].

		### How to make a new release

		- Update/verify the version in the `VERSION` file.
		- Update/verify that the `doc/source/changes.rst` changelog file was updated.
		- Commit everything.
		- Run `git tag -s <version>` to tag the version in Git.
		- _Optionally_ create and activate a [virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment) using `venv` or `virtualenv`.\
		(When run in a virtual environment, the next step will automatically take care of installing `build` and `twine` in it.)
		- Run `make release`.
		- Close the milestone mentioned in the _changelog_ and create a new one. _Do not reuse milestones by renaming them_.
		- Go to [GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.
		1. Update/verify the version in the `VERSION` file.
		2. Update/verify that the `doc/source/changes.rst` changelog file was updated. It should include a link to the forthcoming release page: `https://github.com/gitpython-developers/GitPython/releases/tag/<version>`
		3. Commit everything.
		4. Run `git tag -s <version>` to tag the version in Git.
		5. _Optionally_ create and activate a [virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment). (Then the next step can install `build` and `twine`.)
		6. Run `make release`.
		7. Go to [GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.

		### How to verify a release (DEPRECATED)

Expand Down