diff --git a/.changeset/calm-tools-report-failures.md b/.changeset/calm-tools-report-failures.md deleted file mode 100644 index c153a99ce..000000000 --- a/.changeset/calm-tools-report-failures.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"executor": patch ---- - -Show policy and OAuth app removal failures in the UI, and keep success-only state unchanged when those writes fail. diff --git a/.changeset/emit-return-content.md b/.changeset/emit-return-content.md deleted file mode 100644 index bb7b3b2ee..000000000 --- a/.changeset/emit-return-content.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"executor": patch ---- - -**Fix: `execute` scripts that both `emit()` output and `return` a value no longer lose the returned value in MCP clients that ignore `structuredContent` — the return value is now appended to the tool-result content after the emitted items** diff --git a/.changeset/fix-google-photos-upload-path.md b/.changeset/fix-google-photos-upload-path.md deleted file mode 100644 index bb02c51c0..000000000 --- a/.changeset/fix-google-photos-upload-path.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@executor-js/plugin-openapi": patch ---- - -Use the versioned Google Photos raw upload endpoint so generated upload tools send media to `/v1/uploads` instead of the invalid `/uploads` path. diff --git a/.changeset/handle-deno-stdin-failures.md b/.changeset/handle-deno-stdin-failures.md deleted file mode 100644 index c5c366e12..000000000 --- a/.changeset/handle-deno-stdin-failures.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"executor": patch ---- - -Return an execution error when a Deno subprocess closes stdin instead of emitting an unhandled write failure. diff --git a/.changeset/hosted-dns-guard-latency.md b/.changeset/hosted-dns-guard-latency.md deleted file mode 100644 index 04b9bd9b9..000000000 --- a/.changeset/hosted-dns-guard-latency.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@executor-js/sdk": patch ---- - -Cache hosted outbound DNS guard resolutions, so a proxied request no longer pays a fresh lookup on every hop. `makeHostedHttp` builds the guarded fetch and the guarded HTTP client layer over one cache; building them separately still works but resolves each hostname twice. - -The outbound guard also honors the caller's `redirect` mode, which it previously ignored: `manual` now returns the unfollowed 3xx with its Location header, and `error` rejects, rather than both silently following the redirect. Redirect method semantics now match platform fetch — a `DELETE` or `PUT` meeting a 301/302, and a `HEAD` meeting a 303, keep their method instead of being rewritten to `GET`, so the request the caller made is the request that goes out. Exhausting the redirect budget rejects rather than handing back the raw 3xx as if it were a final response. - -Address classification is tightened too: the cloud metadata endpoint is now blocked by the address a hostname denotes rather than by one dotted-decimal spelling, so its IPv6 forms (`::ffff:169.254.169.254`, the 6to4 `2002:a9fe:a9fe::`, NAT64) are blocked under `allowLocalNetwork` as well, and a name that merely resolves to it is blocked in that mode too — the resolved-address check now runs whether or not the local network is allowed, with only the metadata rule applied to its answers when it is; IPv6 prefixes that carry an IPv4 destination (IPv4-translatable, 6to4, local-use NAT64) are classified by that destination; deprecated site-local addresses (`fec0::/10`) count as local; every address a hostname resolves to is checked rather than the first; subresource integrity survives a cross-origin redirect; and address forms the platform resolver reads differently from a decimal-only parser (octal octets, a dotted quad in the head of a compressed literal) no longer classify as public. diff --git a/.changeset/native-select-dark-mode.md b/.changeset/native-select-dark-mode.md deleted file mode 100644 index d2b9199b7..000000000 --- a/.changeset/native-select-dark-mode.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@executor-js/react": patch ---- - -Keep native `` dropdown options readable in dark mode. The console themes through `prefers-color-scheme` and never sets a `.dark` class, so Tailwind `dark:` utilities never matched and the native option popup rendered with a light color scheme over dark text. `NativeSelect` now uses a solid themed surface (`bg-popover`) and pins `color-scheme` to the active theme, so the browser draws a matching, readable popup. + +- Updated dependencies [[`6a924dd`](https://github.com/UsefulSoftwareCo/executor/commit/6a924dd98de916d6ff8cea2329bf672f149b64f4)]: + - @executor-js/sdk@1.5.38 + - @executor-js/api@1.4.58 + ## 1.4.57 ### Patch Changes diff --git a/packages/react/package.json b/packages/react/package.json index e208e5c3c..f522c8df8 100644 --- a/packages/react/package.json +++ b/packages/react/package.json @@ -1,6 +1,6 @@ { "name": "@executor-js/react", - "version": "1.4.57", + "version": "1.4.58", "private": true, "type": "module", "exports": {