chore: publish new package versions #2639
Merged
Conversation
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
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
github-actions
bot
force-pushed
the
changeset-release/main
branch
16 times, most recently
from
b39344f to
ada0741
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
223c1a2 to
fff7225
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
fff7225 to
4f82bcd
Compare
🫡
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
@core/elixir-client@0.4.0
Minor Changes
@core/sync-service@1.0.12
Patch Changes
8c52956: Fix: properly handle more connection-related edge cases. Streamline error reporting in stack events.
7f01303: Lower severity of expected lock acquisition errors
4ad1d0f: Mitigate
EEXISTerror onrm_rfdue to suspected filesystem race with retries.c66b869: Use non-pooled connection for grabbing advisory lock to avoid unexpected behaviour.
a00e863: fix: ensure continued replication (via shape reset) when WAL slot size is exceeded
55aef88: Fix handling of some connections errors. Treat "wal_level != logical" as a fatal error after which there's no point in retrying the connection.
c82153d: fix: make sure a split PK update is visible in the read log when it's in the last position in the transaction
575a6fa: fix: load instance_id from opts for configuring application_telemetry
79d769a: Electric will now shut down and provide an error message if there is a critical error connecting to the database
such as the database or domain not existing.
The API will now return more helpful error messages if Electric is having issues connecting to the database.
c7bde30: Add stack events for when timeline change is detected and when the database connection shuts down.
7fa69ac: fix: don't send a 500 on a shape delete race condition