Skip to content

Releases: Abarbesgaard/Sara

v1.5.2

Choose a tag to compare

@github-actions github-actions released this 07 Sep 08:34
release: v1.5.2 (mcp guide tool ergonomics fix)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

v1.5.1

Choose a tag to compare

@github-actions github-actions released this 07 Sep 07:05
release: v1.5.1 (mcp pre-initialize fix)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

v1.5.0

Choose a tag to compare

@github-actions github-actions released this 07 Sep 05:54
release: v1.5.0 (local telemetry capture)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

v1.4.0

Choose a tag to compare

@github-actions github-actions released this 02 Sep 10:16
chore(release): 1.4.0 — ship the perf work and repair the release cas…

v1.1.2

Choose a tag to compare

@github-actions github-actions released this 31 Aug 08:54
6dfffe2
chore(release): 1.1.2 (#122)

Release the recall strength fix: associative/spread surfacings no longer
inflate a memory's usage-based strength, while Hebbian co-activation is
preserved.

v1.1.1

Choose a tag to compare

@github-actions github-actions released this 28 Aug 11:47
fix(db): serialize display-id allocation and make set_* helpers atomic

Under concurrent agents — the workload Sara is built for — three data-integrity
bugs were reachable:

* insert_task read the next free display ID and inserted it as two separate
  steps. WAL readers never block, so racing agents all read the same value and
  all used it: 40 parallel `sara add` calls on 1.1.0 produced 9 distinct IDs,
  31 tasks sharing ID 8. tasks.id has no UNIQUE constraint, so nothing caught
  it and `sara done <id>` became silently ambiguous. The same race applied to
  memory labels (insert_item), checklist positions (add_step) and repack_ids.
  Allocation now holds the write lock (BEGIN IMMEDIATE) across read and write.

* The set_item_*/set_task_files_sourced helpers DELETE then INSERT in a loop
  with no transaction, so a mid-loop failure committed the delete and lost the
  data. Each is now atomic via SAVEPOINT — savepoints nest, which matters
  because import already holds a transaction open.

* relearn --file stored the path raw while learn and recall both resolve it to
  absolute, so a corrected memory silently vanished from recall --file.

add_step also swallowed DB errors and fell back to position 1, inserting at the
front of the guide with a duplicate position instead of reporting the failure.

Each fix is covered by a test verified to fail without it.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

v1.1.0

Choose a tag to compare

@github-actions github-actions released this 28 Aug 11:16
Merge remote-tracking branch 'sara/main'

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 25 Aug 09:40
11e9561
Merge pull request #119 from Abarbesgaard/nightly

Release 1.0.0

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 06 Jul 10:25
chore(release): bump version to 0.9.0

Co-authored-by: Cursor <cursoragent@cursor.com>

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 06 Jul 07:31
ba68b89
chore(release): bump version to 0.8.0 (#75)

Board redesign (issue-tree grouping, badges, dependency graph view),
shared TUI keymap, $EDITOR integration, list --by-issue, and help
overlay have accumulated since 0.7.0 — cutting a minor release.