Release v0.0.3: the version and the acceptance artifact for this tree

mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-27 08:41:13 -07:00

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.

This commit is contained in:

ScottW514

2026-09-11 14:55:25 -04:00

parent 5c93e49c8c

commit b7a595ced7

3 changed files with 21063 additions and 1 deletions

									
										meta-forgefirm/recipes-forgefirm/images/forgefirm-release.inc
									
		+1
		-1
	
												View File
												
				@@ -15,4 +15,4 @@

				# 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.2"

				FORGEFIRM_RELEASE ?= "0.0.3"