Repository navigation
chore: register disabled NuGet workflow identity - #33
Merged
Merged
Conversation
11 of 12 tasks
This was referenced Oct 25, 2026
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.
Refs #29.
GitHub assigned preparation workflow ID
394955059after the disabled workflows merged. Bind that ID in the publication policy and both trigger checks, refresh the preparation file hash, and document the registered identities and verified main evidence.Both NuGet job guards and all publication step guards remain literal false. This does not activate publishing. CI, Sonar, Dependabot, permissions, environments, NuGet policies, release tags and other repositories are unchanged. Hosted rehearsal and the separately approved legacy-publisher cutover remain outstanding; #29 stays open.
Validation: actionlint; exact registration-only workflow diff and preparation-byte hash checks; 11/11 offline recorder scenarios; clean Release build; 8/8 Core tests; CSharpier; no vulnerable dependencies. Merged main
06953d0passed CI and Sonar: 100% overall/new coverage across four new lines, no findings, accepted baseline and policy unchanged. Exact-head PR CI 40080112424, attempt 1 also passed for18c14b5d4138cf0419e1d93c3adc121f867e5f28; the publisher was skipped. Core has no separate E2E workflow.