What shipped in ZenginUI.

Every release of ZenginUI, newest first, with the reason it went out. Follow it by RSS.

ZenginUI releases

1. Oct 15, 2026

   @zenginui/adapter-css 0.6.0, @zenginui/adapter-shadcn 0.1.6, @zenginui/cli 0.10.0, @zenginui/engine 0.7.0, @zenginui/figma 0.3.1, @zenginui/hook 0.2.3, @zenginui/mcp 0.2.0, @zenginui/registry 0.5.3, @zenginui/rollup 0.1.6, create-zengin 0.1.12

   • chore(zen-errors-001): Error reporting for ZenginUI (#36): com (the site and the docs) now sends its errors to PostHog's error tracking, each tagged with the release (Vercel's commit sha) and the surface (site or docs). It does nothing until you set VITE_POSTHOG_KEY, and it sends errors only, nothing that identifies a reader. Readers also get pages they can recover from: a crash shows Reload and a way back instead of a blank page, an unknown address gets a branded 404 with links home and to the docs, and the template catalog gets a "Try again" wh…
   • chore(zen-measure-001): Measure ZenginUI with PostHog (#35): com now sends product analytics to the org's PostHog project. Both pages (home and /why/) send a pageview, and pressing Copy on the npm create zengin@latest command sends install_command_copied, the venture's main action. Other snippet copies send code_copied.
   • A Claude Design adapter, and the third field test that is not shadcn (#34): ts` contracts, cross-checked against the export's own adherence config. It is proven the way the shadcn adapter was, with a field test on three real exports (FakeOrders, PainSense, AstroSense) that are not shadcn-descended. Running it surfaced four engine bugs in how fixes are suggested; those are fixed here too, each with a regression test.
2. Oct 9, 2026

   @zenginui/adapter-css 0.5.1, @zenginui/adapter-shadcn 0.1.5, @zenginui/cli 0.9.0, @zenginui/engine 0.6.0, @zenginui/figma 0.3.0, @zenginui/hook 0.2.2, @zenginui/mcp 0.1.5, @zenginui/mock 0.1.0, @zenginui/registry 0.5.2, @zenginui/rollup 0.1.5, @zenginui/ui 0.2.4, create-zengin 0.1.11

   Maintenance release