The one-week API revert
Datasette 1.0a37 undoes a change it shipped seven days earlier, after a cosmetic repackaging of one data response broke plugin tests across the ecosystem.
Datasette, Simon Willison's tool for turning any SQLite database into an explorable website and JSON API, put out its 37th alpha on the road to a stable 1.0. Most of the release is housekeeping: permission checks now run faster on large databases, a debug view explains why an action was allowed or denied, and a new option lets database-maintenance commands like VACUUM run on their own.
The revert is the story: an API meant to be stabilized by 1.0 churned and un-churned inside a single week.
The one wrinkle worth keeping: a week earlier, 1.0a37's predecessor had changed a small internal data feed, /-/plugins.json, to return its data in a new wrapper instead of as a plain list. That cosmetic tweak broke test suites across the plugin ecosystem, so this release simply puts it back. A seven-day round-trip on a response format is a reminder of why the 1.0 series exists in the first place: to freeze these contracts before real code depends on them.
For anyone not running a Datasette instance, there is nothing to act on here. The interest is narrow and mostly a small object lesson in API discipline, arriving in the same alpha series meant to stabilize the interface for good.
The lenses
The facts
Concepts
How this connects
Tap a node to open it