Repository navigation
fix(ci)!: retire catalogue-only .NET workflow - #708
Conversation
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Corrected head CodeRabbit's direct repository-scoped allowance evidence, freshly re-read, is still zero included reviews after the 07:08:25 UTC review under its one-per-hour plan. That limit remains applicable conservatively until 08:08:25 UTC. No redundant CodeRabbit request or paid overage is used. With no current-head review already delivered here, the ordered substantive review proceeds to Codex. |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep them coming! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Superseded by the current blocker record #708 (comment) (the head moved to daf5bad and this record no longer applies). The record marker was removed so the PR carries exactly one record. Earlier recordBlocker: #271 | upstream | last-verified 2026-10-22: At unchanged head f4150b7, three self-repository scanner threads remain unresolved. GitHub supports the recommended syntax, but the mandatory catalogue credential-source guard cannot classify it yet. A disposable complete-source probe passes unchanged, then exits 2 with UNKNOWN unresolved or mutable source when only the two native fixture references use the recommended syntax. No PR source or guard was changed. Resume after #271 delivers source classification and its local, composite and cross-repository resolution proof; then adapt the fixture and preserve consumer-root isolation, token/source-state controls, all native OS jobs, complete CI and current-head review. Existing green CI and review do not clear the three scanner findings; no dismissal, waiver or promotion. |
The three self-repository findings are now fixed at signed head The credential auditor now traverses native references using the defining file's immutable revision, independently of workspace checkouts. Regression tests reject mutable/path aliases, follow nested credentials and prove an older pinned composite cannot substitute a newer caller's leaf. The native fixtures use that binding without checking catalogue source into the consumer workspace. The isolation test uses complete external action source and reproduces the original failure with an in-workspace copy. Local validation passed: all fourteen deployment baseline checks, race-enabled auditor tests and vet, 44 credential regressions, 26 native-fixture refusals, the real isolation negative control, scope/required-aggregate controls, 20 instruction controls and 40 README cases. The scanner reports zero self-repository findings on these three new references; the separate catalogue-wide migration remains tracked in #271. Both new commits are GitHub-verified signed. Fresh complete hosted CI and current-head review remain required before promotion. |
Blocker: #655 | upstream | last-verified 2026-10-22: GitHub's Actions Results incident (githubstatus: investigating, re-checked 15:20Z) still delays completed job results. At unchanged signed head daf5bad, CI 39793830610 failed only the native cache observer and its dependent aggregate; a later complete read showed all nine fixture jobs successful, so this is not a demonstrated cache-policy violation. The earlier #271 source-classification blocker is superseded. Resume after GitHub reports recovery (and #719 for #655 lands): run complete CI again at the then-current head (not failed-jobs-only), obtain a fresh substantive review, and revalidate findings before promotion. |
@coderabbitai full review |
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 51 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@codex review |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Ready at signed head
The zero-product .NET wrapper can now be retired while retaining the private native fixtures and the template's repository-level enforcement. Protected merge and the major release/publication checks remain the final delivery steps. |
The .NET-wrapper retirement is delivered and verified:
#703 is complete. This does not claim that the separate World runtime/migration gate or KHoist publication migration is complete. |
Why
The shared .NET workflow has no remaining product callers, but is still published solely to run catalogue fixtures. Keeping that extra layer obscures ownership and contradicts the portfolio workflow convention.
What
Run those fixtures in the catalogue's own CI and share only their local setup steps. Preserve all three operating systems, credential restrictions, source-state checks and consumer-isolation coverage, and update the action guide and workflow catalogue accordingly.
Fixes #703
💥 Breaking change: the unused public .NET test workflow is removed; consumers use the maintained test action in their own CI jobs.