[WP02 · SubStep 02.05] Enforce dependency admission and deliberate stable publication - #59
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.
The current producer dependency closure is now an executable admission policy: 31 NuGet and 10 existing Python tooling coordinates, bound to exact source/lock inputs, reviewed package licences and an append-only upgrade receipt. Existing native/source provenance and package legal gates retain their closed native inventory. Historical coordinate hashes prevent a reviewed successor from rewriting an immutable version; major framework changes require an explicit runtime-posture assessment.
Adds deliberate canonical vX.Y.Z publication through the existing original-candidate pipeline, with peeled tag/source identity, main ancestry, stable closure checks, restricted OIDC and a shared non-cancelling publication queue. Main prerelease versions remain unchanged. No tag was created. The coordinator configured the nuget environment to preserve main and permit v* tags.
Validation: 12 targeted offline policy/publisher tests passed; source provenance and native provenance checks passed; complete diff and whitespace review passed. Existing Windows/Linux CI remains required. Stable publication, product runtime and consumer execution were not run. No packages/toolchains were installed or public artifacts downloaded.