Repository navigation
fix(ci)!: keep release recovery repository-owned - #723
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 |
Fixed the two same-repository security findings at signed head Both internal offline-fixture calls now use native The new native-call control failed against the original guard. Both real call forms and all non-call controls now pass, along with the complete existing wiring suite, recovery authority/projection controls, documentation/layout checks, shellcheck and the full reached credential graph with all 44 real-source refusal controls. No scanner or required check was disabled. Fresh native CI and a substantive current-head review remain required. |
@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 34 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 |
Review availability for unchanged green head CodeRabbit's authenticated request received refusal 6352139427 at 21:53:25 UTC, stating that its included review is unavailable for 34 minutes. This PR-scoped refusal is not a review; no usage-based billing is authorized. A complete current-head no-gate scan confirms no delivered CodeRabbit verdict or finding is being discarded. The ordered loop therefore advances to Codex, with full native CI, the published body and both addressed native-security threads already clear. A substantive exact-head review is still required. |
@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". |
Ready at signed head The former unused shared recovery entry is now repository-owned and manual; its internal offline fixture has no publishing job or secrets. Independent projection, generator equality, refusal, credential-boundary and actual native-call controls pass. Existing admission, least privilege, default-off consent and build-before-credentials controls remain intact. Self-review, simplification and security passes found no outstanding issue. Promotion does not authorize a production recovery run, retire #603 or complete legacy Actions deletion under #240. |
Delivered #722 through protected merge and normal publication.
The unused public recovery export is gone. Recovery is repository-owned and manual; the internal offline fixture has no publisher or secrets. No production recovery was activated, #603 remains a separate rollout gate, and legacy Actions deletion remains open under #240. |
Why
Release recovery is advertised as shared automation even though no product uses it. That makes the catalogue harder to navigate and encourages centralizing a procedure before there is a real need.
What
Keep recovery as this repository's manual operation, preserving confirmation and credential safeguards. Separate its internal offline validation from supported consumer interfaces and update the ownership guidance and usage documentation.
Fixes #722
💥 Breaking change: the unused reusable recovery interface becomes manual-only; a future product must own its recovery procedure until repeated use justifies extraction.