v1.0.114

What's Changed

• docs: relicense under AGPL-3.0, add CONTRIBUTING + CHANGELOG (OSSF badge) by @moorew in #19
• dependency updates by @moorew in #20
• chore(ci): resolve remaining zizmor findings (artipacked, superfluous-actions) by @moorew in #21
• feat(integrations): surface AI task-title cleanup in settings by @moorew in #22
• chore(deps): bump uuid from 1.23.2 to 1.23.3 in /frontend/src-tauri in the cargo-deps group across 1 directory by @dependabot[bot] in #10
• fix(installer): stop set -e abort on custom input; auto-tag releases … by @moorew in #23

New Contributors

• @dependabot[bot] made their first contribution in #10

Full Changelog: v1.0.113...v1.0.114

What's Changed

• docs: relicense under AGPL-3.0, add CONTRIBUTING + CHANGELOG (OSSF badge) by @moorew in #19
• dependency updates by @moorew in #20
• chore(ci): resolve remaining zizmor findings (artipacked, superfluous-actions) by @moorew in #21
• feat(integrations): surface AI task-title cleanup in settings by @moorew in #22
• chore(deps): bump uuid from 1.23.2 to 1.23.3 in /frontend/src-tauri in the cargo-deps group across 1 directory by @dependabot[bot] in #10
• fix(installer): stop set -e abort on custom input; auto-tag releases … by @moorew in #23

Full Changelog: v1.0.113...v1.0.114

v1.0.113

What's Changed

• fix(recurrence): proactively generate future recurring instances (1.0.113)

Recurring instances were only materialised lazily, server-side, when a web
client requested a specific week. Offline-first clients (Tauri desktop,
Capacitor Android) read tasks straight from the local SQLite DB and never
trigger that generation, so a daily task appeared to "end" at the last week a
web client happened to request — e.g. showing only today + tomorrow.

Add a recurrence poller (StartRecurrence) that runs on startup and every 6h,
materialising the current week + next 2 weeks via TaskStore.GenerateHorizon.
These instances flow to every client through normal sync, so no client-side
recurrence logic is needed. Generation stays idempotent (pristine-existence
checks), and the existing daily rollover is unchanged.

Adds GenerateHorizon + a regression test covering future weeks and idempotency.

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com by @moorew in #18

New Contributors

• @moorew made their first contribution in #18

Full Changelog: v1.0.112...v1.0.113

What's Changed

• fix(recurrence): proactively generate future recurring instances (1.0.113)

Recurring instances were only materialised lazily, server-side, when a web
client requested a specific week. Offline-first clients (Tauri desktop,
Capacitor Android) read tasks straight from the local SQLite DB and never
trigger that generation, so a daily task appeared to "end" at the last week a
web client happened to request — e.g. showing only today + tomorrow.

Add a recurrence poller (StartRecurrence) that runs on startup and every 6h,
materialising the current week + next 2 weeks via TaskStore.GenerateHorizon.
These instances flow to every client through normal sync, so no client-side
recurrence logic is needed. Generation stays idempotent (pristine-existence
checks), and the existing daily rollover is unchanged.

Adds GenerateHorizon + a regression test covering future weeks and idempotency.

Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com by @moorew in #18

New Contributors

• @moorew made their first contribution in #18

Full Changelog: v1.0.112...v1.0.113

v1.0.112

Full Changelog: v1.0.111...v1.0.112

Full Changelog: v1.0.111...v1.0.112