@devries-cameron20 / composio Mirror · read-only / commits / cb19864d5
Fork 0

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, 07:15 UTC

docs(changelog): describe Python 0.29.1 dependency caps accurately (#5063)

This PR: - no Linear issue; addresses the Greptile finding on #5062 - the 0.29.1 notes said each range stops before the next major, but caps sit before the first *unreleased* major, so `openai>=2.48.0,<4` allows 2.x and 3.x and `anthropic>=0.120.0,<3` allows 0.x through 2.x - rewrites that bullet to state the rule and show both examples

Alberto Schiabel committed Oct 22, 2026 at 16:23 UTC cb19864d54e7a7c0882c0a9a24539e95f0fe5f18
1 file changed +1 -1
docs/content/changelog/10-22-26-python-sdk-0-29-1.mdx
+1 -1
@@ -17,7 +17,7 @@ All 13 Python provider packages are released at `0.29.1`.
17 ### What's changed
18
19 - **`certifi>=2026.10.19` is now required.** That bundle removes the emSign ECC Root CA - G3 root after eight eMudhra intermediate keys were compromised. Older bundles still trust certificates issued under it.
20 -- **Third-party dependencies have upper bounds.** Each range now stops before the next major version, or before `1.0` for `0.x` packages, so a new major line can't install until the SDK supports it. For example, `openai>=2.48.0,<4` and `pydantic>=2.11.9,<3`. `certifi` stays uncapped so CA bundle updates always install.
20 +- **Third-party dependencies have upper bounds.** Each range stops before the first major version that wasn't released yet when the cap was set, or before `1.0` for packages still on `0.x`. A future major line can't install until the SDK raises the cap. Ranges can still span majors that already exist: `openai>=2.48.0,<4` allows 2.x and 3.x, and `anthropic>=0.120.0,<3` allows 0.x through 2.x. `certifi` stays uncapped so CA bundle updates always install.
21 - **`pysher` is pinned to `1.0.8`.** The trigger client depends on it, and it has had no release since 2022. Its transport is capped at `websocket-client<2`.
22 - **Releases come from a locked build.** Packages are built only from locked dependencies and published with PyPI trusted publishing, so each file on PyPI carries an attestation linking it to the GitHub workflow that built it.
23