Skip to content

Barrel 2026.11.9

Choose a tag to compare

@github-actions github-actions released this 14 Nov 17:26
· 15 commits to main since this release

Commit 794415d73ca7, 2026-11-14.

App Version
barrel 1.14.0
barrel_att_s3 0.2.2
barrel_crypto 1.0.0
barrel_docdb 3.1.0 (was 3.0.0)
barrel_embed 2.6.1
barrel_faiss 1.0.1
barrel_ngram 0.11.5
barrel_rerank 1.0.3
barrel_server 1.15.1 (was 1.15.0)
barrel_spaces 2.0.0 (was 1.3.2)
barrel_vectordb 2.5.4

barrel_docdb 3.1.0

Fixed

  • A document whose id is another id followed by : (session:42 and session:42:data:k, a and a:b) mixed its version history with the other one. The conflicts of a listed versions of a:b, replication carried them to the peers as versions of a, and the longer one's deletion could make a read as deleted on every node. Removing the history of a also removed the history of a:b. Each document now keeps its own history.
  • A peer still on 3.0 keeps sending versions it took from another document. A 3.1 database refuses them and logs it.
  • Versions 3.0 already stored this way are repaired when 3.1 converts the database: a document whose winner came from another document shows its own newest version again, and conflict counts are corrected.

Added

  • A conflict_resolver receives the id of the document in each version (doc_id), so one resolver can treat documents differently by id, a deleted version included.

Changed

  • The version history is stored in a new layout. A database moves to it once, the first time this version opens it writable, and logs how many rows it moved and documents it repaired; a read-only database keeps reading the old layout correctly. A database opened by 3.1 cannot be opened by 3.0 again without losing its conflicts and past versions. You can upgrade the nodes of a mesh one at a time.

barrel_server 1.15.1

Fixed

  • Spaces, tokens and handoffs replicated between servers no longer lose writes: a revoked token stays revoked, session data and pins written on two servers are both kept, and a completed handoff stays completed. Every server of a mesh must be upgraded before any of them writes; the spaces guide gives the order.
  • A document whose id extends another id with : no longer mixes its history with the other one (barrel_docdb 3.1).

Changed

  • A session read over REST or MCP no longer carries _rev, and carries counters.
  • Requires barrel_docdb 3.1 and barrel_spaces 2.0.

barrel_spaces 2.0.0

Breaking

  • Grants, sessions and handoffs are stored as one document per fact, so they replicate without losing writes. Nodes running 1.x and 2.0 do not agree: a 1.x node ignores the new revocation documents and keeps accepting a revoked token, and does not see session data written by 2.0. Upgrade every node, with writes or replication stopped, then run barrel_spaces:migrate/0 on one node; the spaces guide gives the full procedure. Documents written by 1.x read the same and convert on their next write. There is no way back to 1.x once sessions are converted.
  • barrel_session:get/2 no longer returns _rev, and returns counters.
  • Requires barrel_docdb 3.1.

Fixed

  • A revocation could be undone. Revoking edited the grant, and a concurrent write to that grant on another node could win over the revocation. A revocation is now a document of its own that nothing edits.
  • Two nodes writing the same session kept only one side's data keys, pins or summary, and an unpinned item came back from a node that still had it. Each data key, pin and the summary are now documents of their own; removing one deletes its document.
  • A handoff could go back from completed to accepted, or from accepted to pending. Each step is now a document written once and the status is the furthest step present. Agents accepting on nodes that cannot see each other are all recorded, and every node names the same owner.
  • Concurrent edits of grants, sessions and handoffs left conflicts that nothing resolved. The registry and spaces now open with barrel_spaces_resolver, which closes every conflict on these documents by keeping the version every node already shows, so applications replicating a space no longer need a resolver for them. A space opened with your own conflict_resolver still uses it for your documents.
  • The janitor could delete a session's documents that replication delivered before the session itself, and the deletion then replicated to every node. It now deletes them only once the session is deleted.

Added

  • barrel_spaces_resolver: the conflict resolver of the registry and of spaces, for applications that open them themselves.
  • barrel_session:delete_data/3 removes a data key.
  • barrel_session:incr_counter/4 and get_counters/2: per-session counters that two nodes can update at once without losing an increment. get/2 returns them under counters.
  • barrel_caps:revoke/2 records who revoked a token; list/1 returns it as revoked_by.
  • barrel_spaces:migrate/0, barrel_session:migrate/1, barrel_caps:migrate/0 and barrel_handoff:migrate/0 move documents written by 1.x to the new layout.