feat: package for PyPI (pipx/uvx install + Trusted Publishing)#5
Merged
Conversation
Make the proxy installable as a published package, not just from source: - Add a tag-triggered Release workflow that builds the sdist + wheel, runs twine check, and publishes to PyPI via OIDC Trusted Publishing (no API token stored as a secret). - Single-source the version from vertex_proxy/__init__.py via hatchling dynamic versioning; pyproject and the running app's version both read from it, so a release is a one-line bump. Bump to 0.2.0. - README: lead the install section with pipx / uv / uvx, keep the from-source path for development; run examples use the on-PATH command. - CONTRIBUTING: add a "Releasing" section with the one-time Trusted Publisher setup and the per-release steps. - CHANGELOG: cut the 0.2.0 release section.
…tion Align the package's PyPI keywords with the repo's GitHub topics for discoverability, and note the OpenAI-compat route in the description (it was already a first-class route, just not mentioned here).
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
1 participant
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.
Makes vertex-proxy installable as a published package, so users can
pipx install vertex-proxyinstead of cloning. Per the maintainer's call, this targets PyPI only (no Homebrew, no curl|bash).What's in here
.github/workflows/release.yml): on av*tag, builds sdist + wheel, runstwine check, and publishes to PyPI via OIDC Trusted Publishing (no API token stored as a secret).vertex_proxy/__init__.pyis now the one source of truth (hatchling dynamic version);pyproject.tomland the running app'sversionboth read from it. Bumped to 0.2.0.pipx install vertex-proxy(plusuv tool install/uvx); from-source kept for development; run examples use the on-PATHvertex-proxycommand.0.2.0section.Build verified locally:
python -m buildproducesvertex_proxy-0.2.0(sdist + wheel),twine checkpasses, app reports version0.2.0. Suite: 22 passed, ruff clean.Action required before this delivers value (maintainer)
This PR is intentionally not auto-merged because publishing depends on a one-time account action only you can do, and on release timing.
vertex-proxy· Owner:prasadus92· Repo:vertex-proxy· Workflow:release.yml· Environment:pypipypito gate the publish job.git tag v0.2.0 && git push origin v0.2.0→ the workflow builds and publishes.Note: the README advertises
pipx install vertex-proxy, so it's best to merge and tag close together (the package won't resolve on PyPI until the first publish in step 4).