diff --git a/kas/forgefirm-glowforge.lock.yml b/kas/forgefirm-glowforge.lock.yml
index 173d51e..9cfeddf 100644
--- a/kas/forgefirm-glowforge.lock.yml
+++ b/kas/forgefirm-glowforge.lock.yml
@@ -11,4 +11,4 @@ overrides:
     meta-freescale-distro:
       commit: b9d6a5d9931922558046d230c1f5f4ef6ee72345
     meta-openglow:
-      commit: f012d8e82aa0dbfa511214e46a1e13559b1a0d74
+      commit: b7626be45c7708a8e71bd03af61ca968796fc8f7
diff --git a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc
index 3aaa7d1..e98a47e 100644
--- a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc
+++ b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc
@@ -4,5 +4,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 = "c274f19b09f2c0b0b553edbbe56cb9d9c193703e"
-PV = "0.1.30"
+SRCREV = "c9e3347bdcc6535056e5de5e1d4bd38e93de9494"
+PV = "0.1.31"
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 33eb272..240c486 100644
--- a/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc
+++ b/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc
@@ -6,9 +6,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 = "021323ddfbdfcd131831f916ad3c0ef1d7a59071"
+SRCREV = "0f59c547b6e8418712ab9e000c58eb1975c29d79"
 
 # 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.31+git"
+PV = "0.1.32+git"