Version Packages - #1557
Open
RhysSullivan wants to merge 1 commit into
Open
Conversation
RhysSullivan
force-pushed
the
changeset-release/main
branch
from
August 7, 2026 21:44
6824817 to
21da38d
Compare
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 2bdbe5f | Commit Preview URL Branch Preview URL |
Aug 16 2026, 12:46 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 2bdbe5f | Aug 16 2026, 12:47 PM |
Contributor
Cloudflare preview
Sign-in is Cloudflare Access (one-time PIN to an allowed email). The preview has its own database and encryption key; it is destroyed when this PR closes. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
RhysSullivan
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
August 16, 2026 10:40
8a91783 to
1c91dbb
Compare
RhysSullivan
force-pushed
the
changeset-release/main
branch
from
August 16, 2026 12:44
1c91dbb to
2bdbe5f
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
1 participant
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/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
#1580
d572658Thanks @RhysSullivan! - Fix: the admin joined user view no longer issues one connection query per subjectadmin.listSubjectsWithConnectionsread a page of subjects and then queriedconnections once per subject, sequentially. A default page therefore cost 100
round trips inside a single request, which on a per-request socket dominated
the response. It now reads the page and then batches every subject's
connections into one query, so the cost is two queries regardless of page size.
A subject with no connections still reports an empty array rather than dropping
out of the page, and the batched read carries the same
owner: "user"andtenant scoping the per-subject read did.
The
?email=filter on the admin users endpoints is also applied before theread rather than after it: the address resolves to a principal id and that id is
read directly, instead of paging the tenant and keeping the row that matched.
Paging still applies to a filtered response, but to the selected row — one row
at
offset: 0, empty beyond it.@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
[email protected]
Patch Changes
#1600
1b5f931Thanks @RhysSullivan! - Addintegrations.removeto the core tools so an agent can drop a catalog integrationintegrations.listadvertisescanRemoveper integration, but nothing on the agent surface could act on it: removal existed only on the HTTP API and the web console, so an agent that could add an integration could never take one back out. Cleaning up a catalog meant clicking through the UI once per integration.The core-tools plugin now contributes
integrations.remove, taking theslugreported byintegrations.listand cascading to every connection under the integration and the tools those produced. It is approval-gated, being strictly more destructive thanconnections.remove. Theremovedflag is honest rather than always-true:falsemeans no catalog row matched, so an already-absent slug and a built-in namespace likeexecutorare distinguishable from a real removal, and an integration pinned withcanRemove: falseis refused withIntegrationRemovalNotAllowedErrorinstead of silently surviving.#1556
f674fb8Thanks @RhysSullivan! - Fix: native MCP elicitation now reaches clients on the local HTTP endpoint instead of timing outThe local daemon's Streamable HTTP transport ran with
enableJsonResponse: true, which buffers atools/callinto a single JSON body and leaves no open stream for the server to write on. A server-to-clientelicitation/createraised during that call was therefore never delivered, and approval-gated tools failed with a-32001request timeout even though the session had negotiatedelicitation_mode=nativeand the client'selicitation.formcapability. The transport now uses the spec-default SSE streaming, so the reverse request rides the originating tool call's stream — matching the Cloudflare host's behaviour.#1603
624e85fThanks @RhysSullivan! - Fix:oauth.clients.removereported success for clients it never removedThe tool returned
{ removed: true }unconditionally.oauth.removeClientis idempotent by design at the storage layer —deleteManyon a missing row is a no-op, which is the right behaviour for a delete — but the tool mapped that silence to success, so a typo'd slug, an already-deleted client, and the wrong owner were all indistinguishable from a real deletion.This bites hardest because clients are keyed by BOTH owner and slug, so the same slug can exist separately under
organduser. An agent sweeping a list of slugs under one hardcoded owner would delete only half of them and report every call as a success, leaving org-owned OAuth apps registered after everything they authorized was gone.The tool now checks the caller-visible client set first and returns
removed: falsewhen nothing matched that(owner, slug)pair. The service-levelremoveClientis unchanged and stays idempotent.Updated dependencies [
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
@executor-js/[email protected]
Patch Changes
@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]
Patch Changes
d572658]:@executor-js/[email protected]