chore: manage the package entirely with uv - #78
Merged
Merged
Conversation
GClunies
changed the title
Replace twine upload with uv publish, remove the build dev dependency that uv build superseded, and drop the egg-info cleanup that only mattered for pip editable installs. twine stays for the metadata check in CI.
GClunies
force-pushed
the
chore/envrc-uv-sync
branch
from
September 18, 2026 22:01
4d123b3 to
aa24659
Compare
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.
What
Remove the last pip-era tooling so uv owns the whole package lifecycle: environment, editable install, build, and publish.
.envrc)pip show/pip install -e ".[dev]"guarduv syncmake install-devrm -rf *.egg-infoworkaround for pip installsuv syncmake submit/ release workflowtwine uploaduv publishbuild,twineuv buildanduv publishreplace them)uv build+twine checkuv build+ wheel-content assertsWhy
The project already used
uv.lock,[dependency-groups], anduv runeverywhere. The remaining pip and twine references were leftovers that pulled in a dozen transitive dependencies and could recreate staleegg-infometadata that shadowed the uv-managed install.twine checkonly validated README rendering for PyPI. The README is Markdown with the content type set by hatchling, so the check always passed. The wheel-content asserts are the part that catches real packaging regressions.Verified
uv syncinstalls snowcap editable (uv pip show snowcapreports the repo as the editable location).make packagebuilds the sdist and wheel.uv publish --helpconfirmsUV_PUBLISH_USERNAME/UV_PUBLISH_PASSWORD. The release workflow maps the existing PyPI secrets to them.