Add PyPI packaging metadata and a Trusted Publishing release workflow#274
Merged
Conversation
The project shipped as a bare name/version with no publishing path. Fill in the distribution metadata (readme, SPDX license, classifiers, keywords, project URLs) and add a release workflow so tagging cuts a real PyPI release. - pyproject: PEP 639 license (`license = "MIT"` + `license-files`), readme, classifiers, keywords, and [project.urls]. Pin the build backend to setuptools>=77 so the emitted Metadata-2.4 (License-Expression / License-File) validates cleanly under `twine check` and modern PyPI. - .github/workflows/release.yml: on a `v*` tag (or manual dispatch), build the sdist+wheel, assert the tag matches the package version, run `twine check`, capture `pyisolate-doctor` provenance, and upload the artifacts. A separate publish job uploads via PyPI Trusted Publishing (OIDC, no stored token), gated on the `pypi` GitHub Environment so it stays a no-op until a maintainer wires the publisher up. - Document the release flow in docs/packaging-reproducibility.md and ignore the local dist/ and build/ output. Verified `python -m build` + `twine check` pass on both distributions in a clean environment. Full suite: 449 passed, 4 skipped. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PbbJc7Ntj159D9LNGevwC2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The project shipped as a bare name/version with no publishing path. Fill in the distribution metadata (readme, SPDX license, classifiers, keywords, project URLs) and add a release workflow so tagging cuts a real PyPI release.
license = "MIT"+license-files), readme, classifiers, keywords, and [project.urls]. Pin the build backend to setuptools>=77 so the emitted Metadata-2.4 (License-Expression / License-File) validates cleanly undertwine checkand modern PyPI.v*tag (or manual dispatch), build the sdist+wheel, assert the tag matches the package version, runtwine check, capturepyisolate-doctorprovenance, and upload the artifacts. A separate publish job uploads via PyPI Trusted Publishing (OIDC, no stored token), gated on thepypiGitHub Environment so it stays a no-op until a maintainer wires the publisher up.Verified
python -m build+twine checkpass on both distributions in a clean environment. Full suite: 449 passed, 4 skipped.Claude-Session: https://claude.ai/code/session_01PbbJc7Ntj159D9LNGevwC2