Version Packages#1200
Merged
Merged
Conversation
RhysSullivan
force-pushed
the
changeset-release/main
branch
from
b2ca44e to
3beb213
Compare
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 2ab16a4 | Jun 29 2026, 01:28 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 2ab16a4 | Commit Preview URL Branch Preview URL |
Jun 29 2026, 01:27 AM |
Greptile SummaryAutomated changeset release PR bumping versions across the monorepo and updating all CHANGELOG files. It also includes two minor documentation edits:
Confidence Score: 5/5Safe to merge — all changes are changeset-generated version bumps, CHANGELOG entries, lockfile updates, and minor documentation reformatting with no functional code changes. Every changed file is either a package.json version field, a CHANGELOG entry, a bun.lock workspace record, a deleted changeset file, or a documentation-only edit. The deliberate skip of @executor-js/cli 0.2.29 (republish-locked) is correctly reflected in the package.json and CHANGELOG; the only discrepancy is the PR description title still saying 0.2.29. packages/core/cli/CHANGELOG.md and packages/core/cli/package.json — verify that consumers are aware 0.2.29 does not exist and 0.2.30 is the next published version. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
CS[Changesets consumed] --> VB[Version bumps across 30+ packages]
VB --> CORE["Core packages<br/>sdk@1.5.23 · api@1.4.43 · react@1.4.43<br/>execution@1.5.23 · config@1.5.23"]
VB --> CLI["@executor-js/cli<br/>0.2.28 → 0.2.30<br/>(0.2.29 republish-locked, skipped)"]
VB --> PLUGINS["Plugins<br/>graphql@1.5.23 · openapi@1.5.23<br/>mcp@1.5.23 · google@1.5.22 · …"]
VB --> APPS["Apps<br/>executor@1.5.23 · cloud@1.4.41<br/>desktop@1.5.23 · host-selfhost@0.0.22"]
CORE --> LOCK[bun.lock updated]
CLI --> LOCK
PLUGINS --> LOCK
APPS --> LOCK
CS --> DOCS[Docs edits<br/>e2e/AGENTS.md · vision.md]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
CS[Changesets consumed] --> VB[Version bumps across 30+ packages]
VB --> CORE["Core packages<br/>sdk@1.5.23 · api@1.4.43 · react@1.4.43<br/>execution@1.5.23 · config@1.5.23"]
VB --> CLI["@executor-js/cli<br/>0.2.28 → 0.2.30<br/>(0.2.29 republish-locked, skipped)"]
VB --> PLUGINS["Plugins<br/>graphql@1.5.23 · openapi@1.5.23<br/>mcp@1.5.23 · google@1.5.22 · …"]
VB --> APPS["Apps<br/>executor@1.5.23 · cloud@1.4.41<br/>desktop@1.5.23 · host-selfhost@0.0.22"]
CORE --> LOCK[bun.lock updated]
CLI --> LOCK
PLUGINS --> LOCK
APPS --> LOCK
CS --> DOCS[Docs edits<br/>e2e/AGENTS.md · vision.md]
Reviews (2): Last reviewed commit: "Skip @executor-js/cli 0.2.29 (republish-..." | Re-trigger Greptile |
0.2.29 was published then unpublished during the 2.0.0 rollback, so npm blocks republishing that exact version for 24h. Bump @executor-js/cli to 0.2.30 so the patch release publishes cleanly.
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.29
Patch Changes
@executor-js/config@1.5.23
Patch Changes
@executor-js/execution@1.5.23
Patch Changes
@executor-js/vite-plugin@0.0.40
Patch Changes
@executor-js/runtime-quickjs@1.5.23
Patch Changes
@executor-js/plugin-desktop-settings@1.5.23
Patch Changes
@executor-js/plugin-example@1.5.23
Patch Changes
@executor-js/plugin-file-secrets@1.5.23
Patch Changes
@executor-js/plugin-google@1.5.22
Patch Changes
29936d5,29936d5]:@executor-js/plugin-graphql@1.5.23
Patch Changes
#1199
29936d5Thanks @RhysSullivan! - Fix the GraphQL plugin generating invalid operations against large schemas, and make field selection caller-controlled instead of a baked-in guess.Previously each tool froze a recursive, depth- and count-bounded selection at sync time. Against a rich schema (GitLab) this produced invalid GraphQL (composite fields with no sub-selection, nested fields missing required arguments) so every call over a rich return type failed, and the arbitrary bound silently truncated which fields came back.
Generated tools now default to selecting only scalar/enum leaf fields of the return type (always valid, always within a server's query-complexity budget), and expose an optional
selectinput carrying a GraphQL selection set so a caller can request nested or list data per call (including supplying nested required arguments). Fixes #1146.Updated dependencies [
29936d5,29936d5]:@executor-js/plugin-keychain@1.5.23
Patch Changes
@executor-js/plugin-mcp@1.5.23
Patch Changes
29936d5,29936d5]:@executor-js/plugin-microsoft@1.5.22
Patch Changes
29936d5,29936d5]:@executor-js/plugin-onepassword@1.5.23
Patch Changes
29936d5,29936d5]:@executor-js/plugin-openapi@1.5.23
Patch Changes
29936d5,29936d5]:@executor-js/plugin-toolkits@1.5.15
Patch Changes
29936d5,29936d5]:@executor-js/sdk@1.5.23
@executor-js/codemode-core@1.5.23
executor@1.5.23
Patch Changes
#1199
29936d5Thanks @RhysSullivan! - Add a test seam to skip the first-run "keep Executor running in the background?" consent dialog under automation, matching the existingconfirmResetStateseam. SetEXECUTOR_TEST_AUTO_CONFIRM_BACKGROUND_SERVICE=1to keep the background service or any other value to decline. When the variable is unset the dialog is shown exactly as before. Native dialogs cannot be answered from CDP or Playwright, so a packaged first-run boot under automation previously blocked at this prompt with no way to proceed.#1199
29936d5Thanks @RhysSullivan! - Fix the desktop app failing to start its local server when the generated auth token begins with a dash. The token israndomBytes(32).toString("base64url"), which can start with "-", and the packaged app passed it to the bundled CLI as a separate argument (--auth-token, then the token). The CLI then read the leading-dash token as an unknown flag, printed its help, and exited, so the desktop showed a fatal "local Executor server crashed during startup" dialog. This was persistent (the token is saved) and cross-platform, affecting roughly 1 in 64 fresh installs. The token is now passed in the combined--auth-token=<value>form so a leading dash is treated as the value.#1199
29936d5Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.Updated dependencies [
29936d5,29936d5]:@executor-js/cloud@1.4.41
Patch Changes
29936d5,29936d5,29936d5]:@executor-js/desktop@1.5.23
Patch Changes
29936d5Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.@executor-js/host-selfhost@0.0.22
Patch Changes
29936d5,29936d5,29936d5]:@executor-js/e2e@0.0.20
Patch Changes
29936d5,29936d5,29936d5]:@executor-js/example-all-plugins@0.0.41
Patch Changes
29936d5]:@executor-js/example-docs-sdk-quickstart@0.0.26
Patch Changes
@executor-js/api@1.4.43
Patch Changes
#1199
29936d5Thanks @RhysSullivan! - Fix OAuth "Mismatching redirect URI" for org-scoped client-id metadata documentsOrg-scoped client-id metadata documents registered their callback as
redirect_uriwith anexecutor_orgquery param, but the client always sendsthe bare callback and the org is carried in the OAuth
state. Providers thatcompare
redirect_urias an exact string (such as PostHog) rejected theauthorize request. Org targets now keep their distinct
client_idURL butregister the same bare callback
redirect_urias every other target.#1199
29936d5Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.Updated dependencies []:
@executor-js/cloudflare@0.0.22
Patch Changes
29936d5,29936d5]:@executor-js/plugin-encrypted-secrets@0.0.22
Patch Changes
@executor-js/react@1.4.43
Patch Changes
#1199
29936d5Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.Updated dependencies [
29936d5,29936d5]: