Release v0.0.1: pin meta-openglow, refresh the lock, add the acceptance artifact

Browse Source

The kas configuration takes the pinned-remote meta-openglow block, with
its commit in the lock file (d655e1e, the read-only rootfs), so a fresh
clone builds the release without a sibling checkout. The lock keeps the
upstream layers where they were.

releases/v0.0.1 carries the acceptance artifact the bench exported for
this image: campaign c-20260909160235-7649 on 20260909150456, 83 tests,
83 satisfied, none inherited, release authorized. The release gate
recomputes every test's fingerprint from the manifest inside the release
rootfs and signs only when the recorded results agree.

...

This commit is contained in:

ScottW514

2026-09-09 13:15:37 -04:00

parent 4a95595afd

commit b2f50ad765

4 changed files with 21412 additions and 11 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

releases/v0.0.1/acceptance.json

+21301

File diff suppressed because it is too large Load Diff