fix: validate v3 qualification environments with separate tooling pins - #139
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
1 participant
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.
Partial qualification tooling work for issue #119. Accept validated v3 prepared environments; pin exact test-tooling commit and Git tree digest separately from unchanged frozen product source. Four-file test-only allowlist and clean-checkout checks refuse product/pin substitution. No product/runtime/dependency/version changes. Component fixture suite passes; root coordinated compatibility check passes all six components with zero qualification credit. Executors remain OPEN. No AWS allocation, deployment or publication. Do not close the owning qualification issue from this PR.