Repository navigation
Mark local date windows machine-attested - #35
Merged
Merged
Conversation
DTTerastar
approved these changes
Nov 10, 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 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.
Mark local-midnight date-window semantics as machine-attested for all three exporters now that each runs the shared resolved-window check in CI. Update the compatibility documentation to describe the check and its limits.
Evidence: quantcli/crono-export-cli#58, quantcli/liftoff-export-cli#70, and quantcli/withings-export-cli#51 are merged with their compatibility checks green. The test covers reported explicit date bounds; API request and filtering behavior require exporter-specific tests.
Validation:
go test ./...incompat/.