2.14: streaming responses, and a breaking change
Responses can now stream. The v1 batch endpoint is removed, six months after deprecation. Upgrade notes inside...
Digest 2.14 is out. One new capability, one removal, four fixes.
Streaming
Every endpoint that returns a list can now stream it. Pass Accept: application/x-ndjson and rows arrive as they are produced rather than after the last one. For a 200,000-row export this moves time-to-first-byte from forty seconds to under one.
curl -H "Accept: application/x-ndjson" \
https://api.digest.example/v2/events?since=2026-08-01Breaking: v1 batch endpoint removed
POST /v1/batch was deprecated in 2.8 and returned a warning header since 2.10. It is gone in 2.14. Requests to it now return 410 with a link to the v2 equivalent. If you are still on it, the migration is one path change and one field rename; the guide is linked from the 410 body.
Fixed
- Cursor pagination skipped a row when two rows shared a timestamp at a page boundary (#4471).
- The CLI printed the wrong exit code on a partial diff (#4490).
- Webhook retries could fire twice after a restart (#4502).
- Rate-limit headers were missing on 304 responses (#4515).
Upgrade
digest upgrade, or pull the 2.14 image. Migrations run forward automatically and are reversible for thirty days.
Release notes by email
Every release and every incident report, the day it is published. Nothing else.
Digest Engineering
The team that builds Digest. Release notes are signed by the team; incident reports by whoever was on call.
All Posts