Repository navigation
Register disabled publication workflows and record new-code acceptance - #32
Merged
Merged
Conversation
This was referenced Oct 24, 2026
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.
Core's reviewed NuGet preparation/publishing templates are not yet discoverable as GitHub workflows. This change moves them into
.github/workflowswith their literal-false job guards intact, pins the publication verifier to reviewed workflows main68683cdc6a268328ed6ce686d26c26ace479eab0, and records the exact preparation-file hash. The actual preparation workflow ID remains deliberately zero, including both publication-trigger checks, until GitHub assigns it after registration. The verifier continues to reject that incomplete registration.Existing CI, Sonar and Dependabot Actions and the analysis runner pin are unchanged. The old publisher and NuGet policy remain unchanged. No environment, credential, tag rule, release tag, upload or publishing activation is included. The migration plan records the separate registration, rehearsal, legacy-publisher removal and controlled activation steps; this PR does not complete #29.
The same change records #30's completed central evidence on main
42874ff085ed01c2d06016195360dbdf3d910fe2: CI 40078055900 and Sonar 40078086628, both attempt 1, passed. Sonar reports four new lines to cover at 100% new-code coverage, all eight tests, imported Result.cs coverage and a fresh exact-attempt readiness receipt. The accepted baseline, all six gate conditions, 27 frozen profiles, disabled small-change exemption and absence of coverage exclusions were verified unchanged. Isolated local failure/recovery evidence is explicitly distinguished from the central successful run.Validation: both new standby workflows pass actionlint; all 11 offline recorder cases pass using the relocated actual workflow; Core Release build has zero warnings/errors, 8/8 tests pass, CSharpier and vulnerability audit pass. Shared main CI passed all checks, including 1,086 tests per platform on Windows and Ubuntu. No existing Actions file differs from main. Hosted CI 40078692007, attempt 1 passed for
745deef0e3e9ac653160e1010141d1da079bbf82, including 8/8 tests; publication was skipped. #30 is closed with its verified acceptance evidence; #29 remains open.Refs #29 and #30. Please review; do not activate publishing or merge automatically. Core has no separate E2E workflow; hosted publication integration remains pending.