You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cladetime is working as intended when installed via GitHub. Thus, publishing the package to PyPI isn't required, but it's a good goal and lends legitimacy to the work.
Definition of done
Cladetime is available for install on PyPI
The Cladetime repo has a GitHub action that automates publishing releases to PyPI
More than one person in the Reich Lab has a PyPI account and is added as a Cladetime package owner
All docs with Cladetime install instructions are updated
The text was updated successfully, but these errors were encountered:
Will be adding a series of comments to document the process of publishing to PyPI as we learn about it (so we have some artifacts and notes when it's time to incorporate PyPI info into the Hubverse dev docs).
First set of process notes:
We will use a combination of GitHub actions + PyPI trusted publisher to automate the process of pushing a release to PyPI
Prerequisites for the above:
Create an environment in the package's GitHub repo. This environment name will be used when setting up a trusted publisher on PyPI. PyPI requires that deployments be manually approved when publishing via GitHub. Accomplish this by adding a deployment protection rule to the environment.
This PR adds setuptools_scm to Cladetime...a handy tool for automatically versioning Python packages (including feature branches) in a way that complies with PEP 440 #84
Background
Cladetime is working as intended when installed via GitHub. Thus, publishing the package to PyPI isn't required, but it's a good goal and lends legitimacy to the work.
Definition of done
The text was updated successfully, but these errors were encountered: