1.1.0

DayTasks 1.1.0

Changed

• Task List view: the filter toolbar is now two tidy rows with icons — search and
  status pills on top; date, group, sort, tags, contexts, projects, and clear
  below. Status pills show their status icon and color. Same filtering behavior.
• Task List view: each group is now a bordered container with a group icon
  (calendar / status / folder by group-by), a count badge, and a collapse arrow.

Fixed

• Inline capture: dates are now recognized only from colon markers
  (scheduled:, due:/by:/deadline:). The parser no longer scans the line
  for a bare date, so ordinary prose date words ("Discuss the March numbers",
  "Email report by friday") stay in the task title and are no longer mistaken for
  a date or stripped out. Use scheduled:friday to schedule from the line.

1.0.1

DayTasks 1.0.1

Fixed

• Inline capture button: it now appears only on Markdown checkbox/task lines
  (- [ ], * [x], 1. [ ], blockquotes ok), not on every line the cursor lands
  on. Plain prose lines no longer show the button (the command still captures any
  line).

1.0.0

DayTasks 1.0.0

Added

• Inline task capture. Run the Capture task from line command on any note
  line (or a multi-line selection) to turn it into a scheduled DayTasks task. The
  line is parsed for #tags, @contexts, +project (or +[[wikilink]]),
  !priority, a time estimate (45m, 2h, or 1h30m),
  and a date. A scheduled: marker or a bare date phrase sets the day the task
  sits on; due:/by:/deadline: set a deadline only. With no scheduled: date,
  the task lands on the note's daily date if it is a daily note, otherwise today.
  The captured line is replaced with the task title followed by the new task id,
  and the task records the note it came from. New setting: Inline capture › Enable inline task
  capture (on by default). Multi-line selections use the lines after the first as
  the task description.
• Inline capture button. With inline capture enabled, a small button appears
  at the end of the current line in editor / Live Preview mode; click it to capture
  that line as a task — no command palette needed. The button is hidden on blank
  lines and on lines already captured. New setting: Inline capture › Show capture
  button (on by default).

Fixed

