-
Release: update version (#3402)
发布于
2026-05-11 23:11:04 +00:00 This PR was opened by the Changesets
release GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to next, this PR will
be updated.Releases
@composio/cli-local-tools@0.0.3
Patch Changes
@composio/core@0.9.1
Patch Changes
-
84a3a07: AddaccountTypeand per-user ACL support for SHARED
connected accounts. -
accountTypeon create:composio.connectedAccounts.link(userId, authConfigId, { accountType: 'SHARED' })creates a SHARED connection.
Default remainsPRIVATE. A SHARED connection can be used by other
userIds, but only when the connection is explicitly pinned in a
tool-router session's config and only when the requestinguserId
passes the connection's ACL. -
accountTypeon retrieve:get()andlist()responses now
includeaccountType('PRIVATE' | 'SHARED'). -
aclConfigForSharedon create + retrieve: per-user ACL block —{ allowAllUsers, allowedUserIds, notAllowedUserIds }. On responses the
field isundefinedwhen the caller isn't authorised to see the ACL, so
callers can distinguish "I can't see the ACL" from "ACL is the
default deny-by-default state". -
updateAcl()method (new):
composio.connectedAccounts.updateAcl(nanoid, { allowAllUsers, allowedUserIds, notAllowedUserIds })writes the ACL viaPATCH. PATCH
semantics — omit a field to leave it unchanged; pass an empty array to
clear an allow/deny list. At least one field required. Calling on a
PRIVATE connection raisesComposioAclOnlyForSharedError(400). -
ToolRouterSession.authorize()options gainaccountType+
aclConfigForShared, so a SHARED connection with an ACL can be
created in one call from inside a tool-router session.ACL resolution rule (deny wins):
- requesting
userId∈notAllowedUserIds→ DENY allowAllUsers === true→ ALLOW- requesting
userId∈allowedUserIds→ ALLOW - otherwise → DENY (deny-by-default)
- requesting
Limits: each ACL list accepts up to 1000 entries; each
userIdis
1..256 characters. The SDK enforces these caps at the input boundary.New error classes:ComposioSharedAccessDeniedError(403) — surfaces from direct
connectedAccountIdexecution paths when the requesting user fails the
ACL.ComposioAclOnlyForSharedError(400) — ACL fields sent on a PRIVATE
connection.ComposioSharedConnectionNotAccessibleError(400) — tool-router
session create / PATCH with a pinned SHARED connection the session user
cannot use.
No breaking changes. Existing
link()callers without the new options
get aPRIVATEconnection exactly as today; existingget()/list()
callers see new optional fields.The Python SDK mirror ships in a separate PR.c358ffa: Fix false-positiveinitiate()deprecation warning for
custom auth configs (SEC-339 follow-up).
composio.connectedAccounts.initiate()previously emitted a one-time
console.warnon every redirectable-OAuth response, regardless of
whether the auth config was Composio-managed (subject to the 2026-07-03
cutover) or custom (unaffected). The wording was conditional ("If this
auth config is Composio-managed…") so callers using their own OAuth apps
could ignore it, but the warning still printed and caused noise in logs.Apollo already emits the SEC-339
Deprecation/Sunset/Link rel="deprecation"headers (RFC 9745 / RFC 8594) only on the
retiring branch — managed + redirectable OAuth. The SDK now reads the
Deprecationheader from the response (viaAPIPromise.withResponse())
and gates the warning on its presence. Custom auth configs and non-OAuth
schemes get a clean response from the server and now stay silent in the
SDK as well.-
Behavior change: No warning is emitted for
initiate()calls
against custom OAuth auth configs or non-OAuth schemes (API key, bearer,
basic). Managed-OAuth callers continue to get exactly one warning per
process, now with revised wording that points at the response'sSunset
header for the precise cutover date. -
No public API change:
initiate()returns the same
ConnectionRequestshape and respects the sameallowMultipleguard.
ComposioLegacyConnectedAccountsEndpointRetiredErrorcontinues to
surface from the 400 retired-path response. -
Test scaffolding: new mock helper
mockApiPromiseWithHeaders()in
connectedAccounts.test.tswraps a value as anAPIPromise-shaped
thenable so the new tests can simulate apollo's header behavior.
Pre-existing initiate tests usingmockResolvedValueOncecontinue to
pass via the SDK's defensive fallback whenwithResponseis absent on
the mock.Python SDK gets the matching change in the same release train.
@composio/anthropic@0.9.1
Patch Changes
@composio/claude-agent-sdk@0.9.1
Patch Changes
@composio/cloudflare@0.9.1
Patch Changes
@composio/google@0.9.1
Patch Changes
@composio/langchain@0.9.1
Patch Changes
@composio/llamaindex@0.9.1
Patch Changes
@composio/mastra@0.9.1
Patch Changes
@composio/openai@0.9.1
Patch Changes
@composio/openai-agents@0.9.1
Patch Changes
@composio/vercel@0.9.1
Patch Changes
@composio/cli@0.2.29
Patch Changes
- Updated dependencies [
84a3a07] - Updated dependencies [
c358ffa]- @composio/core@0.9.1
- @composio/cli-local-tools@0.0.3
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
下载附件
-