Skip to content

Fix #251: Correct return type for next_version() #254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
May 13, 2020
Merged

Fix #251: Correct return type for next_version() #254

merged 19 commits into from
May 13, 2020

Conversation

tlaferriere
Copy link
Contributor

@tomschr if you could take a look that would be appreciated.

@tlaferriere
Copy link
Contributor Author

PS: you might want to squash these commits since I merged newer changes from the repo into my old fork

@tomschr
Copy link
Member

tomschr commented May 13, 2020

@tlaferriere haha, we had the same idea. 😄 I've created #255.

There is one thing you could improve: Could you copy the CHANGELOG from my PR? You should also adapt the PR number to this. Other than that, it looks ok.

I will squash the commits later.

@tlaferriere
Copy link
Contributor Author

I was just about to do that

@tomschr tomschr merged commit f55559a into python-semver:master May 13, 2020
@tomschr tomschr added the Bug Error, flaw or fault to produce incorrect or unexpected results label May 13, 2020
@tomschr tomschr linked an issue May 13, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Error, flaw or fault to produce incorrect or unexpected results
Projects
None yet
Development

Successfully merging this pull request may close these issues.

VersionInfo.next_version() returns Union[VersionInfo, str]
2 participants