When the Database Stops Matching the Migrations
KittyLog's production schema drifted from its Alembic chain: twelve timestamp columns, one stamped migration, and a guard that fails closed.
Thoughts on AI-powered changelog generation, developer tools, and building in public.
KittyLog's production schema drifted from its Alembic chain: twelve timestamp columns, one stamped migration, and a guard that fails closed.
KittyLog's usage metering broke silently for most of a day while changelogs kept shipping. What a zero-token day taught us about alarming the meter.
A look at the OpenNext migration, the Pages compatibility proxy, and the deployment checks that keep the front door stable.
What an opt-in GitHub Release integration taught us about event seams, ownership markers, and leaving human notes alone.
A queue-health issue can make the boundary between finished content, scheduled posts, and human editorial judgment visible.
Changelogs are the most neglected piece of developer docs. Automation is not just convenient; it is the only way to keep them accurate.
For too many teams the changelog workflow is scrolling through 200 commits and writing something probably wrong. There is a better way.