CRATEFIELD
Get started with Harness Join the waitlist

adapter-resend

Mailer over the Resend API, through the runtime's HttpClient port.

With cargo

cargo add cratefield-adapter-resend
crates.iodocs.rsSource

What it is

adapter-resend.

Mailer port over the Resend REST API for the Cratefield harness. Uses the runtime's HttpClient port — no reqwest, no vendor SDK — so it runs unchanged on Workers (worker::Fetch) and natively.

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.

  1. 0.4.3

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core

  2. 0.4.2

    crates.ioReleaseDiff

    Added

    • core report per-provider mailer status in /__health (#793) (#845)
    • providers() reports the one provider behind the adapter — resend, configured or not, with health left unknown because whether the key works is only learned by sending (issue #793).
3 earlier versions 0.3.1 to 0.4.1

  1. 0.4.1

    crates.ioReleaseDiff

    Other

    • Inbound mail: a verify-then-parse source in core, a Resend inbound adapter, and ADR 0028 for channels (#563) (#734)

  2. 0.4.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.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

  3. 0.3.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules