What it is
adapter-owlpost.
Mailer port over the Owlpost REST API for the Cratefield harness (issue #591). Uses the runtime's HttpClient port — no reqwest, no vendor SDK — so it runs unchanged on Workers (worker::Fetch) and natively. It is the second mail provider alongside adapter-resend, and speaks the same Resend-compatible POST {base}/v1/emails wire.
From the crate’s own README.
Ports
Implements Mailer
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 5 versions recorded, newest first. Every published version is on crates.io.
Other
- updated the following local packages: cratefield-core
3 earlier versions 0.1.0 to 0.2.1
Added
- adapter-owlpost sending domains — create, list, get, verify, delete (#681) (#797)
- adapter-owlpost suppressions and topic naming (#669) (#795)
- adapter-owlpost typed webhook events and a verify-then-parse entry point (#668) (#796)
- adapter-owlpost inbound messages — list/search, held, get, raw, reply, release (#682) (#798)
Changed
- Breaking: requires
cratefield-core0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).
Other
- updated the following local packages: cratefield-core
- Breaking: requires
One of 76 crates in the harness, all of them MIT and all of them in one repository.