• Inline capture: a due: date is now treated as a deadline only and no longer
  sets the day a captured task is scheduled. A task with a due: date but no
  scheduled: marker lands on today (or the note's daily date) instead of jumping
  to the due date.
• Inline capture: estimates now require a unit (45m, 2h, 1h30m). A bare
  number is kept in the title instead of being read as minutes, so "Buy 2 apples"
  no longer becomes a 2-minute task.
• Inline capture: running the command on a line that is already captured (one
  ending in a task id) no longer creates a duplicate task — it reports that the
  line is already captured and does nothing.
• Inline capture: the line is marked only after re-checking it is unchanged once
  the task is saved, so a concurrent edit during the save can no longer overwrite
  the wrong line; a stale capture button that lingers after the feature is turned
  off no longer captures.

Removed

• Removed the reserved local API settings (Enable local API, API port) from the
  settings tab and the stored settings. They were schema-only and never shipped a
  working API. A local HTTP API and a browser extension are out of scope for
  DayTasks. Existing stored API values are dropped harmlessly on the next save;
  tasks are unaffected.

0.8.3

DayTasks 0.8.3

Security

• Release assets now carry build-provenance attestations. You can
  cryptographically verify that main.js, manifest.json, and styles.css were
  built from this repository's source.

Internal

• Releases are now built, attested, and published by GitHub Actions.
• Added GitHub issue templates (bug report / feature request) and a Discussions
  space for questions and ideas.
• Replaced an internal property-drop pattern with a small omit() helper
  (no behavior change).

0.8.2

DayTasks 0.8.2

Fixed

• The daily-note task widget no longer triggers a ResizeObserver feedback loop
  in Live Preview. Its bottom spacing was recalculated and rewritten on every
  editor frame; that rewrite resized the note and fed CodeMirror's own resize
  observer, which looped back into another recalculation — flooding the developer
  console with "ResizeObserver loop completed with undelivered notifications"
  warnings and forcing a layout reflow on every keystroke and scroll. The spacing
  is now rewritten only when it actually changes, so the loop is gone and editing
  near the widget is lighter.

0.8.1

DayTasks 0.8.1

Changed

• Better theme support. The warm surface tint is now a single overridable CSS
  variable, and the success/error/estimate colors fall back to Obsidian theme
  variables instead of fixed hex — so DayTasks tracks dark and high-contrast
  themes more faithfully.
• Settings: the reserved API section heading is now simply API.

Fixed

• Task cards no longer overlap their controls when a detail note is present.
  A detail note adds a fifth control to the card; cards now reserve room for all
  of them, so a collapsed card's due date is no longer clipped and an expanded
  card's long title wraps instead of running under the icons. The collapsed task
  id and due date also use a smaller, consistent size, and the id picks up the
  theme's accent color.
• Visible keyboard focus. The Task List filter controls and the project/tag
  chips show a focus outline when you tab to them, and the group collapse/expand
  button has an accessible name for screen readers.
• Creating a detail note no longer fails when both candidate filenames are
  taken. If <title>.md and the <title>-<id>.md fallback both already exist,
  DayTasks now picks the next free name instead of erroring and leaving the task
  without its note.
• Editing or syncing a task no longer overwrites an unrelated note. If a
  task's detail-note link points at a file that now belongs to a different task
  (moved or replaced), DayTasks leaves that note's properties untouched.
• The daily-note task widget now works in popped-out windows and split
  panes. It is built against the note's own window, so it renders and sizes
  correctly even when that note isn't the focused one.
• Task List view filters and layout survive a quick disable/reload. Pending
  view-state is saved when the plugin unloads instead of being dropped, and
  scheduled refreshes no longer run after the plugin is gone.

Security

• Detail-note folders stay inside your vault. A Detail notes folder setting
  containing .. (for example ../Outside) can no longer write notes outside the
  vault — paths are normalized and traversal segments are dropped.
• Unreadable tasks are no longer silently discarded. If stored data contains
  task entries DayTasks can't read, it now shows a notice with how many were
  skipped, so a later save doesn't quietly erase them. Back up your data before
  making changes if you see this.

0.8.0

DayTasks 0.8.0

Added

• Date templates in the detail-notes folder. The Detail notes folder
  setting now understands {{year}}, {{month}}, {{day}}, and {{date}},
  filled from the task's scheduled date when a note is created — so
  Tasks/{{year}}/{{month}} files a task scheduled in June 2026 under
  Tasks/2026/06/. Nested folders are created automatically. A plain folder with
  no {{…}} works exactly as before.

Full Changelog: 0.7.2...0.8.0

0.7.2

DayTasks 0.7.2

Changed

• Existing detail notes are tidied up automatically. On first load after this
  update, any detail note made before 0.7.1 is normalized once: its file is
  renamed to the clean title-only name (Buy milk.md, dropping the -<id>
  suffix, when that name is free) and the redundant title property is removed.
  Your note body and links are preserved.
• Detail-note sync now tracks only the tasks that actually have a note instead of
  scanning every task on each change (faster on large vaults).

Full Changelog: 0.7.1...0.7.2

0.7.1

DayTasks 0.7.1

Changed

• Detail note filenames are now just the task title (e.g. Buy milk.md
  instead of Buy milk-TSK-abc123.md). If two tasks share a title, the second
  falls back to a -<id> suffix. The redundant title property was removed from
  the managed frontmatter — the note's filename is its title.

Fixed

• The Create detail note toggle in the task edit dialog now works: turning
  it on and saving creates the note (previously it only worked when creating a new
  task; existing tasks could already use the ⋮ menu).

Full Changelog: 0.7.0...0.7.1

0.7.0

DayTasks 0.7.0

Added

• Detail notes — give any task a real markdown note that stays linked to it.
  • Turn on Create detail note in the task modal to make one when you create a
    task, or use the ⋮ menu → Create detail note on any existing task. The note
    opens in a new tab.
  • Open an existing note again from the new file-text icon on the card rail
    (shown on collapsed cards, expanded cards, and in the Task List view) or the
    ⋮ menu → Open detail note.
  • The note's frontmatter is managed for you — title, status, priority,
    dates, contexts, projects, estimate, tags, and ids stay in sync with the task
    automatically. The rest of the note body is yours and is never touched.
  • Opening a detail note shows an interactive Subtasks panel: the task's
    subtasks render as the same cards you use elsewhere, and cycling a subtask's
    status updates the real task (and every open view) instantly.
  • If you delete a detail note's file, opening it again clears the stale link so
    the card reverts to offering Create detail note.

Changed

• The Detail notes folder and Create detail note by default settings are
  now active (previously reserved). The folder (default DayTasks/Tasks) is where
  new detail notes are created.

Full Changelog: 0.6.0...0.7.0