Skip to content

ci(release): add stable Python SDK release PR flow#451

Open
Abhijeet Prasad (AbhiPrasad) wants to merge 1 commit into
mainfrom
abhi-feat-stable-release-workflow
Open

ci(release): add stable Python SDK release PR flow#451
Abhijeet Prasad (AbhiPrasad) wants to merge 1 commit into
mainfrom
abhi-feat-stable-release-workflow

Conversation

@AbhiPrasad
Copy link
Copy Markdown
Member

@AbhiPrasad Abhijeet Prasad (AbhiPrasad) commented May 20, 2026

resolves https://linear.app/braintrustdata/issue/BT-5169/set-up-publish-workflow-environment-rules-for-python-sdk

Add a GitHub Actions driven stable release path that creates a version-bump PR from the Prepare Stable Python SDK Release workflow. Merging the release/py-sdk-v PR now triggers Publish Python SDK directly, so tagging and publishing live in one release workflow instead of a separate tag workflow.

Gate only stable, non-dry-run PyPI publishes with the pypi-publish environment so the job that calls trusted publishing receives the protected environment context. After approval, the publish workflow builds, publishes to PyPI, and creates the py-sdk-v GitHub Release tag and release.

Prereleases continue to use the manual Publish Python SDK workflow without environment approval or a committed version bump; the requested prerelease version is supplied as a workflow input and applied as a build override. Update the release validator and docs for the new process.

Add a GitHub Actions driven stable release path that creates a version-bump PR from the Prepare Stable Python SDK Release workflow. Merging the release/py-sdk-v<version> PR now triggers Publish Python SDK directly, so tagging and publishing live in one release workflow instead of a separate tag workflow.

Gate only stable, non-dry-run PyPI publishes with the pypi-publish environment so the job that calls trusted publishing receives the protected environment context. After approval, the publish workflow builds, publishes to PyPI, and creates the py-sdk-v<version> GitHub Release tag and release.

Prereleases continue to use the manual Publish Python SDK workflow without environment approval or a committed version bump; the requested prerelease version is supplied as a workflow input and applied as a build override. Update the release validator and docs for the new process.
@AbhiPrasad Abhijeet Prasad (AbhiPrasad) force-pushed the abhi-feat-stable-release-workflow branch from 90e42e8 to 743aadf Compare May 20, 2026 19: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.

2 participants