Repository navigation
feat(mail): prepare offline administration assets - #5316
Conversation
Validation for source
That local container test is additional evidence; the hosted Docker fixture on an internal network is still required and is running in CI. It also exercises unexpected-application refusal and identity/history preservation on replay. No production activation, DNS, Homepage or client acceptance is claimed here. |
Hosted native testing at Signed follow-up The focused pinned-server run now proves: positive bootstrap, extra-application refusal, bootstrap refusal, actual cleanup through the bounded inventory, and preservation of the original administration identity. ShellCheck and whitespace checks pass. The complete hosted suite must pass at this new head before review or promotion; the previous failed run is not counted. |
The supplementary static pass found a cache-pinning issue before provider review: Stalwart could reuse an old cached ZIP while bootstrap successfully verified a different file at the permanent local URL. The native regression reproduced that exact failure. Cache fix The regression now positively primes a previous cached interface, reconciles with the real image, requires all pinned served assets and confirms the original Application identity. Its native RED and GREEN were observed. Race tests, vet, ShellCheck, whitespace checks and UID 2000 asset/license readability passed. Static re-review found no further actionable issues. Current signed head is |
@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 17 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 |
CodeRabbit's authenticated command reply refused this exact-head request at 07:44:43 UTC on 2026-10-25 because its included review allowance was exhausted. The stated recovery is 18 minutes after that event. The current-PR review objects, conversation, threads and checks contain no delivered review or finding for this request; the no-gate guard returns ADMIT. This is a service limit, not a clean review. Continuing to the next provider under the existing review policy; no paid review is authorized. |
@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 it up! 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". |
Readiness for signed head
This source slice prepares verified offline administration assets. It does not claim a deployed mailbox, public route, Homepage tile, mail-app migration or production browser acceptance; those remain tracked by #5030. Proceeding through the protected queue at this exact head. |
The first queue attempt 40176242046 deployed successfully, but its required aggregate never executed: the hosted runner's setup timed out three times while resolving action downloads. The native timeline records removal for Fresh preflight still binds signed source |
Post-merge publication verified for merged source An independent anonymous pull and Cosign verification passed for that exact digest, the reviewed main-workflow identity, GitHub OIDC issuer, transparency record and merged source revision. Separately verified the index, runtime, configuration and attestation hashes, the matching source label, SPDX 2.3 inventory with 107 packages, and SLSA v1 maximum BuildKit provenance bound to the runtime digest and source revision. The first independent inspector expected the older SLSA predicate version and correctly refused it; inspection of the actual statement established the v1 schema, which the corrected verifier validates explicitly. This is publication evidence. Deployment, authenticated administration from Homepage, migration, direct delivery and the remaining real-mail acceptance criteria are still open under #5030. |
Actual published-image evaluation also passed for immutable digest Both administration and account pages, including every script/style referenced by their entry pages, matched the committed verified bundle. The expected native base-path rewrite was checked explicitly. The owned proof server was stopped and deleted successfully. This supplementary evaluation used Apple's Linux container runtime; the PR's hosted native proof used Docker. Neither is deployed Homepage/browser acceptance, which remains open with the rest of #5030. |
Why
Mail administration needs to open reliably even when the mail service cannot download its interface from the internet.
What
Bundle the verified Stalwart interface with the mail initializer and refuse unexpected administration settings. This prepares administration for activation; the public service and Homepage entry remain part of the mail rollout.
Part of #5030