Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Build/CI Change] Publish to test pypi during the release workflow #44

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

hinxcode
Copy link

@hinxcode hinxcode commented Jul 14, 2024

Change Description

  • My PR includes a link to the issue that I am addressing

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 have read the Contribution Guide
  • My code follows the code style of this project
  • My code builds (or compiles) cleanly without any errors or warnings
  • My code contains relevant comments and necessary documentation

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

  • If required or optional dependencies have changed (including version numbers), I have updated the README to reflect this
  • If this is a new CI setup, I have added the associated badge to the README

A new token TEST_PYPI_API_TOKEN is needed to add to the repo.

@hinxcode hinxcode changed the title [Build/CI Change] Publish to test pypi during the release workflow #24 [Build/CI Change] Publish to test pypi during the release workflow Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant