Publish

Publishing a new version

Publication to PyPI is automated via GitHub actions and triggered via merging to the main branch

Please make sure the example notebooks used for documentation are up-to-date, since they are deployed as-is.

Bugfix releases

• Have a PR into main for which
  • The bugfix number of the __version__ string in xplt/__init__.py is incremented
  • CI passes
• Merge the PR 🚀
• Update the GitHub release of the associated minor revision to point to the new tag and include a note on the fix

Minor and major releases

• Have a PR into main for which
  • The minor or major number of the __version__ string in xplt/__init__.py is incremented
  • CI passes
• Create a branch main-* from main for future bug fixing of the previous version (e.g. main-1.2 when releasing 1.3.0)
• Merge the PR 🚀
• Create a GitHub release documenting the changes and additions to the previous version

Information

🚀 Merging a PR into main will trigger CI to do the following:

• CI creates a matching tag via the Release trigger workflow
  ⚠ This automatism is temporarily disabled, please trigger it manually or create a matching tag manually or via a GitHub release
• CI builds and publishes the package to test.pypi.org
• CI builds the documentation and pushes it to the gh-pages branch, from where it is published on GitHub Pages
• CI publishes the package to pypi.org