Skip to content

fix(history): require semver >= 2.10 #297

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 1 commit into from
Dec 20, 2020

Conversation

wyardley
Copy link
Contributor

This resolves deprecation warnings, and updates this to a more 3.x compatible syntax

This resolves deprecation warnings, and updates this to a more 3.x
compatible syntax
@wyardley
Copy link
Contributor Author

wyardley commented Dec 19, 2020

Don't think this needs to be breaking, since the dependency is updated in setup.py?

If this is not conservative enough, feel free to close - this just resolves a deprecation warning observed when running tests.

I couldn't get the getattr() approach to work with this, but (assuming next_version() satisfies the intent, which it seems to, I think this actually reads a little easier.

@relekang relekang merged commit 5087e54 into python-semantic-release:master Dec 20, 2020
@wyardley
Copy link
Contributor Author

error: can only concatenate str (not "VersionInfo") to str

sorry, that CI failure is likely from this. Let me take a look

@wyardley wyardley deleted the wyardley-semver branch December 20, 2020 17:16
wyardley added a commit to wyardley/python-semantic-release that referenced this pull request Dec 20, 2020
The changes in python-semantic-release#297 mistakenly omitted coercing the return value to a
string. This resulted in errors like:
"can only concatenate str (not "VersionInfo") to str"
wyardley added a commit to wyardley/python-semantic-release that referenced this pull request Dec 20, 2020
The changes in python-semantic-release#297 mistakenly omitted coercing the return value to a
string. This resulted in errors like:
"can only concatenate str (not "VersionInfo") to str"

Add test case asserting it's type str
danth pushed a commit that referenced this pull request Dec 21, 2020
The changes in #297 mistakenly omitted coercing the return value to a
string. This resulted in errors like:
"can only concatenate str (not "VersionInfo") to str"

Add test case asserting it's type str
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants