The appliance image bakes the RigForge tree at commit 32be3a4 (the rigforge#330 merge on their develop) because no tagged RigForge release includes appliance mode yet — recorded in the image at /opt/rigforge/RIGFORGE_REF and pinned via ARG RIGFORGE_REF in the Containerfile. A commit pin on a moving integration branch is the wrong long-term anchor for a release artifact.
When RigForge cuts its next release (their side of the pithead#797 R1 work), move RIGFORGE_REF to that tag and record the version-compat note the rigforge#1 build/release section calls for.
🤖 Generated with Claude Code
The appliance image bakes the RigForge tree at commit
32be3a4(the rigforge#330 merge on their develop) because no tagged RigForge release includes appliance mode yet — recorded in the image at/opt/rigforge/RIGFORGE_REFand pinned viaARG RIGFORGE_REFin the Containerfile. A commit pin on a moving integration branch is the wrong long-term anchor for a release artifact.When RigForge cuts its next release (their side of the pithead#797 R1 work), move
RIGFORGE_REFto that tag and record the version-compat note the rigforge#1 build/release section calls for.🤖 Generated with Claude Code