From da0299924fdef3cb875fc03b69bb66eec3663e38 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Fri, 4 Sep 2026 10:15:02 -0400 Subject: [PATCH] pins: forgectrl at the revision the campaign ran The request-body cap is on the bench. Image 20260904131106 carried forgectrl ff89288 through a build overlay, and campaign c-20260904132654-d731 authorized it, 56 of 56. The pin now says what the campaign ran. --- 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 d094b08..d6b0bd8 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 = "8ef95091b7f22fa100814147bef437602d96dc26" +SRCREV = "ff89288cd321033a2ee33117729f58c6f4918228" PV = "0.1.2"