The process of setup.py using the latest Github release to determine the version of this package isn't correct. We should be managing the version separately. This only works if you are on master and have a strict version/release/tag based on that. Any other branch or PR is going to have a different version.
We need a process to manage versions separate from Github. In Python, there are a number of strategies, mostly involving storing it in a file and regexing it out.
Then, we can invert the logic - we change the version somewhere, and that triggers a new release, whether against master, develop, or some other branch.
The process of
setup.pyusing the latest Github release to determine the version of this package isn't correct. We should be managing the version separately. This only works if you are onmasterand have a strict version/release/tag based on that. Any other branch or PR is going to have a different version.We need a process to manage versions separate from Github. In Python, there are a number of strategies, mostly involving storing it in a file and regexing it out.
Then, we can invert the logic - we change the version somewhere, and that triggers a new release, whether against
master,develop, or some other branch.