From 2936890eaa6e9df94a3a798b71bf4b8be0561257 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Wed, 9 Sep 2026 08:43:45 -0400 Subject: [PATCH] Pin forgectrl on the revision CI passed forgectrl 6040e64 carries the three fixes behind the pinned 93fb22e: the test header reached the way the sibling tests reach theirs, the key added to /status carried in the panel dev-server mock, and the lens test's carriage driven by the sweep's own steps rather than by a clock. The shipping behavior is unchanged from 93fb22e; the pin names what passed. Verified with bitbake -c fetch. --- meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc index cf71956..4a8472a 100644 --- a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc @@ -2,5 +2,5 @@ # only SRCREV and PV here - the image manifest leaves *-pin.inc out of the # layer content hash because the component entry already identifies the # pinned source (forgefirm-image-manifest.bbclass). -SRCREV = "93fb22e7aaa84f305dbdb51a5812f76d586fac56" +SRCREV = "6040e64a388005761d7598a5edbc46e55d38af76" PV = "0.1.9"