chore: publish new package versions - #4645
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
8 times, most recently
from
June 25, 2026 16:04
c21d938 to
5be4d94
Compare
✅ 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
from
June 25, 2026 19:16
5be4d94 to
fe10e07
Compare
KyleAMathews
approved these changes
Jun 25, 2026
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
had a problem deploying
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Failure
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
KyleAMathews
temporarily deployed
to
Pull request
June 25, 2026 19:24 — with
GitHub Actions
Inactive
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.6.3
Patch Changes
@electric-ax/agents-runtime@0.6.3
Patch Changes
886c423: Context compaction for the agents runtime. Modelled on OpenAI Codex's
summarization but adapted to the event-sourced timeline (a
context_insertedcheckpoint placed at a stored watermark, so reconstruction folds older messages
into a summary):
context_input_tokens+context_windowpersisted per step) and<token_budget>notices injected at25 / 50 / 75% usage.
at the 90% hard ceiling (runs before every model step via the adapter's
transformContexthook).summarize whose checkpoint is applied at the next turn's start, or immediately
if it finishes while idle. Each generation uses a watermark-unique checkpoint
id so a new run can't supersede a prior completed one. Summarize calls are
bounded by a hard timeout.
"Context compacted" entry in the conversation timeline.
Thresholds are env-tunable (
ELECTRIC_AGENTS_COMPACT_CEILING,ELECTRIC_AGENTS_COMPACT_BG_CEILING).7139c53: Context-usage indicator: a circular ring gauge plus a hover breakdown popover
showing how the prompt decomposes across system prompt, tools, messages, and
free space (à la Claude Code's
/context). The runtime now persists anapproximate
context_breakdownof the stable request parts (system + tools) oneach step alongside the cache-inclusive total, and exports new
computeContextBreakdown/parseContextBreakdownhelpers from the cliententry; the UI derives the "messages" bucket as the real remainder so the
segments always sum to the gauge.
@electric-ax/agents-server@0.6.3
Patch Changes
electric-ax@0.2.23
Patch Changes
@electric-sql/experimental@6.0.22
Patch Changes
@electric-sql/react@1.0.51
Patch Changes
@electric-sql/client@1.5.22
Patch Changes
AbortSignal.reason, such as some React Native fetch/AbortController implementations.@electric-sql/y-electric@0.1.48
Patch Changes
@electric-ax/example-agents-chat-starter@0.1.14
Patch Changes
@electric-ax/example-agents-walkthrough@0.1.11
Patch Changes
@electric-ax/example-deep-survey@0.1.30
Patch Changes
expo-db-electric-starter@1.0.23
Patch Changes
@electric-ax/agents-mobile@0.6.3
Patch Changes
@electric-ax/agents-server-ui@0.6.3
Patch Changes
886c423: Context compaction for the agents runtime. Modelled on OpenAI Codex's
summarization but adapted to the event-sourced timeline (a
context_insertedcheckpoint placed at a stored watermark, so reconstruction folds older messages
into a summary):
context_input_tokens+context_windowpersisted per step) and<token_budget>notices injected at25 / 50 / 75% usage.
at the 90% hard ceiling (runs before every model step via the adapter's
transformContexthook).summarize whose checkpoint is applied at the next turn's start, or immediately
if it finishes while idle. Each generation uses a watermark-unique checkpoint
id so a new run can't supersede a prior completed one. Summarize calls are
bounded by a hard timeout.
"Context compacted" entry in the conversation timeline.
Thresholds are env-tunable (
ELECTRIC_AGENTS_COMPACT_CEILING,ELECTRIC_AGENTS_COMPACT_BG_CEILING).7139c53: Context-usage indicator: a circular ring gauge plus a hover breakdown popover
showing how the prompt decomposes across system prompt, tools, messages, and
free space (à la Claude Code's
/context). The runtime now persists anapproximate
context_breakdownof the stable request parts (system + tools) oneach step alongside the cache-inclusive total, and exports new
computeContextBreakdown/parseContextBreakdownhelpers from the cliententry; the UI derives the "messages" bucket as the real remainder so the
segments always sum to the gauge.
Updated dependencies [886c423]
Updated dependencies [7139c53]
@core/sync-service@1.7.4
Patch Changes
shape_snapshot.execute_for_shapeandshape_snapshot.query_fnspans formove_in_queryoperations. Previously these spans were silently dropped because the spawned move-in task had no parent span context, andwith_child_spanskips emission when no parent exists. Ashape_snapshot.move_in_taskroot span is now opened inside the task (mirroringshape_snapshot.create_snapshot_taskfor initial snapshots) so the existing child spans are emitted withshape.query_reason="move_in_query".whose where clause contains a subquery (e.g.
id IN (SELECT ... WHERE active))could return stale results or a
409 must-refetchonce the stack restarted andrestored from disk. Two causes are addressed: the dependency materializer now
replays the full persisted history (snapshot + main log) on startup instead of
just the first chunk, and dependent (outer) subquery consumers are eagerly
restarted during restore so their materializer subscription is re-established
before live events flow.
rows that back subquery routing and exact membership repeated several boxed
terms in their keys — the shape handle,
make_ref/0condition references, thecanonical
["$sublink", "<dep>"]subquery ref, and the{condition_id, field}node id. Each of those is now a compact integer id, leaving only the actual
typed value boxed. This cuts the cost per seeded subquery membership value by
~51% (e.g. ~568 MiB → ~275 MiB for 1,000,000 seeded values) with no change to
routing behaviour.
replication slot. Previously, when Electric purged all shapes after the
replication slot was (re)created — e.g. a temporary slot recreated on restart
with
CLEANUP_REPLICATION_SLOTS_ON_SHUTDOWN=true— the persisted relationtracking (
tracked_relations) and the inspector cache (ets_inspector_state)survived and were read back on startup, even though WAL continuity had been
lost. These caches are now reset as part of the same purge, so no stale
pre-restart metadata is reused.