Bump version in pyproject toml to avoid metadata clash with file version #836
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
|
@JoostJM do you think I'm on the right track with this, or is there a lot more involved in the versioning and meta-data? |
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.
A few of the issues ( #831 and #828 ) posted appear to have root cause in the metadata clash with the package publish/file version.
This is an attempt at resolving that by updating the version value in the pyproject.toml file.
There may be other causes: poetry complains about pep-517 compliance.
reverted some of my own commits so that this only alters pyproject.toml and leaves the versioner changes to the CI/CD (if that's how things work). there were build failures because of changes made by versioneer (and I don't have pre-commit hooks set up that match the CI expectations).
The published version claims 3.1.0, so the next valid semantic version is 3.1.1