Versioning update #387
Merged
Versioning update #387
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
😄
janosh
reviewed
May 16, 2024
|
|
||
| [tool.versioningit.vcs] | ||
| default-tag = "0.0.1" | ||
| method = "git" |
There was a problem hiding this comment.
It uses tags to set the version:
https://pypi.org/project/versioningit/0.3.3/
|
OK, if I break things on PyPI I promise I'll fix ASAP! |
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.
Address a few problems with the CI:
Modified
./pytest-docs.ymlLooks like the docs build has been failing for some time due to upstream package changes.
Modified the build pipeline to make sure tests pass
Automatic Versioning and release
With the new setup, you should just do a release on GitHub and the release workflow will automatically trigger.
I cannot test this without merging into main and affecting Pypi so I want to make sure this is reviewed.