Each version pairs its build hash with the commit it came from, so engineers can match a tested binary to the exact source change without digging through separate notes.
Changelog
Notes that travel with the build
Changelog entries stay attached to each version, so reviewers can see what changed between builds before deciding which one to test next.
Lifecycle
From staging intake to archive
01
Stage the build
Upload a new build into its own staging slot so it never overwrites an active test.
02
Review the changes
Check the build hash, commit record, and changelog against the previous version.
03
Promote or hold
Move a verified version forward for testing, or keep it staged while issues are open.
04
Archive history
Retire superseded builds while keeping their staging lifecycle on record.