Version Packages - #1804
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 9b80713 | Commit Preview URL Branch Preview URL |
Aug 28 2026, 07:06 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 9b80713 | Aug 28 2026, 07:08 AM |
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: |
RhysSullivan
force-pushed
the
changeset-release/main
branch
from
August 28, 2026 06:36
f0d9d18 to
0eaeb32
Compare
RhysSullivan
force-pushed
the
changeset-release/main
branch
from
August 28, 2026 07:04
0eaeb32 to
9b80713
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/cli@0.2.52
Patch Changes
@executor-js/config@1.6.2
Patch Changes
@executor-js/execution@1.6.2
Patch Changes
@executor-js/vite-plugin@0.0.62
Patch Changes
@executor-js/runtime-quickjs@1.6.2
Patch Changes
@executor-js/plugin-desktop-settings@1.6.2
Patch Changes
@executor-js/plugin-example@1.6.2
Patch Changes
@executor-js/plugin-file-secrets@1.6.2
Patch Changes
@executor-js/plugin-graphql@1.6.2
Patch Changes
@executor-js/plugin-keychain@1.6.2
Patch Changes
@executor-js/plugin-mcp@1.6.2
Patch Changes
@executor-js/plugin-onepassword@1.6.2
Patch Changes
@executor-js/plugin-openapi@1.6.2
Patch Changes
@executor-js/plugin-toolkits@1.5.37
Patch Changes
@executor-js/sdk@1.6.2
@executor-js/codemode-core@1.6.2
executor@1.6.2
Patch Changes
#1802
2afb6e8Thanks @RhysSullivan! - Concurrent API requests no longer share one database provider buildEvery HTTP request gets its own database connection, opened when the request fiber's scope opens and closed when it closes. The middleware that builds a request's execution stack, however, captures the boot fiber's context once at layer-construction time and re-applies it to every request. A captured context carries Effect's current memoization map, and re-applying it replaced the fresh per-request map with the boot one — which every in-flight request in the isolate shares.
The per-request stack build then memoized itself there. Sequential requests still rebuilt, because the memo entry is released once the request that built it finishes, so the problem was confined to requests that overlap: the second request reused the first one's stack build, and with it the first one's database connection. A request could therefore issue queries on a connection it did not own, and lose that connection mid-flight when the owner finished and closed it — typically surfacing as a failed read after a slow outbound call, on a request that had already read successfully.
The stack is now built with a request-local memoization scope, so overlapping requests each build their own stack over their own connection. The captured context still carries the long-lived services it exists to carry. The two other per-request provider builds that ran under a captured context — the account provider and the admin-users provider — are built the same way, for the same reason.
#1807
78311a1Thanks @RhysSullivan! - Desktop: restore the macOS signing entitlements and app icon that were accidentally removed from the build inputs, and fail fast at PR time and before publishing when any configured build resource is missing. The v1.6.1 desktop build could not be signed; this release supersedes it.Updated dependencies []:
@executor-js/cloud@1.4.63
Patch Changes
@executor-js/host-selfhost@0.0.44
Patch Changes
@executor-js/local@1.6.2
Patch Changes
@executor-js/e2e@0.0.42
Patch Changes
@executor-js/example-all-plugins@0.0.63
Patch Changes
@executor-js/example-docs-sdk-quickstart@0.0.48
Patch Changes
@executor-js/analytics@0.1.9
Patch Changes
@executor-js/api@1.4.65
Patch Changes
@executor-js/cloudflare@0.0.44
Patch Changes
@executor-js/mcp-apps-shell@1.4.13
Patch Changes
@executor-js/runtime-workerd-subprocess@0.0.17
Patch Changes
@executor-js/plugin-encrypted-secrets@0.0.44
Patch Changes
@executor-js/plugin-provider-service-split@0.0.16
Patch Changes
@executor-js/react@1.4.65
Patch Changes
@executor-js/desktop@1.6.2