apunkt/omnigraph
1
0
Fork 0
mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-12 01:45:14 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
omnigraph/docs/releases/v0.6.1.md
Andrew Altshuler 171a8c5d13
docs(releases): attribute the __run__ sweep (MR-770) to v0.6.2, not v0.6.1 (#161) 
The v0.6.2 notes omitted the MR-770 `__run__` cleanup entirely, and the v0.6.1
notes wrongly claimed it shipped in v0.6.1. The code (the `migrate_v2_to_v3`
`__manifest` sweep + `is_internal_run_branch`/`run_registry.rs` removal) first
appears at the v0.6.2 tag via #132 and is absent at v0.6.1.

- v0.6.2: add the MR-770 highlight, correct the manifest-stamp note to describe
  the v2→v3 auto-migration on first read-write open (with the read-only caveat),
  and mention the cleanup in the intro.
- v0.6.1: replace the two over-claiming `__run__` lines with corrections that
  point to v0.6.2.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-09 22:31:50 +03:00

4.3 KiB
Raw Blame History

Omnigraph v0.6.1

v0.6.1 focuses on operational polish after v0.6.0: stored-query registries, safer branch cleanup, more complete release artifacts, and a Lance blob-compaction workaround.

Highlights

  • Stored-query registries. omnigraph.yaml can declare curated queries: blocks per graph. Servers load and type-check them at startup, omnigraph queries validate checks them offline, omnigraph queries list shows exposed queries and typed params, GET /queries exposes a typed catalog, and POST /queries/{name} invokes a stored query without accepting ad hoc .gq source from the client.
  • Stored-query policy gate. New Cedar action invoke_query gates the stored-query invocation surface. Stored mutations are double-gated: invoke_query to reach the stored query and change for the actual write.
  • Safer branch deletion. branch_delete now treats the manifest as the authority, flips branch visibility atomically, and reclaims per-table/commit-graph forks as derived state. If best-effort reclaim is interrupted, cleanup reconciles orphaned forks; reusing a branch name before cleanup reports an actionable error.
  • Legacy __run__ cleanup (MR-770). (Correction: this item shipped in v0.6.2, not v0.6.1 — the v0.6.1 notes over-claimed it. At the v0.6.1 tag the __run__ branch-name guard and run_registry.rs were still present and no v2→v3 sweep migration existed.) The guard removal and the one-time v2→v3 __manifest migration that sweeps stale __run__* staging branches on first read-write open are described in the v0.6.2 release notes.
  • Blob-safe optimize. omnigraph optimize skips tables with Blob properties instead of failing the whole sweep on Lance's blob-v2 compaction decode bug. Skips are visible in human output, --json as skipped, TableOptimizeStats.skipped, and logs; non-blob tables still compact normally.
  • Deployment improvements. The container entrypoint now composes OMNIGRAPH_TARGET_URI with OMNIGRAPH_CONFIG, so operators can keep the graph URI in env while loading policy/query config from a mounted file. The local RustFS bootstrap pins RustFS beta.3 and allows the current insecure local-dev default credentials.
  • Windows release support. Tagged and edge releases now publish Windows x86_64 archives containing omnigraph.exe and omnigraph-server.exe, with a PowerShell installer and Windows install docs.
  • Release tooling. Homebrew formula generation was tightened to produce audit-clean formulas.

Compatibility Notes

  • A graph selected by name (--target or server.graph) now uses graphs.<name>.policy and graphs.<name>.queries. Top-level policy / queries blocks are only for anonymous bare-URI single-graph mode; using them with a named graph now fails loudly with migration guidance.
  • mcp.expose defaults to true for stored-query registry entries. Set mcp: { expose: false } for service-only queries that should not appear in the catalog.
  • invoke_query is graph-scoped, not branch-scoped. Branch/snapshot access remains enforced by the inner read / change gate.
  • Legacy __run__ migration. (Correction: deferred to v0.6.2.) The automatic v2→v3 __manifest stamp migration that sweeps stale __run__* branches on first read-write open ships in v0.6.2, not v0.6.1; a v0.6.1 binary does not perform it. See the v0.6.2 notes for the migration behavior and the read-only caveat.
  • Blob tables are not compacted until the upstream Lance fix lands, so fragment count and deleted-row space on blob tables are not reclaimed by optimize. Reads, writes, and query results are unaffected; no on-disk migration is required.
  • TableOptimizeStats is now #[non_exhaustive] and gains a skipped: Option<SkipReason> field (so does the new SkipReason enum). This is a source-level change only for downstream code that built this returned result struct by literal — rare, since it is produced by optimize and consumed by reading its fields; field access is unaffected, and #[non_exhaustive] keeps future additions non-breaking.

Docs And Cleanup

  • Public docs were updated for stored queries, policy, server routes, deployment, Windows installation, branch deletion, maintenance, and the runs docs rename to writes.
  • README copy and release documentation were refreshed; older release notes had small typo/wording fixes.