You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e4aab5b
Browse filesBrowse the repository at this point in the historyBrowse files
advance recurring occurrences moved before their original date
A moved occurrence replaces its original recurrence slot, but next-occurrence
planning ignored that stored exclusion, so completing or skipping the moved
occurrence could schedule the replaced original date again.
Treat pending and resolved moved-original dates as processed while calculating
the next open occurrence only. Persisted completion and skip history stays
keyed to the moved date.
Copy file name to clipboardExpand all lines: docs/releases/unreleased.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,3 +35,6 @@ When a change has user-facing documentation, include a canonical tasknotes.dev l
35
35
## Fixed
36
36
37
37
- Fixed `PUT /api/tasks/:id` ignoring empty arrays for `contexts` and `blockedBy`: sending `{"contexts": []}` or `{"blockedBy": []}` now clears the corresponding frontmatter field instead of silently leaving the previous value in place. The deletion pass previously fired only on a literal `undefined`, which JSON cannot express, so HTTP clients had no way to clear these fields. Thanks to @tgrosinger for the contribution.
38
+
- (#2191) Completing or skipping a recurring occurrence that was moved earlier
39
+
than its original date no longer schedules that original date again. Thanks to
0 commit comments