From 6e4a26ac6152b99b911ac80892e52945433b3a69 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Wed, 19 Aug 2026 17:25:42 -0400 Subject: [PATCH] Bump the forgefirm-app pin alongside python3-gfhardware Both recipes pin the same repository and the pin files say to move them together. Documentation only on this side: the cloud doc now records what the factory enforces from the pulse header, and what it does not. --- .../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 929e4ff..716ed0a 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 = "81500ae5aed3d20a7079145c5af3c68a22cd5a48" +SRCREV = "a3907f6b24134aeb3ad3812eed55d05834e8320b" # 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.9+git" +PV = "0.1.10+git"