Bump version to v0.8.0 #45
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
|
Relevant to #37 |
|
Going to give this a go right now. I've only ever done it by pushing a tag I'm not positive that creating a tag via GitHub will trigger the publish action I also suspect the publish action is outdated |
|
As I suspected the action did not run, though publishing the release and adding tag here did trigger it. I will update the workflow to the modern standard |
|
Thanks @sstucker, and hope you are well!! |
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.
I am not entirely sure of the release procedure here. But from looking at the code, I think if we bump the version number, then make a new tag, it should cut a new pypi release.
Wasn't sure if this should be a minor or major change, so I went with the safer option and went the larger one.