From 1a9f8b1f7fa91568cb9dd7f664b71c8d52e44da1 Mon Sep 17 00:00:00 2001 From: Andrew Altshuler Date: Sat, 23 May 2026 14:09:58 +0100 Subject: [PATCH] ci(publish-crates): include omnigraph-policy in the publish list (#116) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit omnigraph-policy is a new crate this release cycle (Cedar policy engine, MR-722). It wasn't added to the publish list when it was created, so v0.5.0's tag-triggered publish run succeeded for omnigraph-compiler but failed at omnigraph-engine: failed to prepare local package for uploading Caused by: no matching package named `omnigraph-policy` found location searched: crates.io index required by package `omnigraph-engine v0.5.0` omnigraph-policy has no internal omnigraph-* deps so it can publish after omnigraph-compiler (either could go first). omnigraph-engine depends on both; server on the three; cli on everything. publish_if_new is idempotent — re-running with the v0.5.0 tag after this lands will skip omnigraph-compiler (already published), then publish policy + engine + server + cli. Co-authored-by: Claude Opus 4.7 (1M context) --- .github/workflows/publish-crates.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/publish-crates.yml b/.github/workflows/publish-crates.yml index d7f783f..fad3951 100644 --- a/.github/workflows/publish-crates.yml +++ b/.github/workflows/publish-crates.yml @@ -93,7 +93,12 @@ jobs: cargo publish -p "$crate" --locked } + # Order matters: each crate must precede anything that depends on it. + # omnigraph-compiler and omnigraph-policy have no internal deps; + # omnigraph-engine depends on both; server depends on engine + the + # two leaf crates; cli depends on everything. publish_if_new omnigraph-compiler + publish_if_new omnigraph-policy publish_if_new omnigraph-engine publish_if_new omnigraph-server publish_if_new omnigraph-cli