This repository was archived by the owner on Nov 8, 2026. It is now read-only.
Repository navigation
Validate record outcomes without public revision tokens - #30
Merged
Merged
Conversation
This was referenced Sep 20, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Public record results no longer expose storage revisions. Verify statuses, persisted documents, returned counter values, and backend commit counts instead, while retaining adapter-level revision and conflict coverage.
Validated integration-tagged compilation against the updated local SDK and server test overlay; live backend tests were not run locally. Companion changes: batchstream/sink#115 and batchstream/sink-go#26.