Skip to content

docs(release): add v0.5.2 release notes header #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryanlewis merged 1 commit into from
Aug 9, 2026
Merged

docs(release): add v0.5.2 release notes header #128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .github/releases/v0.5.2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
## `things-cli` v0.5.2 — timestamps back from 2057

Patch release: one bug fix.

### Fixes

- **`creationDate` and `stopDate` are 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 `--json` output.
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`).
Loading