Skip to content

chore(deps): bump the compatible-updates group across 1 directory with 3 updates - #192

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/compatible-updates-d84e23f984
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/main/compatible-updates-d84e23f984

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 19, 2026

Copy link
Copy Markdown

Bumps the compatible-updates group with 3 updates in the / directory: @composio/core, mcp-remote and zod.

Updates @composio/core from 0.22.0 to 0.25.0

Release notes

Sourced from @​composio/core's releases.

@​composio/core@​0.25.0

Minor Changes

  • 79c2d1d: Requires @composio/client 2.0.0-rc.17. The SDK now reports itself to the API client through the client's identity option instead of default headers. The headers sent with each request are unchanged, with one exception: on Cloudflare Workers and Vercel Edge with Node.js compatibility enabled, x-client-runtime now names that runtime instead of nodejs, and the polyfilled Node.js version is no longer sent as x-runtime-version. A createSession() clone no longer copies these headers into its defaultHeaders.

    The API client owns these headers, so defaultHeaders and createSession({ headers }) now reject x-client-provenance, x-client-version, x-client-library, x-client-library-version, x-client-language, x-client-runtime, x-sdk-version, x-source, x-framework, x-runtime and x-runtime-version with a ComposioError from @composio/client. The SDK used to overwrite such entries silently.

    A custom provider whose name cannot be sent as a header value (anything other than printable ASCII with no leading or trailing whitespace) is reported as unknown in x-framework.

  • 40546c3: Add experimental support for tool calls that need the user's approval.

    Sessions accept a requireApproval list next to the toolkits, tools and tags filters on create() and update(). A call to a matching tool doesn't run: session.execute() and session.executeMeta() throw ComposioToolInputRequiredError with the questions on inputRequests. To answer, repeat the same call with the user's answers in inputResponses and the error's requestState:

    const session = await composio.create('user_123', {
      tools: { gmail: { requireApproval: ['GMAIL_SEND_EMAIL'] } },
    });
    try {
    await session.execute('GMAIL_SEND_EMAIL', args);
    } catch (error) {
    if (!(error instanceof ComposioToolInputRequiredError)) throw error;
    const inputResponses = await promptUser(error.inputRequests);
    await session.execute('GMAIL_SEND_EMAIL', args, {
    inputResponses,
    requestState: error.requestState,
    });
    }

    promptUser is a placeholder for your application's consent UI. Display each request, wait for the user's response, and return the answers keyed by request ID. Forward decline and cancel responses unchanged.

    experimental.noElicitationSupportFallback ('deny' or 'allow') sets what happens to such a call when the session's MCP client can't ask the user.

    session.executeMeta() now takes these answers as its third argument, so its request options move to the fourth.

    The Python SDK gains the same require_approval lists, experimental.no_elicitation_support_fallback, and input_responses and request_state on session.execute() and session.execute_meta().

Patch Changes

  • f9a972b: Update the owned API client to @composio/client@2.0.0-rc.16. The SDK's public API and runtime behavior are unchanged.

  • 04cd5c4: Fix the trigger subscription lifecycle and contain errors from trigger handlers.

    • triggers.unsubscribe() now closes the realtime connection, so a Node process can exit once it has unsubscribed. A later triggers.subscribe() opens a new connection.
    • triggers.unsubscribe() before any subscribe() no longer fetches realtime credentials or creates a client.
    • Concurrent subscribe() calls share one connection, and unsubscribe() cancels a subscription that is still connecting, so it never opens a connection or delivers events afterwards.
    • A rejected promise from an async trigger handler is logged like a synchronous throw instead of escaping as an unhandled rejection that ends the process. Handler failures log the error's message rather than {}.
Changelog

Sourced from @​composio/core's changelog.

0.25.0

