feat: Use bump2version to make new release tags #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Running `bump2version <part>` will automatically produce a commit and a tag of the new version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To try to reduce some of the workflow confusion that PR #69 caused, this PR assumes that maintainers will use
bump2versionto make a release tag and adds a.bumpversion.cfgfile that enables committing changes and tagging the commit with the new version tag (equivalent of adding--commitand--tagat the CLI API).This PR also adds instructions to walk a maintainer through a release process.
@marceloprates I've left this PR in draft status and have it with parent of 77b992e rather than the current project HEAD so that I can rebase it after whatever actions you take RE: our discussion in #69 (comment). I'm of course happy to elaborate or revise any part of this PR! 👍