Give up on 2.1.2 tag/release. Prepare for a 2.1.3 release #18
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
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.
Doing a 2.1.2 release to PyPI at this point is getting problematic as it would/could not match the v2.1.2 tag on Github.
This PR prepares for a 2.1.3 release. After merging this, and doing a v2.1.3 release through github, the upload to pypi should proceed automatically, if not it can be done manually.
In future should be updated to use
scm_versionor something so we can do version number management purely through the github release mechanism. Nobody wants to have to remember to update version numbers in multiple places.