EventSourcingDB 1.3.0 is Available

EventSourcingDB 1.3.0 has been released, delivering faster writes, EventQL queries, and reads, time-bounded requests, and more than sixty fixes, alongside a new v2 API that runs on the same data as v1 and reports every accepted request's outcome in the response body with individually coded, documented errors. The v2 API adds explicit end-of-stream markers, heartbeats to keep proxies from closing waiting streams, and recursive preconditions (isSubjectPristine, isSubjectPopulated, isSubjectOnEventId) that can span a subject and all subjects beneath it. All eight client SDKs support both APIs and default to v2 where available, so most users need only update their SDK, provided any fronting proxy passes the QUERY HTTP method; direct HTTP API callers must follow the route-by-route migration guide. The v1 API remains supported until January 31, 2027, giving users time to migrate before a later release removes it. Export and import now use one plain CloudEvent per line with IDs and timestamps preserved, letting users strip personal data from an exported history and reimport it without computing hashes manually, while incremental backups capture only events written since the prior backup and restores now write events in batches for greater speed. Documentation has moved to eventfoundation.io, with old links redirecting there.