dsh-global-todo 0.16.0 → 0.16.1

package/CHANGELOG.md

@@ -1,3 +1,15 @@
+## [0.16.1] — 2026-10-22
+
+Same code as 0.16.0; the tag now points at a commit whose CI is green.
+
+- **0.16.0's tag commit had all three CI jobs red.** The new `before:`/`after:` test asserted the
+  order of two todos created in the same test, and CI creates them in the same millisecond, so the
+  order it asserted was not the order the default sort produces. The behaviour under test was
+  correct; the assertion was wrong. Fixed in 8024a48 — the run after it is green on both platforms.
+- **Why a release rather than a moved tag**: `v0.16.0` is published on npm, and a tag that no
+  longer matches what was published is worse than a version bump. 0.16.1 is 0.16.0 plus the
+  assertion, so its tag has a green check.
+
 ## [0.16.0] — 2026-10-22
 
 The three small promises the roadmap still carried.

package/lib/index.js

@@ -37,7 +37,7 @@ import { createStore, resolveStorePath } from './store.js'
 import { createTools, normalizeToolGroups, selectTools } from './tools.js'
 
 /** Must equal `package.json`'s version; `npm run check` enforces that. */
-export const VERSION = '0.16.0'
+export const VERSION = '0.16.1'
 
 /** Plugin id. Also the Loader row id in `cordis.patch.yml`. */
 export const name = 'dsh-global-todo'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-global-todo",
-  "version": "0.16.0",
+  "version": "0.16.1",
   "icon": "./docs/icon.svg",
   "description": "Cross-session todo list for DeepSeek Harness: one JSON file a person and an agent both write to, with step plans that ship as a numbered hand-off, session read-back, and a human confirmation before an agent's \"done\" counts.",
   "type": "module",