From 722de73a39c6bae59fba2109a993cc5babe244e6 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Tue, 8 Sep 2026 13:37:13 -0400 Subject: [PATCH] pins: forgectrl 0.1.7, grblhal-glowforge 0.1.7, forgefirm-app 0.1.26+git The three components carry documentation-only commits: the README becomes an index card, AGENTS.md lands, and the comments that pointed at the retired BRINGUP.md now point at the documentation site. The pins move because the tree is already past the image that 20260907224817 built: a comment in the kernel config fragment glowforge.cfg changed the meta-glowforge-bsp layer content hash, which the manifest counts as a platform change. Measured against that image's manifest: meta-forgefirm and meta-openglow-core are unchanged, meta-glowforge-bsp is not. A fresh image build and a full acceptance campaign therefore precede any release, and holding these pins back would buy nothing. Verified: every pinned revision is on its public remote, and bitbake -c fetch resolves all of them. --- 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 836d25d..366afda 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 = "b1eee4d9c08384b7c79ed61d6bb903324138fca1" -PV = "0.1.6" +SRCREV = "692e4d8ff689d6752b347ca8cc0202f9ad63a320" +PV = "0.1.7" 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 ae73a5c..a8d76f3 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 = "d1c47b859f6ae88c75c18ff8f70480453e7f4879" +SRCREV = "dae315ea660a9db5ef7cd624396eabe3c5a6e626" # 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.25+git" +PV = "0.1.26+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 2aeb212..cd401dd 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 = "e2ba043394ff7f5324e469f044f9653538130399" -PV = "0.1.6" +SRCREV = "d902e37e11530e8f7f48eefdfa62d8191f8c718a" +PV = "0.1.7"