Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 03:37 UTC
| 1 | # SDK release notes |
| 2 | |
| 3 | Include a Changeset when a PR changes published SDK behavior. Use `pnpm changeset` |
| 4 | and select each affected TypeScript package or `@composio/python-sdk` for Python. |
| 5 | One note can cover both SDKs. Recommend `patch`, `minor`, or `major` and describe the |
| 6 | user-visible change. Python core and all supported providers release together. |
| 7 | The private Python marker is versioned by Changesets and never published to npm. |
| 8 | The CLI uses its own release process and must not appear in SDK Changesets. |
| 9 | |
| 10 | Docs, tests, internal tooling and CLI-only changes need no SDK note. If a change |
| 11 | under SDK source has no public effect, explain it in the PR description: |
| 12 | |
| 13 | ```html |
| 14 | <!-- sdk-release-note-exempt: Explain why this change has no published behavior. --> |
| 15 | ``` |
| 16 | |
| 17 | The SDK release issue form prepares one release PR from protected `next`. A writer |
| 18 | who did not request the release approves its final head after the candidate checks |
| 19 | pass, and a person merges it. See `ts/docs/internal/release.md`. |