Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Release the Python SDK
Request a stable Python release through the shared SDK release procedure. Every active ComposioHQ member can use the release issue form. Leave Python at auto to follow the changesets, or select a patch, minor, or major override. Set TypeScript to skip for a Python-only release.
Public Python SDK/provider changes include a changeset targeting the private @composio/python-sdk marker. Core and supported providers form one stable train. The bot updates the version mirrors and uv.lock and opens one release PR. Its SDK candidate (python) check builds the wheels and sdists; SDK candidate smoke (python) installs them in a clean venv and tests the new core with the latest published providers. A repository writer other than the PR author approves the head, and a person merges it. If you requested the release, your approval counts only while you have repository admin permission. The tag run publishes those exact files through the tag-only pypi-release identity.
If publishing fails, choose Re-run failed jobs on the tag run within 30 days of the candidate build. After that, add a changeset for @composio/python-sdk and request a new release; the train moves to the next version. If the merged release was never tagged, follow the recovery table in the SDK release procedure.
For local packaging checks, run from python/:
make build
The release pipeline installs locked build tools from the root workspace's release dependency group and builds with BUILD_ARGS=--no-isolation. Update generated-client pins only after verifying that the client version exists, and regenerate uv.lock with uv.
The legacy py.release.yml keeps build-only dispatch and core-prerelease publishing. Stable releases use the shared workflow rather than manual version bumps or py@ tags.