How TypeGraph stopped assuming Drizzle, a pg pool, and an engine that locks like Postgres: Drizzle became an optional peer, backends now declare what they can't do, and engine profiles let you adapt a bundled backend to a different engine.
Since 0.55 an edge kind can allow different targets for each source kind, so an assignedTo edge can link employees to departments and students to courses while the other two combinations fail at compile time and at runtime.
A single TypeGraph write used to cost five or six sequential round trips, which adds up to about a quarter of a second from an edge worker to managed Postgres. 0.52 and 0.53 fold most writes into one request.
Five TypeGraph bugs from the last few months that returned plausible answers instead of throwing, how each was fixed, and the tools for checking whether your data was affected.
Put TypeGraph inside a Cloudflare Durable Object and every tenant gets a private graph database that exists the moment you name it and costs nothing while idle.
