Repository navigation
fix: keep the release source-provenance check on current paths - #117
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.
Fix the relocated Daimon broker tamper target and verify it matches the shipped bytes. Check native/integrity rejection diagnostics and tamper valid lockfile whitespace to isolate archive hashing.
Run the same pinned offline gate on every PR/main revision in parallel (~6 minutes). Bump package and lock versions to 0.1.27.
Validation: all four CI checks passed, including the real offline artifact build (6m47s) and full coverage. All four verifier-bypass mutations turned the assertions red. Typecheck and script tests passed locally; the full local Docker gate hit amd64 emulation crashes.