Skip to content

Pypi publish - #88

Merged
ShantanuKodgirwar merged 2 commits into
mainfrom
pypi-publish
Jul 29, 2026
Merged

Pypi publish#88
ShantanuKodgirwar merged 2 commits into
mainfrom
pypi-publish

Conversation

@ShantanuKodgirwar

Copy link
Copy Markdown
Contributor

No description provided.

ShantanuKodgirwar and others added 2 commits July 29, 2026 14:04
Publish releases to PyPI from CI using OIDC trusted publishing, which
needs no repository secret or GitHub Environment — the trust config
lives entirely on pypi.org. Triggered by publishing a GitHub Release.

A tag/version guard fails the build before upload if the release tag
does not match pyproject.toml, since PyPI rejects re-uploads of a
version permanently.

Point install instructions at PyPI, keeping git+https documented for
the unreleased state of main. The static version badge is replaced by
a dynamic PyPI badge so pyproject.toml is the only source of truth for
the version, and README links are absolutised so they resolve in the
PyPI long description.

Also widen the uv_build bound to <0.12; the stale upper bound warned
on every build against current uv.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ShantanuKodgirwar
ShantanuKodgirwar merged commit 83656f2 into main Jul 29, 2026
3 checks passed
@ShantanuKodgirwar
ShantanuKodgirwar deleted the pypi-publish branch July 29, 2026 12:09
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