Repository navigation
ci(distribution): prove install claim verify upgrade on a clean host - #100
Merged
teckedd-code2save merged 3 commits intoSep 19, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
Turn #93's distribution contract into a repeatable end-to-end acceptance test on a disposable Linux host.
Workflow
Adds
.github/workflows/distribution-acceptance.yml.It runs:
mainFor automatic runs it first checks whether the distribution surface changed, so unrelated application changes skip the expensive clean-host test.
Acceptance flow
On a fresh GitHub-hosted Linux machine:
scripts/install --jsonclaim_requiredwith loopback local/claim URLs127.0.0.1/root/.ssh/api/auth/claimalready_claimed / changed:false--previewand prove it is non-mutating--upgradeupgrade_complete, DB backup evidence and digest-pinned runtime image--uninstalldataPreserved:trueand that the DB volume still existsEvidence
Uploads a 7-day acceptance artifact with:
Claim token, claim URL and claim path are removed before the artifact is written.
Guardrail
A Vitest file parses the workflow YAML and locks the install → claim → verify → upgrade → uninstall contract so workflow syntax/intent is checked on PRs even though the workflow itself is triggered after deployment.