chore: publish new package versions - #4766
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
from
August 20, 2026 22:38
02dbdc1 to
9eb803f
Compare
alco
approved these changes
Aug 20, 2026
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
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
@core/sync-service@1.7.12
Patch Changes
ELECTRIC_DATABASE_TCP_KEEPALIVE_IDLE,ELECTRIC_DATABASE_TCP_KEEPALIVE_INTERVAL,ELECTRIC_DATABASE_TCP_KEEPALIVE_COUNTandELECTRIC_DATABASE_TCP_USER_TIMEOUTfor configuring TCP keepalive and user timeout on database connections. All of them are opt-in; when unset the OS defaults are kept./v1/shapein secure mode. Authentication now gates on the route resolved by the router rather than on the raw request path, so requests whose target normalizes to/v1/shape(e.g. a trailing slash, a doubled slash, or a percent-encoded character) can no longer skip the secret check. CORS headers for shape routes are matched the same way.