Release 0.5.0 - #61
Merged
Merged
Conversation
Timestamps carry a UTC offset per OKF 62432a0, and staleness is compared as an instant rather than a local calendar day, which is the behavior change behind the minor bump. The notes state both directions of the staleness shift, that `validate --strict` begins failing on date-only timestamps that used to pass, and that migrating a date-only `verified.at` can raise a concept's trust_tier. Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Cuts 0.5.0 for the two timestamp changes now on
main(#59, #60).stale_afteris compared as an instant rather than as a calendar date in thecaller's local zone. That is the behavior change behind the minor bump, and the
notes give it in both directions: east of UTC a concept goes stale later than it
used to, and west of UTC it can become stale on the previous local day.
Measured on this branch rather than reasoned about:
okf validateexits 0 andokf validate --strictexits 1 on the samedate-only bundle.
isConformantis unchanged, so the compatibility promiseholds everywhere except
--strict; the notes say so and point atokf format --migrate-timestamps.verified.atraisestrust_tierfromunverifiedtohuman-reviewedinokf graph, because the verification gains a usable time.Documented, since it changes output a consumer may key on.
--migrate-timestamps --checkexits 1 and leaves the file byte-identical.2026-02-30used to parse as March 2 and now does not parse at all.Version is mirrored in
pubspec.yaml,lib/src/version.dart, the README actionpin and the changelog heading, which
test/ci/gate_test.dartenforces.Made with Cursor