mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 01:01:12 -07:00
ScottW514
7a9f655916
FORGEFIRM_RELEASE = 0.0.5 and the acceptance artifact that authorizes it:
campaign c-20260915231006 on the dev image 20260915225440 (grbl pin
0.1.17, forgefirm 52a9138), authorized, all required tests passed on the
bench reference.
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.5"
|