diff options
| author | Alex Gaynor <alex.gaynor@gmail.com> | 2023-04-26 09:21:39 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-26 08:21:39 -0500 |
| commit | 9d06775cb1db57ea4389dfeb95e9657d926cb81b (patch) | |
| tree | 9ee960e148bbc7d93b7113829012532d8e150d54 /docs | |
| parent | d78ecb8dc1095ae9101d32671183d7a9bed13acd (diff) | |
| download | cryptography-9d06775cb1db57ea4389dfeb95e9657d926cb81b.tar.gz | |
Automate the version bump (#8828)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/doing-a-release.rst | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/doing-a-release.rst b/docs/doing-a-release.rst index c1571226e..48e253ea4 100644 --- a/docs/doing-a-release.rst +++ b/docs/doing-a-release.rst @@ -40,8 +40,7 @@ Bumping the version number The next step in doing a release is bumping the version number in the software. -* Update the version number in ``src/cryptography/__about__.py``. -* Update the version number in ``vectors/cryptography_vectors/__about__.py``. +* Run ``python release.py bump-version {new_version}`` * Set the release date in the :doc:`/changelog`. * Do a commit indicating this. * Send a pull request with this. @@ -54,7 +53,7 @@ The commit that merged the version number bump is now the official release commit for this release. You will need to have ``gpg`` installed and a ``gpg`` key in order to do a release. Once this has happened: -* Run ``python release.py {version}``. +* Run ``python release.py release {version}``. The release should now be available on PyPI and a tag should be available in the repository. |