Skip to content

Release workflow: mverify 0.1.0 to PyPI - #15

Open
scorvec wants to merge 1 commit into
mainfrom
claude/pypi-release
Open

scorvec wants to merge 1 commit into
mainfrom
claude/pypi-release

Conversation

@scorvec

@scorvec scorvec commented Oct 29, 2026

Copy link
Copy Markdown
Owner

Gets pip install "mverify[all]" working from PyPI.

  • release.yml (new): on every package change it builds the sdist and wheel, then checks them: twine check --strict, the 512-character summary limit PyPI enforces (twine doesn't check it), and the wheel's mverify command in a clean environment. A published GitHub release vX.Y.Z also uploads them to PyPI by Trusted Publishing (environment pypi, no stored token), after checking that the tag matches the package version.
  • Version: 0.1.0, set only in mverify.__version__ (pyproject reads it).
  • Metadata: SPDX licence, classifiers (Alpha, Python 3.11-3.13), keywords, links to the design notes, issues and the live scores on scorvec.com.
  • README: installs from PyPI; CI, PyPI and licence badges; absolute links to DESIGN.md so they work on the PyPI page.

After merging: a PyPI pending publisher (project mverify, owner scorvec, repository nwp_verification, workflow release.yml, environment pypi), then a v0.1.0 release.

🤖 Generated with Claude Code

release.yml builds and checks the sdist and wheel on every package change and
uploads a published GitHub release to PyPI. The version has one source
(mverify.__version__); the metadata gains an SPDX licence, classifiers and
project links, and the README installs from PyPI with absolute links that
render there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant