A concise inventory of the .github/workflows/ pipelines. The key, non-obvious fact is that ci.yml's full Test Workspace job is gated `if: github.event_name != 'pull_request'` — it runs cargo test --workspace --locked (plus failpoints and S3) only on push to main, v* tags, and manual dispatch, a deliberate PR-latency trade-off, so it is NOT a required check and main can briefly break; contributors must run the suite locally and regenerate openapi.json before merging. The fast PR gates that remain are Classify Changes, Check AGENTS.md Links, Test omnigraph-server --features aws, and the two CODEOWNERS checks. Also documents the Windows binary build job, RustFS S3 integration, and the release pipelines (release-edge.yml, release.yml with Homebrew tap push, package.yml ECR images). Read when changing CI, debugging why a PR check is or isn't running, or before merging non-trivial work given main is not gated by the full test suite.
CI / Release Workflows
.github/workflows/:
- ci.yml: text-only changes skip; otherwise
cargo test --workspace --lockedon ubuntu-latest with protobuf compiler. OpenAPI-drift check that auto-commits the regeneratedopenapi.jsonfor same-repository PRs. Also runs the AGENTS.md cross-link integrity check (scripts/check-agents-md.sh).Test Workspacedoes not run on pull requests. The job is gatedif: github.event_name != 'pull_request', so the full workspace + failpoints suite runs only on push tomain(post-merge), onv*tags, and on manualworkflow_dispatch. This was a deliberate PR-latency trade-off — it was the slowest gate (~15min warm, up to the 75min cold ceiling).RustFS S3 Integrationneeds: test, so it is push-/dispatch-only for the same reason. The fast PR gates remain:Classify Changes,Check AGENTS.md Links,Test omnigraph-server --features aws, and the two CODEOWNERS checks.Test Workspaceis correspondingly not in the required-check list (.github/branch-protection.json); see branch-protection.md.- Consequences to internalize: (1) a regression that the suite would catch now lands on
mainand turns the post-merge run red, rather than being blocked pre-merge —maincan briefly break, so runcargo test --workspace --lockedlocally before merging anything non-trivial, or trigger this workflow on your branch via the Actions "Run workflow" button. (2)openapi.jsonis no longer auto-regenerated on PRs (that step is inside thetestjob); for server/API changes, regenerate it locally withOMNIGRAPH_UPDATE_OPENAPI=1 cargo test -p omnigraph-server --test openapiand commit it, or the strict drift check fails the post-mergemainrun. - Applying this policy: removing
Test Workspacefrom the JSON is inert until an admin runs./scripts/apply-branch-protection.sh. Run it immediately after this change merges — until then GitHub still requires aTest Workspacecontext that no longer reports on PRs, which leaves every open PR permanently pending (the job-never-reports trap).
- AWS feature build job:
cargo build/test -p omnigraph-server --features awson ubuntu-latest. - Windows binary build job:
cargo build --release --locked -p omnigraph-cli -p omnigraph-serveron windows-latest with smoke checks foromnigraph.exe version,omnigraph-server.exe --help, and PowerShell installer syntax. - RustFS S3 integration: spins up RustFS in Docker, runs
s3_storage,server_opens_s3_graph_directly_and_serves_snapshot_and_read, andlocal_cli_s3_end_to_end_init_load_read_flow. - release-edge.yml: on every push to main, retags
edge, builds Linux x86_64 / macOS arm64 archives and Windows x86_64 zip + sha256, publishes a rolling prerelease, then smoke-tests the Windows PowerShell installer againstedge. - release.yml: on
v*tags, builds the Linux x86_64 / macOS arm64 archives and Windows x86_64 zip release matrix, updates the Homebrew tap (scripts/update-homebrew-formula.sh) by pushing the regenerated formula toModernRelay/homebrew-tap, and smoke-tests the Windows PowerShell installer against the tag. - package.yml: manual ECR image build; emits two image tags per commit (
<sha>,<sha>-aws) via CodeBuild.