Custom Checkpoint Request Rollout Docs - #614
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
stevensJourney
marked this pull request as ready for review
September 9, 2026 13:50
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Contributor
|
Vale and mintlify link-check results weren't available to this review, so terminology/spelling/link findings from those tools aren't covered here — the comments above focus on technical accuracy and content. |
benitav
reviewed
Sep 9, 2026
benitav
reviewed
Sep 9, 2026
benitav
reviewed
Sep 9, 2026
Co-authored-by: benitav <benitav@users.noreply.github.com>
Co-authored-by: benitav <benitav@users.noreply.github.com>
Co-authored-by: benitav <benitav@users.noreply.github.com>
Collaborator
|
I used this PR to make some other (somewhat related) updates, FYI:
AI usage: Claude Code assisted with the grunt work here. |
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
2 participants
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.
Existing users of custom write checkpoints will most likely need to upgrade to custom checkpoint requests in the future. During an upgrade, developers will probably need to simultaneously cater for older applications which still use legacy custom write checkpoints and newer applications which use checkpoint requests.
On the PowerSync service side, the behaviour for the two share quite a lot of implementation. The main difference is that the newer checkpoint requests are temporary - they are deleted after a period. This is fine since those requests are retried by the client. Legacy write checkpoints are not temporary, they should not be deleted.
The PowerSync service needs some manner to distinguish between the two checkpoint events. This adds docs for that and some general recommendations for rolling out an upgrade to checkpoint_requests.
For context of limitations and implementations, see:
powersyncPR 401AI usage: These docs were generated with the help of Codex 5.6.