weco-datascience releases

[harrisonpim]

Proposed workflow:

• make a bunch of changes in the weco_datascience directory
• set a new version manually in the package init.py
• PR them, merge them into master.
• create a new release, tagged with a new semantic version. any release notes etc added through the same interface. /tags serves as the changelog.
• workflow at .github/workflows/publish.yml is triggered by the new release, which
  • installs flit
  • lints the package
  • runs its tests
  • builds the package binary
  • publishes it to pypi

[harrisonpim]

still need to add a set of PYPI_USERNAME and PYPI_PASSWORD secrets to the repo/organisation, or authorise https://pypi.org/user/wellcomedigitalplatform/ as a maintainer on the package

[jamieparkinson]

Think we should go for publishing it under wellcomedigitalplatform to match our other packages

[harrisonpim]

wellcomedigitalplatform secrets added to repo and authorised as an owner of the package on pypi. Should be ready to go afaict?