From 0dc8c746e59b5d8c170591b878db344006957e7e Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Mon, 7 Sep 2026 18:11:18 -0400 Subject: [PATCH] pins: forgectrl, grblHAL-glowforge and the app at the XY microstep revisions forgectrl 0.1.6 (b1eee4d): the xy_microsteps setting and the quiet hold route. grblhal-glowforge 0.1.5 (48d5f1d): the XY scale, tick and stop ramp derived from the microstep mode, plus the producer lead ceiling. forgefirm-app 0.1.25+git (d1c47b8): the checked header keys note; the python3-gfhardware pin in meta-glowforge-bsp moves with it. Fetch-verified with bitbake -c fetch. Pin bump only: the acceptance consequence is the catalog invalidation the manifest already derives. --- meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc | 4 ++-- .../recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc | 4 ++-- .../grblhal-glowforge/grblhal-glowforge-pin.inc | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc index f3b62e6..836d25d 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 = "e27b4128e7f98b7b06e3d68231f429ec8d87ff4a" -PV = "0.1.5" +SRCREV = "b1eee4d9c08384b7c79ed61d6bb903324138fca1" +PV = "0.1.6" 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 57df9be..ae73a5c 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 = "cff69527ce9f91ae7c85e0ad7edb10d8b5c37000" +SRCREV = "d1c47b859f6ae88c75c18ff8f70480453e7f4879" # 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.24+git" +PV = "0.1.25+git" diff --git a/meta-forgefirm/recipes-forgefirm/grblhal-glowforge/grblhal-glowforge-pin.inc b/meta-forgefirm/recipes-forgefirm/grblhal-glowforge/grblhal-glowforge-pin.inc index c7dd755..7dfad45 100644 --- a/meta-forgefirm/recipes-forgefirm/grblhal-glowforge/grblhal-glowforge-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/grblhal-glowforge/grblhal-glowforge-pin.inc @@ -2,5 +2,5 @@ # changes; keep 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 = "96906b6caa1d68a7a3c126cd3c6ee337e042eb64" -PV = "0.1.4" +SRCREV = "48d5f1de5b98664abf73164d52a8a81942eb0ad7" +PV = "0.1.5"