mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 09:11:11 -07:00
ScottW514
c0d4302d73
FORGEFIRM_RELEASE 0.0.4. The acceptance record that authorizes this build: campaign c-20260912182427-e1ee on dev image 20260912180956 (manifest 8bb5b6f3), 85 tests, 85 satisfied, 0 required, exported 2026-09-12T19:21:35Z. The release notes in releases/v0.0.4/notes.md name this the first public beta; the pipeline takes a release's notes.md, when it carries one, in place of GitHub's generated notes.
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.4"
|