Some minor changes so that the publish to PyPI only happens "on release." In order to test, "regular" PyPI upload is commented out, and publish to "test PyPI" is active. Will change after next release.
Related Issue
Would close #77 and #78
How Has This Been Tested?
It has not. The plan is to put this in place. When we are ready to cut the next release, we use the GitHub Release mechanism to do so, which should trigger this workflow. This workflow will only publish to Test PyPI, but that will be the test. Since the workflow in "test mode" doesn't publish, that release will need to be manually twine-ed up to PyPI (but should be the last time). If the test works, then we can comment out the Test-PyPI and have "regular" PyPI publish enabled for the release after that.
Types of changes
New feature (non-breaking change which adds functionality)
I claim copyrights on my contributions in this pull request, and I provide those contributions via this pull request under the same license terms that the pvl project uses.
Description
Some minor changes so that the publish to PyPI only happens "on release." In order to test, "regular" PyPI upload is commented out, and publish to "test PyPI" is active. Will change after next release.
Related Issue
Would close #77 and #78
How Has This Been Tested?
It has not. The plan is to put this in place. When we are ready to cut the next release, we use the GitHub Release mechanism to do so, which should trigger this workflow. This workflow will only publish to Test PyPI, but that will be the test. Since the workflow in "test mode" doesn't publish, that release will need to be manually twine-ed up to PyPI (but should be the last time). If the test works, then we can comment out the Test-PyPI and have "regular" PyPI publish enabled for the release after that.
Types of changes
Checklist:
Licensing:
This project is released under the LICENSE.