If you mostly follow AI tools from the outside, this is the kind of update you almost skip and then regret missing. The easy mistake is to read sqlite-utils 4.1 like a normal feature release, when the real lesson is about silent data damage, not convenience. [C001]
ZIP-code-like fields are exactly where smart imports can destroy data. A value can look numeric, get treated like an integer, and still be wrong the moment 01234 turns into 1234. Nothing crashes. The meaning just changed. [C002]
That is why the interesting part of 4.1 is not “better guessing.” On 2026-07-11, the release added one option to force a column type and another to turn type detection off. If automatic guessing were reliable enough on its own, those escape hatches would not be the headline.
A release is worth reading when it changes your next decision, not when it adds the most features. Here, the next decision is simple: if a field only looks numeric but is really a code or ID, store it as text before import.
Boundary: this is a docs-only read based on the sqlite-utils 4.1 changelog, CLI docs, and upgrading notes dated 2026-07-11, not a live runtime test.
If you know someone who imports CSVs and assumes “smart” means “safe,” share this with them.