sqlite-utils 4.1 rebuilds tables to fake a STRICT ALTER, most PRs by Codex
Every URL the pipeline pulled into ranking for this issue — primary sources plus the supporting and contradicting findings each Researcher returned. Inline citations in the issue point back here.
Sources
sqlite-utils 4.1 simonwillison.net
Release: sqlite-utils 4.1 The first dot-release since 4.0 a few days ago , introducing a number of minor new features. sqlite-utils insert and sqlite-utils upsert now accept a —code option for providing a block of Python code (or a path to a .py file) that defines a rows() function or rows iterable of rows to insert, as an alternative to importing from a file. ( #684 ) sqlite-utils already had features that allow you to pass blocks of Python code as CLI arguments, for example this one for the…
References
SQLite.org — STRICT Tables documentation sqlite.org
STRICT tables only support five types—INT/INTEGER, REAL, TEXT, BLOB, and ANY—and there is no ALTER TABLE syntax to convert an existing non-strict table into a strict one.
dev.to — HelperX: Migrating a SQLite Schema in Production Without Locking Writers dev.to
The copy-and-swap pattern used to add STRICT to an existing table requires an exclusive write lock; on multi-gigabyte tables the reconstruction can stall writers for minutes unless staged with additive, backward-compatible steps.
simonwillison.net — sqlite-utils 4.0rc1 annotated notes simonwillison.net
This is the first major version bump in over five years, ending a streak of 124 backwards-compatible releases; much of the sweep to identify release-blockers was delegated to Claude Fable and GPT-5.5 agents.
LeadDev — ‘AI-generated abandonware is hollowing out open source’ leaddev.com
Maintainers report being overwhelmed by ‘AI slop’—low-quality automated pull requests that ignore project norms—and worry that agent-shipped features are easy to publish but difficult to sustain.
DevOps.com — ‘ChatGPT-5 coding gains come at a higher cost’ (Sonar research) devops.com
GPT-5 generates more than twice the lines of code per task compared to GPT-4o, and high-reasoning modes increased subtle concurrency/threading vulnerabilities from 20% to 38% in evaluations.
Vellum.ai — GPT-5.6 benchmarks explained vellum.ai
The Sol/Terra/Luna tiers combined with Light/Medium/High/xhigh reasoning levels yield 72 possible configurations; benchmarks show Luna at ‘Extra High’ can outperform Sol at ‘Light’ effort on some tasks at a fraction of the cost.
