Version Packages - #1
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Reviewer's GuideThis automated Changesets release PR versions the affected workspace packages, updates their changelogs and lockfile dependency graph, and removes the five changeset files whose changes are being released, including MCP search-tool, lazy-loading, and OpenAPI/Graph memory-footprint improvements. Sequence diagram for opt-in MCP integration search toolssequenceDiagram
participant Client
participant MCP
participant Model
participant Execution
participant Integration
Client->>MCP: Connect with search_tools=true
MCP->>MCP: Build search_<integration> tools from integration inventory
MCP-->>Model: Expose one tool per integration
Model->>MCP: search_<integration>(query)
MCP->>Execution: execute with tools.search({ namespace })
Execution->>Integration: Search namespace
Integration-->>Execution: Search results
Execution-->>MCP: Return results
MCP-->>Model: Return results
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 26, 2026 08:04
21c203c to
36d7dbe
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 26, 2026 08:11
36d7dbe to
548782c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@executor-js/cli@0.2.51
Patch Changes
@executor-js/config@1.6.1
Patch Changes
@executor-js/execution@1.6.1
Patch Changes
#1741
62748e8Thanks @RhysSullivan! - Opt-in per-integration search tools on the MCP surfaceConnecting with
?search_tools=true(stdio:executor mcp --search-tools) adds one minimally-describedsearch_<integration>MCP tool per connected integration, so the integration namespaces reach the model as tool names it can see without calling anything. Each call routes through the same flow astools.search({ namespace })insideexecute, and the tool list comes from the same inventory theexecutedescription shows. Off by default; a clean endpoint URL is unchanged.#1749
d4afe0cThanks @RhysSullivan! - Slim the per-integrationsearch_<integration>tool definitions to under half their size: one shared one-line description (the tool name already carries the namespace) and a single barequeryparameter, dropping thelimit/offsetknobs. A session pays for these definitions once per connected integration, so the surface now costs ~2k tokens instead of ~5k at 30 integrations; paging through a namespace belongs inexecute.Updated dependencies []:
@executor-js/vite-plugin@0.0.61
Patch Changes
@executor-js/runtime-quickjs@1.6.1
Patch Changes
@executor-js/plugin-desktop-settings@1.6.1
Patch Changes
@executor-js/plugin-example@1.6.1
Patch Changes
@executor-js/plugin-file-secrets@1.6.1
Patch Changes
@executor-js/plugin-graphql@1.6.1
Patch Changes
@executor-js/plugin-keychain@1.6.1
Patch Changes
@executor-js/plugin-mcp@1.6.1
Patch Changes
#1747
91062c2Thanks @RhysSullivan! - Load the MCP client SDK lazily on first outbound connection instead of at module evaluation. Runtimes that bundle the plugin (notably Cloudflare Workers) no longer pay the client package's module-eval memory and CPU on startup or on code paths that never dial an MCP server.Updated dependencies []:
@executor-js/plugin-onepassword@1.6.1
Patch Changes
@executor-js/plugin-openapi@1.6.1
Patch Changes
#1753
ddbf0feThanks @RhysSullivan! - Serve Microsoft Graph preset selections from precomputed slice release assets instead of the 43MB upstream monolith. The monolith fetch almost never survives a 128MB Workers isolate (production traces show one completion in 30 days), so covered selections — every catalog preset, plus any combination within the default bundle — now read a 4–19MB filtered document built offline by the graph-slices workflow, with the monolith path kept only as a fallback and for full-graph/custom-scope selections.#1751
0007474Thanks @RhysSullivan! - Preview OpenAPI spec-format selections (Microsoft Graph) through the streaming structural-split path instead of a whole-document parse, and guard generic whole-document parses by parsed-tree size (line count for block YAML, text size for JSON). Previewing a Graph preset URL previously parsed the 43MB source whole and killed the 128MB Workers isolate mid-request, surfacing as an empty 503; it now streams within budget, and oversized generic specs fail with an actionable error instead of taking down the isolate.Updated dependencies []:
@executor-js/plugin-toolkits@1.5.36
Patch Changes
@executor-js/sdk@1.6.1
@executor-js/codemode-core@1.6.1
executor@1.6.1
Patch Changes
#1741
62748e8Thanks @RhysSullivan! - Opt-in per-integration search tools on the MCP surfaceConnecting with
?search_tools=true(stdio:executor mcp --search-tools) adds one minimally-describedsearch_<integration>MCP tool per connected integration, so the integration namespaces reach the model as tool names it can see without calling anything. Each call routes through the same flow astools.search({ namespace })insideexecute, and the tool list comes from the same inventory theexecutedescription shows. Off by default; a clean endpoint URL is unchanged.#1749
d4afe0cThanks @RhysSullivan! - Slim the per-integrationsearch_<integration>tool definitions to under half their size: one shared one-line description (the tool name already carries the namespace) and a single barequeryparameter, dropping thelimit/offsetknobs. A session pays for these definitions once per connected integration, so the surface now costs ~2k tokens instead of ~5k at 30 integrations; paging through a namespace belongs inexecute.Updated dependencies []:
@executor-js/cloud@1.4.62
Patch Changes
ddbf0fe,91062c2,62748e8,0007474,d4afe0c]:@executor-js/host-selfhost@0.0.43
Patch Changes
ddbf0fe,91062c2,62748e8,0007474,d4afe0c]:@executor-js/local@1.6.1
Patch Changes
ddbf0fe,91062c2,62748e8,0007474,d4afe0c]:@executor-js/e2e@0.0.41
Patch Changes
ddbf0fe,91062c2,0007474]:@executor-js/example-all-plugins@0.0.62
Patch Changes
ddbf0fe,91062c2,0007474]:@executor-js/example-docs-sdk-quickstart@0.0.47
Patch Changes
ddbf0fe,0007474]:@executor-js/analytics@0.1.8
Patch Changes
62748e8,d4afe0c]:@executor-js/api@1.4.64
Patch Changes
62748e8,d4afe0c]:@executor-js/cloudflare@0.0.43
Patch Changes
62748e8,d4afe0c]:@executor-js/mcp-apps-shell@1.4.12
Patch Changes
@executor-js/runtime-workerd-subprocess@0.0.16
Patch Changes
@executor-js/plugin-encrypted-secrets@0.0.43
Patch Changes
@executor-js/plugin-provider-service-split@0.0.15
Patch Changes
ddbf0fe,0007474]:@executor-js/react@1.4.64
Patch Changes
@executor-js/desktop@1.6.1