Repository navigation
Verify pinned package identities in native artifacts - #12
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.
Completes the native canary source-identity gate before first execution: exact installed Conda name, scientific version, build, filename, subdir and SHA256/MD5 must match the reviewed contract independently in OCI and SIF. Binds package identity to existing schema-v1 build inputs. No factory, Dockerfile, contract-version, registry or publication change. Adds 84 negative package checks and durable reconciliation-failure summary. Full local suite: 8392 passed, 13 skipped, no failures. Adapter suite: 154 tests. Ruff and actionlint passed.