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

ci: add workflow to automatically release to PyPI and GitHub #100

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

felix-seifert
Copy link
Collaborator

  • This workflow gets automatically triggered on any tag push if the tag starts with v*.
  • This workflow builds and deploys the lib to PyPI with Twine.
  • After a successful deployment to PyPI, the workflow calls another workflow to issue a GitHub release.

* This workflow gets automatically triggered on any tag push if the tag starts with `v*`.
* This workflow builds and deploys the lib to PyPI with Twine.
* After a successful deployment to PyPI, the workflow calls another workflow to issue a GitHub release.
@felix-seifert
Copy link
Collaborator Author

As mentioned in the discussions, the release workflow requires PyPI credentials. @csgoh Can you please persist the relevant secrets PYPI_USERNAME and PYPI_PASSWORD to make the needed credentials available to the release workflow?

Copy link
Owner

@csgoh csgoh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@felix-seifert I have added PYPI_USERNAME and PYPI_PASSWORD to repo secret

@csgoh csgoh merged commit db4205c into csgoh:main Mar 18, 2024
11 checks passed
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.

2 participants