Repository navigation
fix(email): select the verified image and observe proxy readiness - #5504
Conversation
Validation at The immutable image passed independent cosign verification against the main-only Email publisher and GitHub Actions issuer. The publisher run passed the source race tests, built the image, published it, and verified its signature. Native behavior will also be exercised by this PR's selected mail and gateway CI checks; they are still pending. Source-range review: registry signatures bind the old image to
This is a recovery prerequisite, not an availability pass. Promotion awaits settled CI and a current-head substantive review. |
Blocker: none Cleared 2026-10-28: PR #5503 merged as 20be922. Main publication run 40683516786 succeeded; independent Cosign verification bound the replacement digest to that exact source, repository, main ref, publisher workflow and issuer. Refreshing this draft image pin; fresh CI, review and protected deployment remain required. Previous record (historical): |
…ail-image-refresh-5504-8416
@coderabbitai review Validation at Both canonical KSail validations exited 0 and covered the administration bundle. A rendered before/after comparison proves exactly two image-reference replacements, with all other rendered bytes identical. Unrelated OCI Helm rendering remains incomplete on this host because its Docker credential helper is unavailable; fresh hosted validation remains required. Whitespace and the PR body contract pass. Correctness, security and simplification review found no additional change needed. The current main was integrated with a signed merge; no history was rewritten. Source-range review from The earlier publisher blocker is cleared. Fresh CI and this current-head review are pending, so the PR stays draft. #5448 remains open; client-identity activation, protected deployment and authenticated administration acceptance remain separate. |
|
|
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 56 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 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. Delightful! 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". |
@codex review |
|
Codex Review: Didn't find any major issues. Bravo. 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 Both canonical manifest validations, affected race tests and lint passed. Operator evaluation rendered both administration and proxy profiles and passed them through the actual pod/configuration readers, including their refusal controls. The current-head native integration job and complete Go suite passed. The image's published digest and signature were independently verified against the main-only publisher. Codex completed the exact head without findings (receipt); all four review surfaces are clear. The description and closing-reference guards pass. Every readable required gate passes; the opaque configured code-quality rule is independently unverified and remains enforced by GitHub's native CLEAN state and protected queue. Public Email administration still returns HTTP 503. This delivers the rollout prerequisite and compatible observation path; activation, real-client identity, authenticated administration and rollback acceptance remain on #5448. |
Why
Email needs the credential-preserving bootstrap image before transport changes can be rolled out safely. Its health checks also need to recognize the reviewed client-identity proxy.
What
Selects the verified image and checks both supported deployment profiles, including proxy readiness and configuration continuity. Transport activation and working administration remain separate acceptance steps.
Part of #5448