Skip to content

ci: publish Python SDK to PyPI from release.yml - #718

Open
bhaveshpatel640 wants to merge 15 commits into
AGE-2005from
release-AGE-2005
Open

ci: publish Python SDK to PyPI from release.yml#718
bhaveshpatel640 wants to merge 15 commits into
AGE-2005from
release-AGE-2005

Conversation

@bhaveshpatel640

@bhaveshpatel640 bhaveshpatel640 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Closes #

Changes

How was this tested?

Checklist

  • I have read the contributing guidelines
  • pnpm build, pnpm test, pnpm typecheck, pnpm lint:ci, and pnpm format:check pass locally
  • Tests added/updated where it makes sense
  • No hand-edits to generated code (packages/trueforge-sdk, .github/fern/openapi/openapi.json, docs/openapi.json) — fork PRs omit SDK regen; maintainers regenerate after merge
  • Docs / .env.example updated if configuration or behavior changed

Note

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-sdk on the same Changesets-driven Release workflow as npm, using a new publish-python job (OIDC via pypa/gh-action-pypi-publish, skip-if-already-on-PyPI check, build with python -m build).

Version lockstep: scripts/version.mjs now copies @truefoundry/trueforge-sdk’s version into python/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.md documents 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.

@changeset-bot

changeset-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0599f93

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale Bugbot comment from a previous run.

Comment thread scripts/version.mjs
Comment thread .github/workflows/release.yml
@bhaveshpatel640
bhaveshpatel640 marked this pull request as draft September 11, 2026 15:36
@bhaveshpatel640
bhaveshpatel640 marked this pull request as ready for review September 11, 2026 16:03
@bhaveshpatel640
bhaveshpatel640 force-pushed the release-AGE-2005 branch 3 times, most recently from 45d4139 to 40fe29e Compare September 11, 2026 16:56
@bhaveshpatel640
bhaveshpatel640 force-pushed the release-AGE-2005 branch 3 times, most recently from 77f4438 to bb91545 Compare September 11, 2026 19:55

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ 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.

Comment thread python/trueforge_sdk/pyproject.toml
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.

2 participants