Repository navigation
chore: publish new package versions - #4318
Merged
Merged
Conversation
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
May 13, 2026 09:06
72e89d8 to
572146d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
May 13, 2026 09:31
572146d to
10b8e59
Compare
icehaunter
approved these changes
May 13, 2026
This branch was previously deployed
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
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 the packages will be published to npm 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
@electric-ax/agents@0.4.0
Minor Changes
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....Patch Changes
dec65ae: Do not register a built-in pull-wake runner as the default dispatch policy for built-in agent entity types.
08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [08e85a0]
@electric-ax/agents-runtime@0.2.0
Minor Changes
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Patch Changes
@electric-ax/agents-server@0.4.0
Minor Changes
dec65ae: Add tenant-scoped Durable Streams bearer auth for agents-server library hosts.
Tenant runtimes and request contexts can now provide a static bearer token or a
zero-argument token provider for downstream Durable Streams requests.
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Patch Changes
d8cb2bb: Fix Docker build by adding missing
agents-mcppackage to the Dockerfile.443482a: Prepare the agents server and server conformance test packages for public npm publication.
The agents server package now publishes its Drizzle migration files alongside the built entrypoints so installed servers can run database migrations outside the monorepo.
dec65ae: Fix shared multi-tenant scheduler queries to bind tenant id filters as typed
Postgres text arrays.
Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [08e85a0]
electric-ax@0.2.0
Minor Changes
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....Patch Changes
08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [08e85a0]
@electric-ax/agents-mcp@0.2.1
Patch Changes
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....@electric-ax/agents-server-conformance-tests@0.1.3
Patch Changes
443482a: Prepare the agents server and server conformance test packages for public npm publication.
The agents server package now publishes its Drizzle migration files alongside the built entrypoints so installed servers can run database migrations outside the monorepo.
08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
@electric-ax/agents-server-ui@0.4.0
Minor Changes
08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Patch Changes
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [08e85a0]
@electric-ax/example-deep-survey@0.1.8
Patch Changes
08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [08e85a0]
@electric-ax/agents-desktop@0.1.1
Patch Changes
dec65ae: Send stable asserted user headers from the desktop app and align pull-wake runner registration with the effective request identity.
dec65ae: Port pull-wake runners onto the tenant-aware agents-server routing refactor.
Agents-server now supports runner registration, runner-owned pull-wake subscriptions, dispatch policy resolution, subscription stream linking, compact Durable Streams wake claims, callback-forward claim lifecycle handling, and claim-scoped write tokens. Runtime built-ins can register pull-wake runners, tail runner wake streams, claim work through the server, heartbeat offsets, and acknowledge completed work. The CLI, desktop integration, server UI, and local full-stack compose setup now use asserted identity and runner-backed local sessions for the pull-wake flow.
Saved agents-server connections can include additional request headers for tenant-aware deployments, and CLI/runtime URL handling now preserves base query parameters such as
?secret=....08e85a0: Refactor agents-server HTTP routing around a single
globalRouterentrypoint passed a flatTenantContext.The
ElectricAgentsServerclass now owns lifecycle setup only and dispatches each request through an OSS-only wrapper router that layers dashboard and mock-agent routes overglobalRouter.fetch(request, tenantContext). This prepares the exportedglobalRouterfor library-mode use by callers that build tenant context outside the OSS server class without pulling in the bundled UI or mock agent.Breaking change: entity RPC URLs moved from
/:type/:instanceId/...to/_electric/entities/:type/:instanceId/.... This affects entity spawn/get/head/delete, send, fork, tag, and schedule endpoints. The root namespace is now durable-streams pass-through, with no reserved entity control routes.Breaking change: the
@electric-ax/agents-serverpackage root now only exports the library-mode routing assembly surface: DB setup helpers,AgentsHost,StreamClient,globalRouter,TenantContext,GlobalRoutes,EntityBridgeCoordinator, and tenant helpers. OSS server classes, subrouters, entity-manager internals, scheduler/wake-registry internals, schema helpers, and entity response helpers are no longer root exports.The runtime server client, bundled agents-server UI, and conformance tests have been updated for the new route layout. Agents-server control-plane routes now use shared TypeBox/Ajv body validation.
Updated dependencies [dec65ae]
Updated dependencies [dec65ae]
Updated dependencies [08e85a0]
@core/sync-service@1.6.4
Patch Changes
c38e519: Fix a 2-cycle infinite refetch loop on
live=true&live_sse=trueshape requests caused by a non-monotonicelectric-cursorheader.Electric.Plug.Utils.get_next_interval_timestamp/2could return a cursor smaller than theprev_intervalthe client sent: when the client polled with a previously-jittered value (bucket + delta,delta ∈ 1..3_600) and the wall clock had not yet crossed that value, the function fell through to the plain bucket value and returned a cursor below the client's. Combined withCache-Control: public, max-age=<sse_timeout - 1>on live SSE responses (added intentionally to enable CDN request collapsing), two cached entries could end up pointing at each other:?cursor=A→electric-cursor: B, and?cursor=B→electric-cursor: A. Once both entries were warm, the client would bounce between them at line rate (>600 req/s) until the cache window expired, all within the originalmax-agewindow.get_next_interval_timestamp/2now guarantees that the returned cursor is strictly greater thanprev_interval— when bucket math would return a value<= prev, the function jitters strictly forward fromprevinstead.This is a server-side-only fix; clients on any current version recover automatically once existing CDN-cached cycle entries age out (≤
sse_timeout).