ci: publish Python SDK to PyPI from release.yml - #718
Conversation
|
45d4139 to
40fe29e
Compare
5d649c4 to
76eaebd
Compare
77f4438 to
bb91545
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 72a75ae. Configure here.
72a75ae to
da05efc
Compare

Summary
Closes #
Changes
How was this tested?
Checklist
pnpm build,pnpm test,pnpm typecheck,pnpm lint:ci, andpnpm format:checkpass locallypackages/trueforge-sdk,.github/fern/openapi/openapi.json,docs/openapi.json) — fork PRs omit SDK regen; maintainers regenerate after merge.env.exampleupdated if configuration or behavior changedNote
Medium Risk
Changes release automation and adds a new PyPI publish path; misconfiguration could block releases or publish wrong versions, though npm/chart gates are unchanged and PyPI skips existing versions.
Overview
Adds PyPI publishing for
trueforge-sdkon the same Changesets-driven Release workflow as npm, using a newpublish-pythonjob (OIDC viapypa/gh-action-pypi-publish, skip-if-already-on-PyPI check, build withpython -m build).Version lockstep:
scripts/version.mjsnow copies@truefoundry/trueforge-sdk’s version intopython/trueforge_sdk/pyproject.toml, regenerates both Fern SDKs, and stages the Python tree;generate-sdk.sh/ SDK regen comments reflect that Python tracks TS on Version Packages (no separate Python changeset in bot regen).Docs:
RELEASING.mddocuments PyPI triggers, mirroring, trusted publishing setup, and troubleshooting.The diff also bumps OpenAPI/SDK metadata to
0.2.0-rc.7(OpenAPI) /0.2.0-rc.4(Python package literals from regen)—artifact/version alignment from the regen path, not new API surface in this PR.Reviewed by Cursor Bugbot for commit 0599f93. Bugbot is set up for automated code reviews on this repo. Configure here.