Update README release commands to sign release tags #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor improvements from my experience releasing omero-py 5.7.0.
A second minor is that if the previous dev version does not match the expected release version (in my case
5.6.3.dev0
was released as5.7.0
), the default command will obviously create an undesired tag/commit. Options are either:bumpversion --no-tag [major|minor|patch]
.bumpversion.cfg
using `bumpversion release --current-version/--new-versionNo strong preference either way but if people have a inclination towards either of these options, I can certainly add a sentence to the README as part of this PR