fix: Bugs with suggest in pre-releases #167
Merged
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
If everything that would trigger a micro up-date in a preview will actually increment the pre-release. Example: 0.8.0.a2.dev17 will become 0.8.0a2 and 0.8.0.a2 will become 0.8.0a3
It should be a modifier not a modified
A minor change in a pre-release will update alpha to beta or beta to beta or rc to rc.
The next development version is set
Update notification was not implemented
The next release will be an alpha release
The formatting had issues including the type-checking which needed to be fixed
Moved branches to extra functions and internalized module internal methods to class
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.
-> The next release will be an alpha release