Pin forgefirm-app to a3ca36f: gfcloud --offline

The same python3-gfhardware commit meta-openglow pins; the cloud client
learns the offline service (actions on /run/gfcloud-offline.sock, no
web session) for the acceptance tests.
This commit is contained in:
ScottW514
2026-08-22 19:20:38 -04:00
parent 9cc2e4eef4
commit 628f2f7a7f
@@ -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 = "e65cfc286a352b6a73aa64f973d1864cdc1e3f34"
SRCREV = "a3ca36f68b01fab968f6062183d2d94ab53e3583"
# 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.16+git"
PV = "0.1.17+git"