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, 22:15 UTC
chore(changeset): @composio/core minor bump for link-auth migration tooling
Required by the TS release flow — without a changeset entry, merging to next won't open or update the Release: update version PR and the new exported error class won't reach npm. `minor` because the new exported error class is additive but user-facing. Python is tag-driven and doesn't need a changeset. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Composio committed
May 5, 2026 at 09:58 UTC
9f1497171609f55decc77d938bd16c32069bdf29
1 file changed
+11
.changeset/sdk-link-auth-migration.md
new
+11
@@ -0,0 +1,11 @@
1
+---
2
+'@composio/core': minor
3
+---
4
+
5
+Add migration tooling for the [link auth migration](https://docs.composio.dev/docs/changelog/2026/04/24): callers using `composio.connectedAccounts.initiate()` for Composio-managed auth configs on redirectable OAuth schemes (OAuth1, OAuth2, DCR_OAUTH) now get a typed error and a one-time deprecation warning ahead of the **2026-07-03** all-orgs cutover.
6
+
7
+- **Added:** `ComposioLegacyConnectedAccountsEndpointRetiredError`, exported from `@composio/core`. Thrown by `initiate()` when the underlying `POST /api/v3/connected_accounts` returns a 400 indicating the retiring path. Carries the migration message and a `possibleFixes` block pointing at `link()` and the migration guide.
8
+- **Added:** one-time-per-process `console.warn` from `initiate()` when the response indicates a redirectable OAuth scheme. Wording is conditional ("If this auth config is Composio-managed…") so callers using custom OAuth apps or non-OAuth schemes can ignore it without ambiguity.
9
+- **JSDoc:** `initiate()` now flags the retirement explicitly and points at `link()` for the affected combination. Custom auth configs and non-OAuth schemes (API key, bearer, basic) are unaffected.
10
+
11
+No behavior change for any caller outside the Composio-managed-OAuth combination — `initiate()` continues to call the legacy endpoint, return the same `ConnectionRequest` shape, and respect the `allowMultiple` guard.