From 5555bbe7c9d41224fb446ddb2b5e3c75487bad9d Mon Sep 17 00:00:00 2001
From: Ryan Lewis <ryan@rlew.io>
Date: Sun, 9 Aug 2026 01:40:39 +0100
Subject: [PATCH] docs(release): add v0.5.2 release notes header

---
 .github/releases/v0.5.2.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 .github/releases/v0.5.2.md

diff --git a/.github/releases/v0.5.2.md b/.github/releases/v0.5.2.md
new file mode 100644
index 0000000..08e1336
--- /dev/null
+++ b/.github/releases/v0.5.2.md
@@ -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`).