Skip to content

release: v0.8.1#338

Merged
aaltshuler merged 1 commit into
mainfrom
release/v0.8.1
Jul 6, 2026
Merged

release: v0.8.1#338
aaltshuler merged 1 commit into
mainfrom
release/v0.8.1

Conversation

@aaltshuler

@aaltshuler aaltshuler commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Release commit for v0.8.1 — see docs/releases/v0.8.1.md for the user-facing notes.

  • Version 0.8.1 across all seven crates + path-dep constraints, Cargo.lock, openapi.json, AGENTS.md surveyed version.
  • Channel decision: binaries/Homebrew/installer only; crates.io deferred until Lance 9.0.0 stable (the substrate git-pin cannot be published). publish-crates.yml gains a self-healing guard: skips cleanly while lance is a git dependency, resumes automatically when it returns to a registry version; skipped tags are recoverable via workflow_dispatch.
  • Content since v0.8.0 (all previously merged & CI-validated): Lance 9.0.0-beta.15 substrate (adopts upstream fixes lance#7480/#7320), filtered-search prefilter fix, embedding validation hardening, enum widening, undirected traversal, blob tables in maintenance, self-service upgrade refusals, bench harness.
  • On-disk format unchanged (internal schema v4) — no rebuild, downgrade to 0.8.0 possible.
  • cargo test --workspace --locked green on the release commit; omnigraph version smoke: 0.8.1 / internal-schema 4.

After merge: annotated tag v0.8.1 on the merge commit → release.yml builds the binary matrix + updates the Homebrew tap.


Open in Devin Review

Greptile Summary

This is the v0.8.1 release commit. It bumps all seven workspace crates from 0.8.0 to 0.8.1, regenerates Cargo.lock and openapi.json, updates AGENTS.md's surveyed version, adds the release notes, and wires a self-healing skip guard into publish-crates.yml that defers crates.io publication while lance is git-pinned to a pre-release.

  • All version strings (crate manifests, path-dep constraints, Cargo.lock, openapi.json) are updated consistently; on-disk format is unchanged at schema v4 so downgrade to 0.8.0 remains possible.
  • The new publish-crates.yml step correctly runs after checkout, detects the lance = { git … } entry in the workspace manifest, and propagates the CARGO_PUBLISH_SKIP flag that gates every subsequent step; the guard self-heals when lance returns to a registry version.
  • The omnigraph-ts SDK still declares serverVersion: 0.8.0, but since the OpenAPI surface is unchanged (only info.version changed), this is not a compatibility break — the check-drift script will continue to pass against the still-valid v0.8.0 tag.

Confidence Score: 5/5

Safe to merge; all version strings are updated consistently, the on-disk format is unchanged, and the new workflow guard behaves correctly for the git-pinned lance dependency.

The change is a coordinated version bump with a well-scoped workflow addition. Version strings are consistent across all seven crate manifests, Cargo.lock, and openapi.json. The publish-crates.yml guard runs after checkout, correctly detects the git pin, and propagates the skip flag through all downstream steps. The only finding is a stale Lance 7.x label in the AGENTS.md architecture diagram, which is cosmetic and pre-existing.

AGENTS.md — the architecture diagram's Lance 7.x label is a one-line fix; everything else looks correct.

Important Files Changed

Filename Overview
.github/workflows/publish-crates.yml Adds self-healing guard to skip crates.io publication while lance is git-pinned; guard runs after checkout so Cargo.toml is available, and the existing skip-flag idiom carries through to all downstream steps correctly.
AGENTS.md Version surveyed bumped to 0.8.1 and RFC process entry added to the topic table; however the architecture at a glance ASCII diagram still shows Lance 7.x while the substrate is now Lance 9.x.
Cargo.lock All seven workspace crate entries bumped from 0.8.0 to 0.8.1; no other dependency changes detected.
crates/omnigraph-cli/Cargo.toml Package version and all six internal path-dependency version constraints bumped from 0.8.0 to 0.8.1; consistent with the workspace-wide release bump.
crates/omnigraph-server/Cargo.toml Package version and all five internal path-dependency constraints bumped consistently to 0.8.1.
openapi.json Info.version field updated from 0.8.0 to 0.8.1; no API surface changes, consistent with the patch release scope.
docs/releases/v0.8.1.md New release notes file covering all user-visible changes, behavior changes, upgrade notes, and the crates.io deferral rationale; follows OSS-facing style requirements from AGENTS.md.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[push v* tag / workflow_dispatch] --> B{CARGO_REGISTRY_TOKEN set?}
    B -- No --> SKIP1[Set CARGO_PUBLISH_SKIP=1\nAll remaining steps skipped]
    B -- Yes --> C[Resolve ref]
    C --> D[Checkout source at tag]
    D --> E{lance = git in Cargo.toml?}
    E -- Yes\nLance pre-release --> SKIP2[Set CARGO_PUBLISH_SKIP=1\nDefer until Lance stable]
    E -- No\nLance registry version --> F[Install deps + Rust stable]
    F --> G[publish_if_new omnigraph-compiler]
    G --> H[publish_if_new omnigraph-policy]
    H --> I[publish_if_new omnigraph-engine]
    I --> J[publish_if_new omnigraph-api-types]
    J --> K[publish_if_new omnigraph-cluster]
    K --> L[publish_if_new omnigraph-server]
    L --> M[publish_if_new omnigraph-cli]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[push v* tag / workflow_dispatch] --> B{CARGO_REGISTRY_TOKEN set?}
    B -- No --> SKIP1[Set CARGO_PUBLISH_SKIP=1\nAll remaining steps skipped]
    B -- Yes --> C[Resolve ref]
    C --> D[Checkout source at tag]
    D --> E{lance = git in Cargo.toml?}
    E -- Yes\nLance pre-release --> SKIP2[Set CARGO_PUBLISH_SKIP=1\nDefer until Lance stable]
    E -- No\nLance registry version --> F[Install deps + Rust stable]
    F --> G[publish_if_new omnigraph-compiler]
    G --> H[publish_if_new omnigraph-policy]
    H --> I[publish_if_new omnigraph-engine]
    I --> J[publish_if_new omnigraph-api-types]
    J --> K[publish_if_new omnigraph-cluster]
    K --> L[publish_if_new omnigraph-server]
    L --> M[publish_if_new omnigraph-cli]
Loading

Comments Outside Diff (1)

  1. AGENTS.md, line 56 (link)

    P2 The architecture diagram still labels the storage layer as Lance 7.x while the rest of this file (and the workspace manifest) describe the substrate as Lance 9.x. AGENTS.md rule 6 ("Don't lie") applies here since the file is being modified in this PR.

    Context Used: AGENTS.md (source)

    Fix in Claude Code

Fix All in Claude Code

Reviews (1): Last reviewed commit: "release: v0.8.1" | Re-trigger Greptile

Context used:

  • Context used - AGENTS.md (source)

Version bump across all seven workspace crates + path-dep constraints,
Cargo.lock, openapi.json, and the AGENTS.md surveyed version (also
restores the RFC-process row in the topic index that was dropped during
branch juggling). Release notes: docs/releases/v0.8.1.md.

Channel note: crates.io publication is deferred for this release — the
substrate is a rev-pinned Lance pre-release (git dependency), which
published crates cannot reference. publish-crates.yml gains a
self-healing guard that skips cleanly while the pin is a git dep and
resumes automatically when the dependency returns to a registry version
(Lance 9.0.0 stable → v0.9.0); a workflow_dispatch catch-up can then
publish any skipped tag. Binaries, Homebrew, and the installer ship
normally via release.yml.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@aaltshuler aaltshuler merged commit e415338 into main Jul 6, 2026
8 checks passed
@aaltshuler aaltshuler deleted the release/v0.8.1 branch July 6, 2026 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant