Repository navigation
Activate Net ordinary V2 settlement with CLI 0.1.5 - #107
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.
Net's ordinary V2 receiver was prepared with dedicated custody but hard-disabled. This change enables its protected-main, secret-free preflight and a bounded
ordinary-v2credential job. The job rechecks the exact-run receipt and current protected source, verifies the immutable public Coordination CLI 0.1.5 release archive SHA-256, installs from that local archive, and executes onenet-v1settlement attempt using only the three dedicated secrets.The installed policy pins CLI source
1268908d2d5a38d30a764c927f3e0591e53138aaand release archive SHA-2563567a92825917a7d537f6c5c545d3a7947bc35edd666fc3a1898de3bf97267c9. The non-draftv0.1.5release and exact source tag were independently read back; its package matches the prepared artifact byte for byte. The release readback confirms identical GitHub Packages bytes and identical nuget.org payload after NuGet signing, and a public-only install and invocation passed. Fresh Net API readback matched repository identity, all four required App-bound checks and producer workflows, environment branch policy, and the three dedicated secret names. Shared Authority writer and integrity rulesets match the pinned anchor.Validation: Net observer tests 6/6; qualifier tests 4/4; release source check; locked restore, Debug build with zero warnings, and 29 .NET tests using an isolated NuGet cache. The initial shared-cache restore returned
NU1403forFSharp.Core 10.1.401; clean-cache locked restore passed. All four native required checks remain in place. After exact-head merge, the protected-main workflow and independent Authority readback must establish settlement, followed by a normal whole-runSettlementAlreadyCompletererun.