Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs(changelog): sync January 2026 changelogs from fern
Add missing changelog entries: - 01-14-26: Auth config PATCH semantics fix - 01-20-26: File modifier anyOf/oneOf/allOf support - 01-20-26: File TTL with presigned URLs Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sushmithamallesh committed
Jan 20, 2026 at 19:36 UTC
ac4336732b98334c01ba399ba10cf7e392b4a696
3 files changed
+398
docs/content/changelog/01-14-26-auth-config-patch-semantics.mdx
new
+192
@@ -0,0 +1,192 @@
1
+---
2
+title: "True PATCH Semantics for Auth Config Updates"
3
+date: "2026-01-14"
4
+---
5
+
6
+## Version Information
7
+
8
+### TypeScript/JavaScript
9
+- Package: `@composio/core` and provider packages
10
+- Version: `0.5.1`+
11
+
12
+### Python
13
+- Package: `composio-core` and provider packages
14
+- Version: `0.10.7`+
15
+
16
+---
17
+
18
+The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial update semantics. Previously, omitting fields would clear them (behaving like PUT). Now, omitted fields are preserved—only explicitly provided fields are modified.
19
+
20
+<Callout type="warn">
21
+**Breaking Change**: If you relied on omitting fields to clear them, you must now explicitly send `null` or `[]`. See [Migration Guide](#migration-guide) below.
22
+</Callout>
23
+
24
+## What Changed
25
+
26
+| Field | Before (Buggy) | After (Correct) |
27
+| ----------------------------- | ------------------------ | --------------------------------- |
28
+| `credentials` | Required on every update | Optional—merged with existing |
29
+| `tool_access_config` | Reset to `{}` if omitted | Preserved if omitted |
30
+| `scopes` (type: default) | Cleared if omitted | Preserved if omitted |
31
+| `restrict_to_following_tools` | Reset to `[]` if omitted | Preserved if omitted |
32
+
33
+<Callout type="info">
34
+**Merge Behavior**: The `credentials` object is merged—send only the fields you want to change, and existing fields are preserved.
35
+</Callout>
36
+
37
+## New Capabilities
38
+
39
+### Rotate a Single Credential Field
40
+
41
+Update just `client_secret` without resending `client_id` or other fields:
42
+
43
+<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
44
+<Tab value="Python">
45
+```python
46
+from composio import Composio
47
+
48
+composio = Composio()
49
+
50
+# Only send the field you want to update - other credentials are preserved
51
+composio.auth_configs.update(
52
+ "ac_yourAuthConfigId",
53
+ options={
54
+ "type": "custom",
55
+ "credentials": {
56
+ "client_secret": "new_rotated_secret",
57
+ },
58
+ },
59
+)
60
+```
61
+</Tab>
62
+<Tab value="TypeScript">
63
+```typescript
64
+import { Composio } from "@composio/core";
65
+
66
+const composio = new Composio();
67
+
68
+// Only send the field you want to update - other credentials are preserved
69
+await composio.authConfigs.update("ac_yourAuthConfigId", {
70
+ type: "custom",
71
+ credentials: {
72
+ client_secret: "new_rotated_secret",
73
+ },
74
+});
75
+```
76
+</Tab>
77
+</Tabs>
78
+
79
+### Update Tool Restrictions Without Touching Credentials
80
+
81
+Previously, this would fail because `credentials` was required. Now it works:
82
+
83
+<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
84
+<Tab value="Python">
85
+```python
86
+from composio import Composio
87
+
88
+composio = Composio()
89
+
90
+# Update tool restrictions - credentials are automatically preserved
91
+composio.auth_configs.update(
92
+ "ac_yourAuthConfigId",
93
+ options={
94
+ "type": "custom",
95
+ "tool_access_config": {
96
+ "tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
97
+ },
98
+ },
99
+)
100
+```
101
+</Tab>
102
+<Tab value="TypeScript">
103
+```typescript
104
+import { Composio } from "@composio/core";
105
+
106
+const composio = new Composio();
107
+
108
+// Note: TypeScript SDK currently requires credentials for custom type updates
109
+await composio.authConfigs.update("ac_yourAuthConfigId", {
110
+ type: "custom",
111
+ credentials: {
112
+ // Include existing credentials when using TS SDK
113
+ },
114
+ toolAccessConfig: {
115
+ toolsAvailableForExecution: ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
116
+ },
117
+});
118
+```
119
+</Tab>
120
+</Tabs>
121
+
122
+## Migration Guide
123
+
124
+### Am I Affected?
125
+
126
+**Yes**, if your code relied on omitting fields to clear them.
127
+
128
+**No**, if you always send complete payloads or only use PATCH to update specific fields.
129
+
130
+### How to Clear Fields Explicitly
131
+
132
+| To Clear | Python SDK | TypeScript SDK |
133
+| -------------------- | ------------------------------------------------------------- | ------------------------------------------------------ |
134
+| `tool_access_config` | `"tool_access_config": {"tools_available_for_execution": []}` | `toolAccessConfig: { toolsAvailableForExecution: [] }` |
135
+| `scopes` (default) | `"scopes": ""` | `scopes: ""` (via HTTP API) |
136
+
137
+<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
138
+<Tab value="Python">
139
+```python
140
+from composio import Composio
141
+
142
+composio = Composio()
143
+
144
+# Explicitly clear tool restrictions with empty array
145
+composio.auth_configs.update(
146
+ "ac_yourAuthConfigId",
147
+ options={
148
+ "type": "custom",
149
+ "tool_access_config": {
150
+ "tools_available_for_execution": [],
151
+ },
152
+ },
153
+)
154
+```
155
+</Tab>
156
+<Tab value="TypeScript">
157
+```typescript
158
+import { Composio } from "@composio/core";
159
+
160
+const composio = new Composio();
161
+
162
+// Explicitly clear tool restrictions with empty array
163
+await composio.authConfigs.update("ac_yourAuthConfigId", {
164
+ type: "custom",
165
+ credentials: {
166
+ // Include existing credentials when using TS SDK
167
+ },
168
+ toolAccessConfig: {
169
+ toolsAvailableForExecution: [],
170
+ },
171
+});
172
+```
173
+</Tab>
174
+</Tabs>
175
+
176
+### Raw HTTP API
177
+
178
+For users calling the API directly:
179
+
180
+```bash
181
+# Rotate single credential
182
+curl -X PATCH "https://backend.composio.dev/api/v3/auth_configs/{id}" \
183
+ -H "x-api-key: YOUR_API_KEY" \
184
+ -H "Content-Type: application/json" \
185
+ -d '{"type": "custom", "credentials": {"client_secret": "new_secret"}}'
186
+
187
+# Clear tool restrictions
188
+curl -X PATCH "https://backend.composio.dev/api/v3/auth_configs/{id}" \
189
+ -H "x-api-key: YOUR_API_KEY" \
190
+ -H "Content-Type: application/json" \
191
+ -d '{"type": "custom", "tool_access_config": {"tools_available_for_execution": []}}'
192
+```
docs/content/changelog/01-20-26-file-modifier-anyof-support.mdx
new
+147
@@ -0,0 +1,147 @@
1
+---
2
+title: "[Critical] File Upload/Download Fixes for anyOf, oneOf, and allOf Schemas"
3
+date: "2026-01-20"
4
+---
5
+
6
+## Version Information
7
+
8
+### TypeScript/JavaScript
9
+- Package: `@composio/core` and provider packages
10
+- Version: `0.5.3`+
11
+
12
+### Python
13
+- Package: `composio` and provider packages
14
+- Version: `0.10.8`+
15
+
16
+---
17
+
18
+The file handling modifiers now properly handle `file_uploadable` and `file_downloadable` properties nested within `anyOf`, `oneOf`, and `allOf` JSON Schema declarations. Previously, only direct child properties (and partial `allOf` support) were detected for file upload/download transformations.
19
+
20
+<Callout type="info">
21
+We recommend updating to version `0.5.3` (TypeScript) or `0.10.8` (Python) or later to ensure file uploads and downloads work correctly with tools that use union or intersection types in their schemas.
22
+</Callout>
23
+
24
+## What Changed
25
+
26
+### Before (Bug)
27
+
28
+File properties inside `anyOf`, `oneOf`, or `allOf` were not detected:
29
+
30
+```typescript
31
+// This schema's file_uploadable was NOT being processed
32
+inputParameters: {
33
+ type: 'object',
34
+ properties: {
35
+ fileInput: {
36
+ anyOf: [
37
+ {
38
+ type: 'string',
39
+ file_uploadable: true // ❌ Not detected
40
+ },
41
+ {
42
+ type: 'null'
43
+ }
44
+ ]
45
+ }
46
+ }
47
+}
48
+```
49
+
50
+### After (Fixed)
51
+
52
+File properties are now correctly detected and processed at any nesting level:
53
+
54
+```typescript
55
+// Now properly detected and transformed
56
+inputParameters: {
57
+ type: 'object',
58
+ properties: {
59
+ fileInput: {
60
+ anyOf: [
61
+ {
62
+ type: 'string',
63
+ file_uploadable: true // ✅ Detected and processed
64
+ },
65
+ {
66
+ type: 'null'
67
+ }
68
+ ]
69
+ }
70
+ }
71
+}
72
+```
73
+
74
+## Affected Scenarios
75
+
76
+| Scenario | Before | After |
77
+|----------|--------|-------|
78
+| `file_uploadable` in `anyOf` | Not detected | Works |
79
+| `file_uploadable` in `oneOf` | Not detected | Works |
80
+| `file_uploadable` in `allOf` | Not detected | Works |
81
+| `file_downloadable` in `anyOf` | Not detected | Works |
82
+| `file_downloadable` in `oneOf` | Not detected | Works |
83
+| `file_downloadable` in `allOf` | Not detected | Works |
84
+| Nested objects inside union types | Not detected | Works |
85
+| Array items with union types | Not detected | Works |
86
+
87
+## How to Update
88
+
89
+### TypeScript/JavaScript
90
+
91
+<Tabs groupId="package-manager" items={['npm', 'pnpm', 'yarn']} persist>
92
+<Tab value="npm">
93
+```bash
94
+npm update @composio/core@latest
95
+```
96
+</Tab>
97
+<Tab value="pnpm">
98
+```bash
99
+pnpm update @composio/core@latest
100
+```
101
+</Tab>
102
+<Tab value="yarn">
103
+```bash
104
+yarn upgrade @composio/core@latest
105
+```
106
+</Tab>
107
+</Tabs>
108
+
109
+### Python
110
+
111
+<Tabs groupId="python-package-manager" items={['pip', 'uv', 'poetry']} persist>
112
+<Tab value="pip">
113
+```bash
114
+pip install --upgrade composio
115
+```
116
+</Tab>
117
+<Tab value="uv">
118
+```bash
119
+uv pip install --upgrade composio
120
+```
121
+</Tab>
122
+<Tab value="poetry">
123
+```bash
124
+poetry update composio
125
+```
126
+</Tab>
127
+</Tabs>
128
+
129
+## Backward Compatibility
130
+
131
+This release is fully backward compatible:
132
+
133
+- All existing code continues to work without modifications
134
+- No migration required
135
+- File upload/download for direct properties continues to work as before
136
+- The fix only adds support for previously unsupported schema patterns
137
+
138
+## Impact Summary
139
+
140
+| Change | Runtime Breaking | TypeScript Breaking | Migration Required |
141
+|--------|------------------|---------------------|-------------------|
142
+| `anyOf` support for file uploads | No | No | No |
143
+| `oneOf` support for file uploads | No | No | No |
144
+| `allOf` support for file uploads | No | No | No |
145
+| `anyOf` support for file downloads | No | No | No |
146
+| `oneOf` support for file downloads | No | No | No |
147
+| `allOf` support for file downloads | No | No | No |
docs/content/changelog/01-20-26-file-ttl.mdx
new
+59
@@ -0,0 +1,59 @@
1
+---
2
+title: "File handling in tool execution now uses presigned URLs"
3
+date: "2026-01-20"
4
+---
5
+
6
+## Summary
7
+
8
+Files involved in tool execution are now shared via presigned URLs with a default TTL (time-to-live) of 1 hour. You can customize the file TTL through your project configuration.
9
+
10
+## What changed
11
+
12
+When tools return files (images, documents, exports, etc.), these files are now delivered as presigned URLs with a configurable TTL instead of non-expiring URLs. This provides:
13
+
14
+- **Automatic cleanup** - Files expire after the configured TTL
15
+- **Configurable retention** - Adjust file availability based on your application's needs
16
+
17
+## Default behavior
18
+
19
+All files returned from tool execution now have a **1 hour TTL** by default. After this period, the presigned URLs expire and files are no longer accessible.
20
+
21
+## Configuring file TTL
22
+
23
+You can adjust the file TTL to match your application's needs.
24
+
25
+### Via Dashboard
26
+
27
+1. Navigate to **Project Settings** in your Composio dashboard
28
+2. Find the **File TTL** configuration option
29
+3. Set your desired TTL value
30
+
31
+### Via API
32
+
33
+Use the [Update Project Config API](https://docs.composio.dev/rest-api/projects/patch-org-project-config) to programmatically configure the file TTL:
34
+
35
+```bash
36
+curl -X PATCH "https://backend.composio.dev/api/v3/org/projects/config" \
37
+ -H "x-api-key: YOUR_API_KEY" \
38
+ -H "Content-Type: application/json" \
39
+ -d '{
40
+ "fileTtl": 3600
41
+ }'
42
+```
43
+
44
+## Impact
45
+
46
+| Aspect | Before | After |
47
+|--------|--------|-------|
48
+| File delivery | Non-expiring URLs | Presigned URLs with TTL |
49
+| Default expiry | None | 1 hour |
50
+| TTL customization | Not available | Configurable via project settings |
51
+
52
+## Migration
53
+
54
+No code changes are required. Your existing integrations will continue to receive file URLs as before, but these URLs will now expire after the configured TTL.
55
+
56
+If your application stores or caches file URLs for later use, ensure you handle URL expiration appropriately by either:
57
+- Downloading files before the TTL expires
58
+- Re-executing the tool to obtain fresh URLs when needed
59
+- Increasing the TTL via project settings to match your retention requirements