chore: publish new package versions#4689
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
754c2e8 to
7d023d3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
7d023d3 to
498f4d2
Compare
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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-sql/experimental@6.0.24
Patch Changes
@electric-sql/react@1.0.53
Patch Changes
@electric-sql/client@1.5.24
Patch Changes
require('react-native')auto-detection while keepingruntimeVisibilityas an explicit escape hatch.@electric-sql/y-electric@0.1.50
Patch Changes
expo-db-electric-starter@1.0.25
Patch Changes
@electric-ax/durable-streams-server-rust@0.1.4
Patch Changes
640509c: Write-path performance overhaul plus three crash-recovery correctness fixes.
Performance: removed the WAL group-commit coordination ceiling (+55–60% saturated write throughput, p99 41→12 ms), fixed the 200k–1M stream-cardinality write cliff (1M streams now sustains 1.11M ops/s on 16 vCPU), and made
--durability memorythe buffered append path (4× faster, no longer Linux-only). New flags:--wal-stats <secs>and--worker-threads <n>.Fixes (found by the new seeded crash/fault simulation): multi-segment WAL recovery no longer drops acked records after the first segment; a torn, never-acked tail on a quiet stream is truncated instead of becoming reader-visible; an acked DELETE is now durable before the 204.
@core/electric-telemetry@0.3.3
Patch Changes
ELECTRIC_DROP_EMPTY_RESPONSE_SPANS=trueto enable the drop. Error (5xx) and SSE responses are never dropped.@core/sync-service@1.7.7
Patch Changes
ELECTRIC_DROP_EMPTY_RESPONSE_SPANS=trueto enable the drop. Error (5xx) and SSE responses are never dropped.