Repository navigation
v0.5.2
things-cli v0.5.2 — timestamps back from 2057
Patch release: one bug fix.
Fixes
creationDateandstopDateare no longer 31 years in the future. Things stores its absolute timestamps (task creation, task and checklist completion) as Unix-epoch seconds, but they were decoded against Apple's Core Data reference date (2001-01-01) — so a task created on 2026-08-09 reported"creationDate": "2057-08-09T…"in--jsonoutput. Anything sorting or filtering on those fields downstream would misbehave. Scheduling fields (startDate,deadline) use a different encoding and were always correct. (#127)
No CLI surface changes — if you parse creationDate/stopDate from --json output, the values are simply right now.
Requirements
macOS with Things3 installed. Binaries for Apple Silicon (darwin_arm64) and Intel (darwin_amd64).
What's Changed
Other Changes
- fix(db): decode creationDate/stopDate as Unix epoch, not Core Data by @ryanlewis in #127
- docs(release): add v0.5.2 release notes header by @ryanlewis in #128
Full Changelog: v0.5.1...v0.5.2