History

Release notes + changeset for 1.4.17 (#753)

Rhys Sullivan committed 6 months ago

Commit 66889ee1 parent 7f2413f2 files · +6 −93Browse files

Unified · Split

2 files
  1. .changeset/executor-1.4.17.md +5 −0
  2. apps/cli/release-notes/next.md +1 −93
.changeset/executor-1.4.17.md+5−0
@@ -0,0 +1,5 @@
1---
2"executor": patch
3---
4
5List 1Password vault items in the secrets list without requiring a prior bind. See `apps/cli/release-notes/next.md`.
apps/cli/release-notes/next.md+1−93
@@ -1,95 +1,3 @@
1## Highlights
2
3### Unified credential bindings
4
5Source credentials (OAuth tokens, header secrets, client-credential pairs) are now stored as **scoped credential bindings** instead of plugin-specific shapes. Two consequences for users:
6
7- One consistent UI for editing credentials across OpenAPI, MCP, and GraphQL sources. The old per-plugin credential forms are gone, replaced with a shared slot UI in `@executor-js/react` (`credential-bindings`, `credential-slot-bindings`, `oauth-sign-in`).
8- Existing OpenAPI / MCP / GraphQL / google-discovery credentials are migrated into the new binding rows automatically on first launch (drizzle migrations `0007`, `0008`, `0010` for `apps/local`). No user action required.
9
10### See where a secret or connection is used
11
12A new `executor.usages` surface lets plugins declare every place they reference a secret or connection. The local UI uses it to:
13
14- Show a "used in N sources / M bindings" summary on the secret detail page.
15- Surface a clear "this secret is in use, remove the references first" toast (backed by the new `SecretInUseError` / `ConnectionInUseError`) instead of letting the delete fail silently.
16
17Plugin authors implement `usagesForSecret` / `usagesForConnection`; the executor fans out and concatenates.
18
19### MCP source detection works on more servers
20
21Adding an MCP source now succeeds against servers that previously failed to probe.
22
23- Bearer-auth MCP servers are detected on the initial probe instead of being misclassified as plain HTTP. Probe error messages also tell you what shape of auth challenge came back.
24- 401 challenges that advertise `resource_metadata=` are recognized as MCP-spec OAuth signals.
25- Probes accept RFC 6750-compliant body forms for the access-token check, so servers that don't honor the `Authorization` header on the probe path still discover correctly.
26- A live-snapshot regression suite covers 29 real public MCP servers; new probes are checked against those snapshots before shipping.
27- The MCP connection pool now keys by source identity, so two MCP sources pointing at the same upstream URL with different credentials no longer collide on one shared connection.
28
29### TypeScript code runs in dynamic-worker and QuickJS runtimes
30
31Both runtimes strip TypeScript syntax before evaluation, so tools that pass TS source (annotations, `as` casts, type aliases, etc.) execute without a separate compile step. Previously you had to hand-strip types or precompile.
32
33### OpenAPI source UX
34
35- Source-add screens reworked: cleaner flow, the freeform combobox lists the URL you typed first, scoped credential UI clarified.
36- OpenAPI import size limit removed — large specs (Stripe, GitHub, etc.) import without truncation.
37- The OpenAPI source edit page lets you change the OAuth2 token / authorization endpoint URLs without removing and re-adding the source.
38- Source favicons render again on the sources list (regression from the source-credential cutover).
39- `listSourceBindings` no longer 500s when called after a source has been removed.
40
41### OAuth reliability
42
43A pile of small fixes to the OAuth flow, individually unspectacular, collectively meaning fewer mysterious "Sign in" failures:
44
45- DCR registration declares the requested scopes in the body so providers that key on body-scope (rather than `scope=` on the auth URL) issue refresh tokens with the right grants.
46- Refresh requests use the exact scopes from the original token grant; servers that reject scope upgrades on refresh stop returning `invalid_scope`.
47- `id_token` values returned alongside an access token are stripped before validation (some providers send malformed JWTs in this slot, which used to fail the whole exchange).
48- The `scope` parameter is omitted entirely when empty, instead of being sent as `scope=`.
49- OAuth endpoint URLs from discovery / DCR are validated; obviously-broken metadata fails fast with a clear message rather than later in the popup. Exposed as `assertSupportedOAuthEndpointUrl` / `isSupportedOAuthEndpointUrl` for plugin use.
50- Token-endpoint failures now include the upstream HTTP status + body summary in the surfaced error.
51- Popup handling: the popup is reserved before the start request fires, and close events are detected reliably, so cancelling sign-in no longer leaves the UI stuck waiting.
52
53### Source-registration tools require approval
54
55Tools that register new sources (e.g. `addSource` on the OpenAPI plugin) now go through the standard approval gate by default, the same way destructive tools do. Safer to point an agent at a workspace that has source-mutating tools available.
56
57### Migration safety for older CLI builds
58
59If an older `executor` build opens a data directory that has been migrated by a newer build, you now get an explicit "this data directory was created by a newer version" error instead of a low-level SQLite schema mismatch crash. Drizzle migration preflight checks were also tightened so partially-applied migrations are caught earlier.
60
61### SDK additions
62
63For plugin authors and embedders:
64
65- `Usage`, `UsagesForSecretInput`, `UsagesForConnectionInput` — the usages contract.
66- `CredentialBindingKind`, `CredentialBindingValue`, `ConfiguredCredentialBinding`, `ConfiguredCredentialValue`, `ScopedSecretCredentialInput`, `CredentialBindingRef`, `SetCredentialBindingInput`, `RemoveCredentialBindingInput`, `ReplaceCredentialBindingsInput`, `ResolvedCredentialSlot`, `CredentialBindingId` — the new credential bindings surface.
67- `SecretInUseError`, `ConnectionInUseError` — typed errors for blocked deletes.
68- `RefreshSourceInput`, `RemoveSourceInput`, `RemoveSecretInput`, `RemoveToolPolicyInput`, `CredentialBindingRow` — new typed inputs / row types.
69- `ScopedDBAdapter`, `ScopedTypedAdapter` — type exports for scope-aware storage adapters.
70- Plugin `clientConfig` is threaded through `vite-plugin` into the client bundle, so plugins can hand SDK-side config to their React surface without a separate config endpoint.
71- Schema compile perf: a new lint rule + hoisted `Schema` compilers keep parse-paths fast.
72
73## Fixes1## Fixes
74 2
75- `executeWithPause` now settles correctly when the running fiber fails — previously a fiber failure could leave the execution hanging instead of surfacing the error. (#523)3- 1Password vault items now appear in the secrets list without first being bound. `executor.secrets.list()` fans out to each provider's `list()` after collecting core routing rows, so read-only providers (1Password, file-secrets, workos-vault) surface their inventory directly. Core rows still win on id collisions; connection-owned ids stay hidden.
76- `isDevMode` correctly identifies the compiled bun binary, so installed CLI builds no longer misdetect themselves as running from source. Thanks @grfwings (#699)
77- Drizzle migration handling parses migration metadata with a typed schema and reports outdated-client failures cleanly. Thanks @grfwings (#741)
78- Frontend errors and API-client decode failures are now reported through the existing error-reporting path instead of being swallowed silently.
79- Source forms keep local error messages on screen instead of clearing them on the next render.
80- "Remove in-use source" surfaces a toast instead of a silent failure. (#530)
81
82## Breaking changes
83
84### SDK: `makeTestConfig` import path moved
85
86The deep import path moved from `@executor-js/core/sdk/testing` to `@executor-js/core/sdk/test-config`. The package-root re-export is unchanged:
87
88```ts
89// still works
90import { makeTestConfig } from "@executor-js/core/sdk";
91```
92
93### SDK: per-plugin credential shapes replaced by credential bindings
94
95If you authored a plugin that stored OAuth tokens or other credentials directly under a plugin-specific column, migrate to the unified `CredentialBinding*` surface. The in-tree plugins (OpenAPI, MCP, GraphQL, google-discovery) have all been ported — see them for reference. End users of the CLI / web UI are unaffected; existing rows migrate automatically.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t