From 908e0c76b8a9b9637e560fe6cd8f36371056470f Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Sun, 23 Aug 2026 11:27:36 -0400 Subject: [PATCH] Pin forgefirm-app to 351a623: gfcloud --no-hunt, the markers read first thing --- .../recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc b/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc index fc751da..954da4f 100644 --- a/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc @@ -4,9 +4,9 @@ # because the component entry already identifies the pinned source # (forgefirm-image-manifest.bbclass). The python3-gfhardware recipe in # meta-glowforge-bsp pins the same repository; move both together. -SRCREV = "b7e80359cdfcb4863ab0fe1fb07e7748f9ff3a42" +SRCREV = "351a623c75ec0119e191dfdf7e86fef8488c5108" # Bump PV with every SRCREV move: the hash-derived package version is not # monotonic on its own and buildhistory QA fails the build when it sorts # backwards. -PV = "0.1.19+git" +PV = "0.1.20+git"