Publish OpenClaw packages from Garnix
Green CI alone is not enough for downstream Nix consumers: the user-facing and gateway package outputs must be top-level Garnix artifacts so machines can substitute them without local OpenClaw builds. Tests: git diff --check
This commit is contained in:
parent
7cbc79ce52
commit
fd30aad492
11
garnix.yaml
11
garnix.yaml
@ -1,8 +1,11 @@
|
||||
builds:
|
||||
include:
|
||||
# Single aggregator per platform.
|
||||
#
|
||||
# Avoids building openclaw-gateway multiple times across parallel CI jobs
|
||||
# (cache-miss races) and reduces total compute/quota usage.
|
||||
# CI aggregators prove package contracts.
|
||||
- "checks.aarch64-darwin.ci"
|
||||
- "checks.x86_64-linux.ci"
|
||||
# User-facing/component packages must also be top-level Garnix artifacts,
|
||||
# otherwise downstream machines can see green CI but miss the binary cache.
|
||||
- "packages.aarch64-darwin.openclaw"
|
||||
- "packages.aarch64-darwin.openclaw-gateway"
|
||||
- "packages.x86_64-linux.openclaw"
|
||||
- "packages.x86_64-linux.openclaw-gateway"
|
||||
|
||||
Loading…
Reference in New Issue
Block a user