[Build/CI Change] Publish to test pypi during the release workflow #44
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.
Change Description
This PR is addressing issue tickets:
#24
uw-ssec/codeuw#47
Solution Description
1. Publish to Test PyPI
I separated actions for building the package from the
deploy
job, making a shareable artifact between publishing jobs to PyPI and Test PyPI.2. Check PyPI packages
Similar to the testing done in NoisePy. The changes in init.py are for retrieving the version number.
Code Quality
I've tested these changes using nektos/act locally and my own forked repo without errors.
Project-Specific Pull Request Checklists
Build/CI Change Checklist
A new token
TEST_PYPI_API_TOKEN
is needed to add to the repo.