You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Prepare version-aware Email configuration and readback #5795
Make the existing Email setup recipe explicitly compatible with the tested legacy and 1.x runtimes, so the migrated service can be recreated from reviewed configuration.
Details
The native configuration, message-copy and rollback trials are complete. The checked-in compiler still targets the legacy schema. Add an explicit supported runtime selection while preserving the current serving defaults.
Checklist
Preserve the legacy recipe and reject unknown runtime selections.
Render and verify the 1.x field names, exact mailbox permissions, receiving aliases and client-address policy.
Bind the administration bundle and startup checks to the selected runtime.
Verify fresh setup, replay and refusal controls against both native versions.
Deliver through current-head validation and protected merge.
Dependencies
Part of #5387. Serving-store migration, encryption activation and single sign-on remain separately gated by their recovery and acceptance checks.
Notes
This records existing requested Email work investigated from 2026-11-02. This delivery stages compatibility; it does not switch the serving datastore or enable authentication changes.
#5586 - feat(email): verify live mailbox backup recovery [closed] #5533 - feat(email): move active credentials and recovery to infrastructure [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
This records a child delivery within the already-started Email work in #5387. Its first investigation began on 2026-11-02 at approximately 22:17 UTC; the board's First started date preserves that start rather than resetting it to issue creation.
At signed head 1515752dbc3c76bda8c596cad2639dc795c5c42f, the affected Go package, race checks and vet pass. Both checksum-verified UI bundles staged successfully. Isolated native trials with each matched server/CLI/UI combination completed fresh configuration and two replays, including receiving aliases. Initial native failures exposed a factory-resource URL mismatch and a test-credential validation issue; both were corrected and the trials rerun successfully.
This proves configuration preparation with synthetic fixtures. Production migration, encrypted serving storage, restored user data, sign-in acceptance and external delivery remain separate acceptance work under #5387. PR #5796 delivers this child only.
Verified the published Email bootstrap for the protected merge of #5796 at 09423afd7727c5487071e7c5396ad0812551fc9d. The mail configuration source tree matches the revision exercised in the two native setup and replay trials. Merged-main validation and the bootstrap build and publish run both passed.
An independent registry read verified the published tag's Cosign signature from the protected main workflow and matched the digest reported by that run: sha256:7b13b9820cf5aa5dbc3991452e131053dc9743b6ea7323d9ee993e4e2a59e489.
This completes the publication check for the version-aware bootstrap. The serving datastore, production sign-in and recovery acceptance remain tracked in #5387.
Activity
coderabbitai commentedon Nov 3, 2026
🔗 Related PRs
#5586 - feat(email): verify live mailbox backup recovery [closed]
#5533 - feat(email): move active credentials and recovery to infrastructure [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #5795 nonce=de1cc14d8e9f0c42549e0a0da201a072
devantler commentedon Nov 3, 2026
This records a child delivery within the already-started Email work in #5387. Its first investigation began on 2026-11-02 at approximately 22:17 UTC; the board's First started date preserves that start rather than resetting it to issue creation.
At signed head
1515752dbc3c76bda8c596cad2639dc795c5c42f, the affected Go package, race checks and vet pass. Both checksum-verified UI bundles staged successfully. Isolated native trials with each matched server/CLI/UI combination completed fresh configuration and two replays, including receiving aliases. Initial native failures exposed a factory-resource URL mismatch and a test-credential validation issue; both were corrected and the trials rerun successfully.This proves configuration preparation with synthetic fixtures. Production migration, encrypted serving storage, restored user data, sign-in acceptance and external delivery remain separate acceptance work under #5387. PR #5796 delivers this child only.
chore: agent-claim #5795 nonce=5137f584ff8c465acf963464c2975a3d
devantler commentedon Nov 10, 2026
Verified the published Email bootstrap for the protected merge of #5796 at
09423afd7727c5487071e7c5396ad0812551fc9d. The mail configuration source tree matches the revision exercised in the two native setup and replay trials. Merged-main validation and the bootstrap build and publish run both passed.An independent registry read verified the published tag's Cosign signature from the protected main workflow and matched the digest reported by that run:
sha256:7b13b9820cf5aa5dbc3991452e131053dc9743b6ea7323d9ee993e4e2a59e489.This completes the publication check for the version-aware bootstrap. The serving datastore, production sign-in and recovery acceptance remain tracked in #5387.