chore(release): v0.22.0

[fclairamb]

🤖 I have created a release beep boop

0.22.0 (2026-09-02)

Features

• heartbeat: add an embedded TCP/UDP push transport for constrained devices (#301) (ecde564)
• heartbeat: add an embedded TCP/UDP push transport so constrained (ecde564)

Bug Fixes

• deps: update github.com/dop251/goja digest to 43234fa (#300) (9c9b3e2)
• deps: update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.110.0 (#298) (2482111)

---

This PR was generated with Release Please. See documentation.

[fclairamb]

Release v0.22.0

The headline is push-based heartbeats for constrained devices: two optional listeners (port 4001, TCP and UDP, off by default) accept a one-line beat in either a plaintext (SP1) or HMAC-signed (SP2) form, so a microcontroller or cellular modem can report in without a TLS stack, a certificate store or a correct clock. Replay protection is a database-enforced strictly-increasing counter, require_hmac closes the plaintext form per check, and failed beats get no reply at all so the listeners give away nothing about which orgs, checks or tokens exist. Beats can also carry readings — battery voltage, signal strength — which land as check metrics and chart on the check page.

Alongside that:

• gRPC checks now report a real DNS / connect / TLS / RPC phase breakdown instead of a connection_time_ms that measured almost nothing, attribute failures to the phase that failed, and can authenticate via request metadata (including encrypted secret metadata).
• Uptime report emails gained period-over-period trends, a response-time summary, average incident duration, and a worst-first check table with a per-day availability strip — with deliberate guards so a digest never shows a green zero, a comparison against no baseline, or a cheerful response-time trend measured on error responses.
• Two bugs fixed in passing, neither in the new code: a heartbeat config PATCH silently destroyed the check's ping token, and a report with no incidents in either period rendered <no value> instead of 0.

No new migration — the replay counter reuses the generic state_entries store, on a sliding 7-day window refreshed by every accepted beat.

Full details in CHANGELOG.md.

[fclairamb]

🤖 Created releases:

• v0.22.0

🌻