Repository navigation
Version Packages - #1653
Merged
Merged
Version Packages#1653
Conversation
Contributor
Cloudflare previewTorn down — the PR is closed. |
@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: |
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/cli@0.2.49
Patch Changes
d3f0617]:@executor-js/config@1.5.42
Patch Changes
d3f0617]:@executor-js/execution@1.5.42
Patch Changes
d3f0617]:@executor-js/sdk@1.5.42
Patch Changes
d3f0617Thanks @RhysSullivan! - Redact every span header attribute outside a safe allowlist on the hosted HTTP client. The tracer's default four-name blocklist let provider-specific credential headers reach the trace backend verbatim; the hosted client now inverts the model and masks everything except structurally safe negotiation, caching, and tracing headers.@executor-js/vite-plugin@0.0.59
Patch Changes
d3f0617]:@executor-js/runtime-quickjs@1.5.42
Patch Changes
@executor-js/plugin-desktop-settings@1.5.42
Patch Changes
d3f0617]:@executor-js/plugin-example@1.5.42
Patch Changes
d3f0617]:@executor-js/plugin-file-secrets@1.5.42
Patch Changes
d3f0617]:@executor-js/plugin-graphql@1.5.42
Patch Changes
d3f0617]:@executor-js/plugin-keychain@1.5.42
Patch Changes
d3f0617]:@executor-js/plugin-mcp@1.5.42
Patch Changes
#1646
9ecc7cbThanks @RhysSullivan! - Stdio MCP servers can negotiate the modern protocol (versionNegotiation: "auto")Spawned stdio MCP integrations previously always opened with the legacy 2025
initializehandshake, so an SDK v2 server running with its legacy compatibility lane disabled could not connect. Stdio integrations now acceptversionNegotiation: "auto"(onmcp.addServerand the stored config) to probeserver/discoverper spec 2026-07-28, falling back toinitializeon legacy servers. The default stayslegacy: the SDK's stdio probe costs an extra short-lived child process per connect and stalls on silent legacy servers, which is the wrong trade for spawn-per-call CLI servers. The connect handshake span now records the negotiated era (plugin.mcp.protocol_era) so integration authors can verify which handshake a connection used.Updated dependencies [
d3f0617]:@executor-js/plugin-onepassword@1.5.42
Patch Changes
d3f0617]:@executor-js/plugin-openapi@1.5.42
Patch Changes
#1642
32206c7Thanks @RhysSullivan! - Preserve an integration's selected OAuth consent scopes when refreshing converted API specifications, so Google Gmail refreshes do not restore operations that require broader scopes.Updated dependencies [
d3f0617]:@executor-js/plugin-toolkits@1.5.34
Patch Changes
d3f0617]:@executor-js/codemode-core@1.5.42
executor@1.5.42
Patch Changes
d3f0617]:@executor-js/cloud@1.4.60
Patch Changes
d3f0617,86c68af,32206c7,9ecc7cb]:@executor-js/host-selfhost@0.0.41
Patch Changes
d3f0617,32206c7,9ecc7cb]:@executor-js/local@1.5.42
Patch Changes
d3f0617,32206c7,9ecc7cb]:@executor-js/e2e@0.0.39
Patch Changes
d3f0617,32206c7,9ecc7cb]:@executor-js/example-all-plugins@0.0.60
Patch Changes
d3f0617,32206c7,9ecc7cb]:@executor-js/example-docs-sdk-quickstart@0.0.45
Patch Changes
d3f0617,32206c7]:@executor-js/analytics@0.1.6
Patch Changes
@executor-js/api@1.4.62
Patch Changes
d3f0617]:@executor-js/cloudflare@0.0.41
Patch Changes
#1621
86c68afThanks @RhysSullivan! - MCP execution spans now carry the client identity (mcp.client.*)The
clientInfoa client self-reports atinitialize(or in a modern request's_meta) previously existed only on the initialize request itself, which has no session id yet, so execution telemetry could not be segmented by client. Execute, execute-action, and resume spans (and their descendants) now carrymcp.client.name/mcp.client.version/mcp.client.titlealongside the existing session join keys. Cloudflare session Durable Objects persist the reported identity in session meta, so attribution survives cold restores; it feeds telemetry only, never behavior.Updated dependencies [
d3f0617]:@executor-js/mcp-apps-shell@1.4.10
Patch Changes
@executor-js/runtime-workerd-subprocess@0.0.14
Patch Changes
@executor-js/plugin-encrypted-secrets@0.0.41
Patch Changes
d3f0617]:@executor-js/plugin-provider-service-split@0.0.13
Patch Changes
d3f0617,32206c7]:@executor-js/react@1.4.62
Patch Changes
d3f0617]:@executor-js/desktop@1.5.42