2026-11-15 · ← News
Datasette 1.0a43 opens streaming to every exporter and fixes private query exposure
Datasette 1.0a43 moves CSV and TSV onto general streaming output renderers and gives plugins the same capability. The prerelease also fixes two security issues and changes several interfaces ahead of 1.0.
The image could not be loaded.
Simon Willison released Datasette 1.0a43. Its largest change is general streaming for output renderers, allowing CSV, TSV and plugin formats to send every row incrementally through the new Response.stream().
Plugin exporters now get the same streaming path as CSV and TSV
A renderer can accept an asynchronous row stream and process an entire table or view when ?_stream=1 is present. CSV and TSV now use this mechanism instead of a special path. The size limit setting consequently applies to every streaming format.
The release also introduces a new JSON shape for individual rows, expands the data available to renderers and tightens older plugin interfaces. The 1.0 milestone stood at 53% completion when the release appeared.
One interface removes special cases for operators and plugin authors
Unifying exports matters more than the cosmetic additions. A plugin author can stream a custom format without loading a whole table into memory, while Datasette can handle size limits and transfer failures consistently. If an export fails or reaches max_stream_mb, the connection is dropped so users do not receive a truncated file that looks complete.
Operators still have migration work. Render functions must return Response or None, some previously tolerated arguments are heading for removal, and the new JSON shape may affect clients built against the alpha API.
Security fixes matter more than smoother page transitions
The release fixes exposure of the title and SQL for a private stored query. The flaw did not permit execution of that query, but its metadata could reveal sensitive logic. A second fix covers database downloads when a database was registered under a route different from its name. That issue was also patched in the stable 0.65.6 line.
New CSS view transitions work in Safari and Chrome and make the multi page application feel smoother. For operators, the security updates and compatibility changes carry more weight than animation.
Upgrade results and plugin adoption will define the road to 1.0
The next signal will be how many plugins adopt Response.stream() and what breaks around the JSON format. Datasette 1.0a43 remains a prerelease, so operators should test it against their own templates, exporters and API clients before deployment.
Responses to the security advisories matter as well. Large features move the project toward 1.0, but small compatibility fixes will determine whether users arrive without a rough landing.
Lilith's verdict
Ahead of 1.0, Datasette is cleaning the pipes and locking the basement. Smoother pages are welcome, but operators should inspect the locks and exports first.