Publishing
Documentation
Section titled “Documentation”The Docs workflow builds the site on every push and pull request to main and devel. It
executes the tutorials, generates the API reference and uploads the site. Pushes to devel
also deploy it to GitHub Pages at https://max-models.github.io/mpiarray/.
Enable GitHub Pages once in the repository settings, with “GitHub Actions” as the source.
Releases and PyPI
Section titled “Releases and PyPI”Before merging a release to main, update the version in pyproject.toml,
src/mpiarray/__init__.py and CITATION.cff (including its release date), and add the release
notes to CHANGELOG.md. On
every push to main, the Release workflow:
- tags the release
vX.Y.Zand creates the GitHub release, - builds the package with
uv buildand publishes it to PyPI with trusted publishing (OIDC), if that version is not already on PyPI.
One-time configuration
Section titled “One-time configuration”- Create an account on PyPI and create or claim your project name.
- In the PyPI project settings go to “Publishing” → “Add a new publisher” and fill in:
- PyPI project name:
mpiarray(or your project name) - Owner: your GitHub username or organization
- Repository name:
mpiarray - Workflow name:
release.yml - Environment name:
pypi
- PyPI project name:
- Optionally, in the GitHub repository settings create an environment named
pypiwhose deployment branches are limited tomain.
Coverage
Section titled “Coverage”The tests upload coverage to Codecov. Public repositories need no
configuration; for a private one add a CODECOV_TOKEN repository secret.