sqlite-utils 4.0 Shipped via AI-Assisted Development Cycle

Simon Willison released sqlite-utils 4.0 on July 7, 2026, a major version that adds schema migrations, compound foreign keys, nested transaction support via db.atomic(), and an improved upsert implementation.[4][3] The release went through four release candidates rather than the planned two, because AI-assisted issue triage with Claude Fable 5 and GPT-5.5 kept surfacing additional problems and improvements.[1] Willison credits Fable 5 with writing 12 test scripts that identified 4 release blockers and 10 additional issues, and with drafting the upgrade guide and release notes; GPT-5.5 wrote 5 scripts and found nothing significant by comparison.[4] sqlite-migrate, a standalone beta library, was simultaneously retired as its own package and replaced with a one-line compatibility shim pointing to sqlite-utils 4.0.[5]

The release is as much a case study in AI-assisted open source development as it is a library update. Willison's detailed accounting of which model did what — and his explicit comparison of Fable 5 against GPT-5.5 in a real QA workload — gives practitioners one of the more concrete, documented examples of frontier models being used for pre-release code review rather than code generation.

sqlite-utils 4.0 began its final stretch as a straightforward release: Willison planned to ship a stable version after rc2. Instead, working through the open issue backlog using Claude Fable 5 and GPT-5.5 kept surfacing addressable problems, pushing the release to rc3 and then rc4.[1] The rc3 additions included support for introspecting and creating compound foreign keys — a feature that introduced a breaking change to the table.foreign_keys API significant enough to require landing in a major version.[1] The library also adopted SQLite's convention for case-insensitive column names, a change that touched many parts of the codebase.[1]

rc4, released the following day, was driven almost entirely by feedback from a detailed review Claude Fable 5 conducted against the release candidate.[2] The stable 4.0 followed the same day.[3] The headlining feature is a schema migration system: migrations are written as Python files and tracked via a _sqlite_migrations table, with no rollback support — a deliberate simplicity choice.[4] Other changes include a db.atomic() context manager that supports nested transactions using SQLite Savepoints (resolving long-standing confused transaction behavior), and an upsert rewrite using INSERT...ON CONFLICT...DO UPDATE SET with automatic primary key detection.[4]

Willison's post-release writeup provides an unusually granular account of the AI tooling involved. He ran Fable 5 against a release candidate with an open-ended goal; it wrote 12 test scripts, produced a report identifying 4 release blockers and 10 additional issues, and assembled a combined reproduction script.[4] GPT-5.5, given the same task, wrote 5 scripts and found nothing significant.[4] The upgrade guide and release notes were drafted entirely by Fable 5, Claude Opus 4.8, and GPT-5.5, then reviewed for accuracy by Willison.[4] His summary: the release is higher quality than it would have been without frontier model assistance, and Fable 5 shows 'really good taste in API design' and is 'relentlessly proactive if you give it a more open goal.'[4]

Alongside the main release, Willison retired sqlite-migrate — a standalone beta library for SQLite schema migrations — by publishing version 0.2 as a one-line compatibility shim that re-exports the Migrations class from sqlite-utils 4.0. Existing projects depending on sqlite-migrate continue to work without code changes.[5] He also shipped an unrelated github-code Web Component, built entirely via a GPT-5.5 prompting session, which fetches GitHub blob URLs and renders specified line ranges with line numbers.[6]