Repository navigation
docs: upgrade OwlMail integration to 0.13.0 - #206
Conversation
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 |
|
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". |
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! 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". |
Update the current OwlMail integration from 0.9.0 to published 0.13.0 and synchronize the shell-capable receiver image to WebHook runner-7.3.4. Add an explicit
/app/owlmail healthcheck --containerprobe because the published image has no default Docker HEALTHCHECK or/appPATH entry.Update the existing example test and both language guides with backup/isolation/rollback instructions while preserving version-1 JSON, exact-body HMAC, the shared secret, command allowlist, strict mode, bounded concurrency/rate limits, loopback ports and disabled raw-body logging. Document the existing default receiver behavior: an invalid HMAC returns HTTP 500 as a rule-evaluation error without executing the command, which triggers bounded sender retries.
Validation: existing example race tests,
docker compose config, and strict MkDocs passed. The published-image Compose regression completed successfully: both services healthy, valid HMAC request 200 with field/correlation mapping, invalid signature 500 without command execution, and real SMTP callback plus captured-mail API verification. Temporary containers and staging volumes were removed. No application source or release tags change.