Minor Changes

  • 79c2d1d: Requires @composio/client 2.0.0-rc.17. The SDK now reports itself to the API client through the client's identity option instead of default headers. The headers sent with each request are unchanged, with one exception: on Cloudflare Workers and Vercel Edge with Node.js compatibility enabled, x-client-runtime now names that runtime instead of nodejs, and the polyfilled Node.js version is no longer sent as x-runtime-version. A createSession() clone no longer copies these headers into its defaultHeaders.

    The API client owns these headers, so defaultHeaders and createSession({ headers }) now reject x-client-provenance, x-client-version, x-client-library, x-client-library-version, x-client-language, x-client-runtime, x-sdk-version, x-source, x-framework, x-runtime and x-runtime-version with a ComposioError from @composio/client. The SDK used to overwrite such entries silently.

    A custom provider whose name cannot be sent as a header value (anything other than printable ASCII with no leading or trailing whitespace) is reported as unknown in x-framework.

  • 40546c3: Add experimental support for tool calls that need the user's approval.

    Sessions accept a requireApproval list next to the toolkits, tools and tags filters on create() and update(). A call to a matching tool doesn't run: session.execute() and session.executeMeta() throw ComposioToolInputRequiredError with the questions on inputRequests. To answer, repeat the same call with the user's answers in inputResponses and the error's requestState:

    const session = await composio.create('user_123', {
      tools: { gmail: { requireApproval: ['GMAIL_SEND_EMAIL'] } },
    });
    try {
    await session.execute('GMAIL_SEND_EMAIL', args);
    } catch (error) {
    if (!(error instanceof ComposioToolInputRequiredError)) throw error;
    const inputResponses = await promptUser(error.inputRequests);
    await session.execute('GMAIL_SEND_EMAIL', args, {
    inputResponses,
    requestState: error.requestState,
    });
    }

    promptUser is a placeholder for your application's consent UI. Display each request, wait for the user's response, and return the answers keyed by request ID. Forward decline and cancel responses unchanged.

    experimental.noElicitationSupportFallback ('deny' or 'allow') sets what happens to such a call when the session's MCP client can't ask the user.

    session.executeMeta() now takes these answers as its third argument, so its request options move to the fourth.

    The Python SDK gains the same require_approval lists, experimental.no_elicitation_support_fallback, and input_responses and request_state on session.execute() and session.execute_meta().

Patch Changes

  • f9a972b: Update the owned API client to @composio/client@2.0.0-rc.16. The SDK's public API and runtime behavior are unchanged.

  • 04cd5c4: Fix the trigger subscription lifecycle and contain errors from trigger handlers.

    • triggers.unsubscribe() now closes the realtime connection, so a Node process can exit once it has unsubscribed. A later triggers.subscribe() opens a new connection.
    • triggers.unsubscribe() before any subscribe() no longer fetches realtime credentials or creates a client.
    • Concurrent subscribe() calls share one connection, and unsubscribe() cancels a subscription that is still connecting, so it never opens a connection or delivers events afterwards.
    • A rejected promise from an async trigger handler is logged like a synchronous throw instead of escaping as an unhandled rejection that ends the process. Handler failures log the error's message rather than {}.

0.24.0

... (truncated)

