From ea6ac54ab3a2ada20cabe6bd3f4260edff3c52e2 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Mon, 14 Sep 2026 19:45:44 -0400 Subject: [PATCH] Pin forgefirm-app 0.1.29 The cloud client: the laser latch unlocks at the run and nowhere earlier, the warm-up is supervised, a live feed must land and finish, fire needs a power byte first, the homing runner always stops (python3-gfhardware 5ca279a; the pin also carries the "setup" naming in the comments and the LF normalization). Bench-proven with cloud.dark-print, cloud.verdict-refuse and motion.deadman on the bench reference. --- .../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 18c9e3c..9aa2c2c 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 = "56f134a1e6393a2096c16e8226027fbbd38d79c7" +SRCREV = "5ca279a1f6008ddf6e19a17c6d6375972d27ed7c" # 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.28+git" +PV = "0.1.29+git"