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, 06:00 UTC
chore(release): add Python notes and run the note check on every PR (#5259)
Alberto Schiabel committed
Nov 6, 2026 at 23:09 UTC
e970677aa69f4526009bb535a58d006ca7368e9a
6 files changed
+56
-21
.changeset/python-client-2-1-0.md
new
+5
@@ -0,0 +1,5 @@
1
+---
2
+'@composio/python-sdk': minor
3
+---
4
+
5
+Update `composio-client` to 2.1.0. Breaking (experimental API): `composio.experimental.custom_toolkits.create()` and `upsert()` take the MCP server URL as `mcp_url` instead of `app_url`.
.changeset/python-local-tools-rename.md
new
+5
@@ -0,0 +1,5 @@
1
+---
2
+'@composio/python-sdk': minor
3
+---
4
+
5
+Renames in-process custom tools to local tools, so they are no longer confused with the server-side custom toolkits on `composio.experimental.custom_toolkits`. Pass `experimental={"local_tools": ..., "local_toolkits": ...}` to `composio.create()`, and `local_tools=` and `local_toolkits=` to `composio.use()`. List them with `session.local_tools()` and `session.local_toolkits()`. The types are now `LocalTool`, `LocalToolkit`, `RegisteredLocalTool` and `RegisteredLocalToolkit`. The `custom_tools` and `custom_toolkits` options and session methods still work but emit `ComposioDeprecationWarning`, and the `Custom*` type names remain as aliases. Passing both a new option and its deprecated alias raises `InvalidParams`. The request sent to the API is unchanged.
.changeset/python-missing-api-key-message.md
new
+5
@@ -0,0 +1,5 @@
1
+---
2
+'@composio/python-sdk': patch
3
+---
4
+
5
+The error for a missing API key now explains how to set `COMPOSIO_API_KEY` or pass `api_key=`, and links to where to get a project API key, instead of suggesting `composio login`, which the Python package doesn't install.
.changeset/python-rate-limit-handling.md
new
+5
@@ -0,0 +1,5 @@
1
+---
2
+'@composio/python-sdk': minor
3
+---
4
+
5
+`wait_for_connection()` handles rate limits: the delay between polls grows from 1 to 5 seconds, and a poll rejected with a 429 waits as long as its `Retry-After` header asks (up to the timeout) and polls again instead of failing the wait. A NaN timeout now times out instead of polling forever.
.github/workflows/sdk.release.check.yml
+2
-21
@@ -3,8 +3,7 @@ name: SDK release checks
3
on:
4
pull_request:
5
branches: [next]
6
- # `edited` re-checks the release-note exemption when the PR description changes.
7
- types: [opened, synchronize, reopened, edited]
6
+ types: [opened, synchronize, reopened]
7
paths:
8
- '.changeset/**'
9
- 'python/**'
@@ -22,31 +21,13 @@ on:
21
permissions:
22
contents: read
23
25
-# Description edits only re-run the note check, so they must not cancel a code run's tooling.
24
concurrency:
27
- group: sdk-release-check-${{ github.ref }}-${{ github.event.action == 'edited' && 'description' || 'code' }}
25
+ group: sdk-release-check-${{ github.ref }}
26
cancel-in-progress: true
27
28
jobs:
31
- release-note:
32
- name: SDK release note
33
- runs-on: ubuntu-latest
34
- steps:
35
- - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
36
- with:
37
- fetch-depth: 0
38
- persist-credentials: false
39
- - uses: ./.github/actions/setup-node-pnpm-bun
40
- - run: pnpm install --frozen-lockfile --ignore-scripts
41
- - name: Require a changeset for published SDK behavior
42
- env:
43
- SDK_RELEASE_NOTE_BASE: ${{ github.event.pull_request.base.sha }}
44
- SDK_RELEASE_PR_BODY: ${{ github.event.pull_request.body }}
45
- run: pnpm validate:changesets
46
-
29
tooling:
30
name: SDK release tooling
49
- if: github.event.action != 'edited'
31
runs-on: ubuntu-latest
32
steps:
33
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
.github/workflows/sdk.release.note.yml
new
+34
@@ -0,0 +1,34 @@
1
+name: SDK release note
2
+
3
+# Runs on every PR to next, with no path filter, so `next` can require it: a check that a
4
+# path filter skips never reports, and a required one would then block the PR forever.
5
+# The validator passes PRs that don't change published SDK behavior.
6
+on:
7
+ pull_request:
8
+ branches: [next]
9
+ # `edited` re-checks the release-note exemption when the PR description changes.
10
+ types: [opened, synchronize, reopened, edited]
11
+
12
+permissions:
13
+ contents: read
14
+
15
+concurrency:
16
+ group: sdk-release-note-${{ github.ref }}
17
+ cancel-in-progress: true
18
+
19
+jobs:
20
+ release-note:
21
+ name: SDK release note
22
+ runs-on: ubuntu-latest
23
+ steps:
24
+ - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
25
+ with:
26
+ fetch-depth: 0
27
+ persist-credentials: false
28
+ - uses: ./.github/actions/setup-node-pnpm-bun
29
+ - run: pnpm install --frozen-lockfile --ignore-scripts
30
+ - name: Require a changeset for published SDK behavior
31
+ env:
32
+ SDK_RELEASE_NOTE_BASE: ${{ github.event.pull_request.base.sha }}
33
+ SDK_RELEASE_PR_BODY: ${{ github.event.pull_request.body }}
34
+ run: pnpm validate:changesets