-
Notifications
You must be signed in to change notification settings - Fork 94
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] Publish to PyPI upon Tag #121
Conversation
@benjaminye we don't have the right to add secrets, so this is going to be blocked for now |
@truskovskiyk, I can add repo-scoped secrets for this repo that I created: https://github.com/georgian-io/cohere-rerank-eval. Seems like you need to be the owner of the repo to be able to do this. @RohitSaha please confirm if this guide works for you: https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository |
This PR introduces CI pipeline for PyPI. Addresses #114, #106.
What does this PR do?
Establish
git tags
as single source of truth for package releases and versioningWorkflow is triggered when
gh release create --repo seanh/gha-python-packaging-demo --generate-notes 0.0.1
Dynamic versioning and version convention (Semver) enforcement via poetry plugin
tag
will be replacing values found withinpyproject.toml
as well as in any__init__.py
files (i.e. where we do__version__='0.0.0'
).Requirement
PYPI_API_TOKEN
with a (preferably) scoped PyPI API Token.