Skip to content

v0.13.0

Latest
Latest

Choose a tag to compare

View all tags
@aaltshuler aaltshuler released this 07 Oct 15:26
· 112 commits to main since this release
v0.13.0
926ba35
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

OmniGraph v0.13.0

Released 2026-10-07.

0.13 closes the server configuration gaps in 0.12. The previous release
introduced breaking storage, query and API changes, but shipped with incomplete
cluster configuration support. Cluster configuration now covers live updates to
existing graphs, graph creation and graph deletion through one plan/apply workflow.

Upgrading from 0.11 or earlier requires migration planning; older
cluster-managed graphs require export and rebuild. See
Upgrading to 0.13 below.

What's in 0.13

  • Live configuration updates: change schemas, stored queries, authorization
    policies, embedding providers and Blob access rules without restarting the
    server.
  • Graph lifecycle through configuration: add graphs or remove them through
    cluster apply. Removing a graph permanently deletes its managed storage and
    retained history.
  • Deployment previews and tracking: preview changes with
    cluster plan --server, submit with --no-wait, and track completion by
    deployment ID—even after a client disconnect or timeout.
  • Simpler CLI: consistent query, mutate, load and lint commands, with
    managed service operations selected through cluster … --managed.

Upgrading to 0.13

If you're upgrading from 0.11 or earlier, plan for breaking storage, query and
API changes. Replacing the executable alone does not upgrade an older graph.

  • Older cluster-managed graphs require export and rebuild. Export using the
    old executable, create a replacement cluster with 0.13, and import the data.
    Previous commit IDs, snapshots and branch history are not carried over.
  • Supported standalone graphs can be upgraded offline, preserving data,
    branches and retained commit history. Follow the
    upgrade guide for your source version.
  • Existing 0.12 graphs need no additional storage-format migration. Cluster
    ledger conversion may still be necessary; see
    cluster conversion.

Preserve a verified backup and the old executable. Upgrade the CLI, server and
HTTP integrations together, and verify the replacement before switching
application traffic.

See the upgrade guide for migration steps and
the 0.12 and 0.13 release notes for the complete
breaking-change list and detailed changes.

Assets 10
Loading