fix: scope release evidence requirements to affected hosts - #134
Merged
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.
Release validation previously required fresh live receipts from every host for every version. This change selects required hosts from changes since the previous reachable release tag, excluding the current version tag.
Validation: 44 trust tests, four workflow tests, and 24 executable CLI probes passed. Regression tests failed before the fix; sabotage checks caught forced all-host requirements and disabled required-host checks. All seven PR checks passed, including Node 18 and Node 20 verification.
Release 1.2.0 still requires current evidence from all 11 hosts because it contains shared pipeline changes since v1.1.0. No release was published and no new native-host runs were performed.