Files
forgefirm/kas/forgefirm-glowforge.lock.yml
T
ScottW514 b2f50ad765 Release v0.0.1: pin meta-openglow, refresh the lock, add the acceptance artifact
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.
2026-09-09 13:15:37 -04:00

15 lines
416 B
YAML

header:
version: 14
overrides:
repos:
poky:
commit: 70ed6f677234d32198371a030178d2f272cf2d94
meta-openembedded:
commit: b0c2c648a1af89e7a8dd4c2ec841f3bc0ed0ccb9
meta-freescale:
commit: b699d026506a6fc402e03afb432dcabd3d81c7ab
meta-freescale-distro:
commit: b9d6a5d9931922558046d230c1f5f4ef6ee72345
meta-openglow:
commit: d655e1e58c97224236f21472b02cb19f32eab982