Commits
  • dad230b Release: update version (#4895)
  • 79c2d1d chore: move owned clients to 2.0.0-rc.17 (#4906)
  • 04cd5c4 fix(core): close the trigger connection on unsubscribe() and contain handle...
  • f9a972b chore: move owned clients to 2.0.0-rc.16 (#4901)
  • 40546c3 feat(core): require approval for session tools and answer input requests (PLE...
  • 9a831f6 Release: update version (#4837)
  • e305e73 feat(core): accept instant.returnPricesInSearch on sessions (#4861)
  • 79b4912 feat(core): update owned clients to 2.0.0-rc.14 (#4863)
  • 33fe3ba fix(core): restore source type names in the TS SDK reference (#4848)
  • d66e5de feat(core): accept a boolean proxyExecute shorthand on sessions
  • Additional commits viewable in compare view

Updates mcp-remote from 0.14.3 to 0.15.1

Release notes

Sourced from mcp-remote's releases.

v0.15.1

0.15.1 (2026-10-14)

Bug Fixes

  • keep the static OAuth client and its secret out of the credential store (b529ea1)

v0.15.0

0.15.0 (2026-10-14)

Features

  • add optional OAuth completion page URL (#373) (34f7fd2)

v0.14.5

0.14.5 (2026-10-14)

Bug Fixes

  • give the callback port back once a sign-in has finished (#372) (65bb414)
  • persist OAuth discovery state for the authorization callback leg (#376) (e0a520e)
  • stop OAuth retries after follower timeout (#370) (55a61a9)

v0.14.4

0.14.4 (2026-10-14)

Bug Fixes

  • serve the OAuth error callback as plain text, not HTML (#375) (6a4ff90)
Commits
  • b529ea1 fix: keep the static OAuth client and its secret out of the credential store
  • 34f7fd2 feat: add optional OAuth completion page URL (#373)
  • 55a61a9 fix: stop OAuth retries after follower timeout (#370)
  • 65bb414 fix: give the callback port back once a sign-in has finished (#372)
  • e0a520e fix: persist OAuth discovery state for the authorization callback leg (#376)
  • 6a4ff90 fix: serve the OAuth error callback as plain text, not HTML (#375)
  • See full diff in compare view

Updates zod from 4.6.5 to 4.6.7

Release notes

Sourced from zod's releases.

v4.6.7

Commits:

  • b500a2ee95134f81d74da7911d7378dd2853d042 4.6.7

v4.6.6

Six malicious commits pushed to main on September 21 with a compromised git credential were reverted the same day in #6620 and have since been removed from the history of main. None were ever published to npm. The npm provenance for 4.6.6 names 284243fb, the pre-rewrite copy of 9c219833 with identical contents.

Commits:

  • 0cd3af5e9f50ad11bbcd4407a46a21b8848ba574 docs: load the en locale directly in Zod Mini
  • 9d5e60f162997b764b40d45aa02481888db50dea docs: import locales from zod/locales, not z.locales
  • 34a626f307871ecbb0123947559328dc52ed5e3e docs: tighten the z.locales tree-shaking note
  • 74304ce5b5796b5edb9a88ceb8e170b6ea3e82df release: stage npm versions instead of publishing them (#6622)
  • b2ef983e0711ff6517d6020b021071e2e5653efa docs: add Code for Japan to bronze sponsors
  • 8fb2faf0584828a6a027d8279db36f6f52784462 docs: crop the Code for Japan logo and list it first in bronze
  • bacad518c41610d654658172d325874bf0ee6290 docs: square the Code for Japan logo to match the other bronze tiles
  • c42596bd1c87e941d7241d10e012c5c196adcc10 release: hold the run on the release-approval environment until the staged versions are approved (#6638)
  • a2ba4a67986a3e6b2b131be30084a2f460d9ea67 fix(types): declare record output and input as members, not base type arguments (#6645)
  • a0ebf970f2d752e5f58527cd2942ff48be4f46bd fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • 529f78dd9431b07f49647fee3aa0819b3f8b66b7 4.6.6
  • 9c219833c3a3764fa1f1ea9c5ecec8254a63c0b1 ci: stage at verbose so a failed OIDC token exchange says why
Commits
  • b500a2e 4.6.7
  • 9c21983 ci: stage at verbose so a failed OIDC token exchange says why
  • 529f78d 4.6.6
  • a0ebf97 fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • a2ba4a6 fix(types): declare record output and input as members, not base type argumen...
  • c42596b release: hold the run on the release-approval environment until the staged ve...
  • bacad51 docs: square the Code for Japan logo to match the other bronze tiles
  • 8fb2faf docs: crop the Code for Japan logo and list it first in bronze
  • b2ef983 docs: add Code for Japan to bronze sponsors
  • 74304ce release: stage npm versions instead of publishing them (#6622)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…h 3 updates

Bumps the compatible-updates group with 3 updates in the / directory: [@composio/core](https://github.com/ComposioHQ/composio/tree/HEAD/ts/packages/core), [mcp-remote](https://github.com/punkpeye/mcp-remote) and [zod](https://github.com/colinhacks/zod).


Updates `@composio/core` from 0.22.0 to 0.25.0
- [Release notes](https://github.com/ComposioHQ/composio/releases)
- [Changelog](https://github.com/ComposioHQ/composio/blob/next/ts/packages/core/CHANGELOG.md)
- [Commits](https://github.com/ComposioHQ/composio/commits/@composio/core@0.25.0/ts/packages/core)

Updates `mcp-remote` from 0.14.3 to 0.15.1
- [Release notes](https://github.com/punkpeye/mcp-remote/releases)
- [Commits](punkpeye/mcp-remote@v0.14.3...v0.15.1)

Updates `zod` from 4.6.5 to 4.6.7
- [Release notes](https://github.com/colinhacks/zod/releases)
- [Commits](colinhacks/zod@v4.6.5...v4.6.7)

---
updated-dependencies:
- dependency-name: "@composio/core"
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: compatible-updates
- dependency-name: mcp-remote
  dependency-version: 0.15.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: compatible-updates
- dependency-name: zod
  dependency-version: 4.6.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from makeitfutureDev as a code owner October 19, 2026 06:20
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants