omnigraph/.github/workflows
Andrew Altshuler 92e3886cfa
ci: add publish-crates workflow for crates.io releases (#74)
The release.yml workflow builds binaries and updates Homebrew but never
published to crates.io — v0.4.0 and v0.4.1 are missing from the registry
even though the local Cargo.toml and the v0.4.1 tag are at 0.4.1.

This adds a separate workflow that:
- auto-publishes on every v* tag push (future releases self-publish)
- can be manually dispatched with a tag input (catch up on v0.4.1)
- is idempotent: skips a crate if its current crates.io version already
  matches local, so a partial failure is safe to retry
- gates on CARGO_REGISTRY_TOKEN (already in repo secrets); skips cleanly
  if the token is ever rotated out

Publishes in dependency order: omnigraph-compiler → omnigraph-engine →
omnigraph-server → omnigraph-cli. Path-only deps in Cargo.toml carry
explicit version fields, so cargo publish strips paths and resolves
against crates.io.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-08 15:48:37 +03:00
..
ci.yml ci: fold failpoints test into Test Workspace job 2026-05-01 21:15:14 +02:00
package.yml package caller: pass AWS secrets via secrets: inherit 2026-04-18 21:54:08 +03:00
publish-crates.yml ci: add publish-crates workflow for crates.io releases (#74) 2026-05-08 15:48:37 +03:00
release-edge.yml Drop macOS x86_64 build target (#55) 2026-04-26 18:19:26 +03:00
release.yml Drop macOS x86_64 build target (#55) 2026-04-26 18:19:26 +03:00