mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 16:51:12 -07:00
ScottW514
b7a595ced7
FORGEFIRM_RELEASE takes 0.0.3. The file sits outside the layer content hash, so the bump changes the version and invalidates no acceptance result. releases/v0.0.3 carries the artifact the bench exported for this image: campaign c-20260911182256-078f on 20260911172215 (dev), manifest identity fb24c3f4508ae54592f8d0b98ed0b2a07a933274980d8c1e4e5a967618ef9bd8, 83 tests, 83 satisfied (57 inherited), 0 required, release authorized. The release gate recomputes every catalog test's domain fingerprint from the manifest inside the release rootfs and signs only when the recorded results agree. The release carries, since v0.0.2: the lens frame in one place, so every Z a commissioning card sends comes from the settings the controller opens its Z limit from (the tail at the head's reference, the focus window written before the card's controller starts, every program judged against the reach before its first line goes out); the commissioning sheet acceptance test run as a fresh machine's; and the CPU percent on /status that holds across a status read inside the same scheduler tick as another reader's. Components: forgectrl 0.1.20, grblhal-glowforge 0.1.11, forgefirm-app 0.1.28+git, kernel-module 0.0.5, meta-openglow ced2af2.
19 lines
959 B
PHP
19 lines
959 B
PHP
# The release version, and nothing else.
|
|
#
|
|
# This file is metadata, not platform content: the image manifest leaves
|
|
# it out of the layer content hash the way it leaves out the component
|
|
# pin files (forgefirm-image-manifest.bbclass,
|
|
# FORGEFIRM_MANIFEST_VERSION_SUFFIX). A version bump therefore changes
|
|
# the version and invalidates nothing, so the number can be set at the
|
|
# moment a release is cut rather than before the campaign that authorizes
|
|
# it. Setting it inside forgefirm-image.bb instead would hash as layer
|
|
# content and invalidate every acceptance result, which is what it did
|
|
# until v0.0.1.
|
|
#
|
|
# Nothing else belongs here. The version is still proven end to end:
|
|
# scripts/release.sh reads FORGEFIRM_RELEASE from this file and requires
|
|
# it to equal the rootfs stamp, the .fw meta-version and the release tag,
|
|
# and the acceptance test image.health compares the stamp on the running
|
|
# machine with the manifest's.
|
|
FORGEFIRM_RELEASE ?= "0.0.3"
|