11**************************
2- SiPANN 2.0.0
2+ SiPANN 2.0.1
33**************************
44.. image :: https://img.shields.io/pypi/v/SiPANN.svg
55 :target: https://pypi.python.org/pypi/SiPANN
@@ -95,8 +95,8 @@ Bibtex citation
9595 Releasing
9696=========
9797
98- Make sure you have committed a changelog file titled
99- "[major].[minor].[patch]-changelog.md" before bumping version.
98+ Make sure you have committed a changelog file titled
99+ "[major].[minor].[patch]-changelog.md" before bumping version.
100100
101101To bump version prior to a release, run one of the following commands:
102102
@@ -106,11 +106,11 @@ To bump version prior to a release, run one of the following commands:
106106 bumpversion minor
107107 bumpversion patch
108108
109- This will automatically create a git tag in the repository with the
109+ This will automatically create a git tag in the repository with the
110110corrresponding version number and commit the modified files (where version
111- numbers were updated). Pushing the tags (a manual process) to the remote will
112- automatically create a new release. Releases are automatically published to
113- PyPI and GitHub when git tags matching the "v*" pattern are created
111+ numbers were updated). Pushing the tags (a manual process) to the remote will
112+ automatically create a new release. Releases are automatically published to
113+ PyPI and GitHub when git tags matching the "v*" pattern are created
114114(e.g. "v0.2.1"), as bumpversion does.
115115
116116To view the tags on the local machine, run :code: `git tag `. To push the tags to
0 commit comments