From cd2107fe3ca5e272a21f06ab31c7bf996052c807 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Sat, 8 Aug 2026 16:51:10 -0400 Subject: [PATCH] docs/update-system: add the tested_against_gf release-metadata field Record the Glowforge service/firmware version each release validated cloud mode against, kept distinct from the version cloud mode advertises; forgectrl reads it to warn when the live service has moved past it. --- docs/UPDATE-SYSTEM.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/UPDATE-SYSTEM.md b/docs/UPDATE-SYSTEM.md index 358ae46..8294499 100644 --- a/docs/UPDATE-SYSTEM.md +++ b/docs/UPDATE-SYSTEM.md @@ -152,6 +152,15 @@ demonstrably untouched.* - One version source: `FORGEFIRM_RELEASE` = git tag = `/etc/forgefirm-version` = `.fw` meta-version; the script enforces agreement. +- `tested_against_gf`: pinned release metadata naming the Glowforge + service/firmware version this release validated optional cloud mode + against. `release.sh` sets it beside `FORGEFIRM_RELEASE` and writes + it into the `/etc/forgefirm-version` companion and the `.fw` fwup + meta. It is deliberately distinct from the version cloud mode + advertises to the service; forgectrl reads it to warn when the live + Glowforge service has advanced past the tested version (cloud mode + may break), and falls back to the advertised version on images that + predate the field. - `release.sh --dev` packs a **dev-key-signed** `forgefirm-dev.fw` from the release rootfs for the GUI upload path (decides open question 4: dev archives are signed with the dev key, never