Publishing

The workspace uses release-please, GitHub Releases, and PyPI trusted publishing. The root workspace is not published. extended-data and pytest-extended-data are released from their package paths.

Local Gates

tox -e lint,typecheck,audit,py311,py312,py313,py314,examples,docs,build

The build gate checks both wheels and source archives for private runtime state, generated documentation caches, and machine paths. Source archives select package source, tests, examples where present, and package metadata explicitly; the public documentation site lives under the workspace's root docs/ directory. Workspace-only archive-gate tests stay in the repository because their verifier is workspace tooling. Runtime tests remain in the source archive. Machine-path checks cover macOS, Linux home/root directories, and Windows user directories; documentation placeholders such as <user> remain valid.

After building, the archive check can also run directly:

python scripts/verify_distributions.py dist/extended-data dist/pytest-extended-data

Release Flow

1. Merge feature, fix, docs, and maintenance commits to main.
2. release.yml runs release-please and opens or updates package release PRs.
3. Merge the release PR.
4. release-please creates the GitHub release and version tag.
5. release.yml dispatches cd.yml with the release tag and package name.
6. cd.yml publishes the selected package to PyPI with OIDC trusted publishing. extended-data releases also build and deploy the Sourcey site.

PyPI Trusted Publishers

Each published package needs a PyPI trusted publisher matching the workflow that uploads it. Both extended-data and pytest-extended-data publish through the standard cd.yml workflow. If a new package needs an initial PyPI pending publisher, use these values before rerunning CD:

After the pending publisher exists, rerun the failed publish with:

gh workflow run cd.yml --ref main -f tag=pytest-extended-data-v0.1.0 -f package=pytest-extended-data

Package-scoped release-please configuration owns package versions, package changelogs, release tags, and the release manifest. Do not add the root uv.lock as a package extra-files target; normal uv sync setup can refresh the workspace lock locally, while package builds publish from each package's committed metadata.

Manual tags and manual PyPI uploads are repair paths, not the normal release process.