# datasette 1.0a43

> Source: <https://simonwillison.net/2026/Nov/15/datasette/>
> Published: 2026-11-15 23:20:27+00:00

**Release:** [datasette 1.0a43](https://github.com/simonw/datasette/releases/tag/1.0a43)

I've been leaning hard into Claude Fable 5.2 to help knock things off the [1.0 milestone](https://github.com/simonw/datasette/milestone/37), which is now 53% complete.

The biggest 1.0 item in this release is [streaming support for output renderers](https://docs.datasette.io/en/latest/plugin_hooks.html#plugin-register-output-renderer-streaming) - the built-in TSV and CSV export mechanisms now use this as well, and plugins can register themselves as capable of streaming every row in a table in one go via the new [Response.stream()](https://docs.datasette.io/en/latest/internals.html#internals-response-stream) method.

There are a couple of security fixes, one of which I deemed [deserving of a GitHub advisory](https://github.com/simonw/datasette/security/advisories/GHSA-mw6v-83vp-7c4c): private stored queries could be exposed, granting access to the title and SQL of the query (but not allowing that query to be executed).

There are dozens of smaller improvements. The row page JSON representation [finally has a design suitable for 1.0](https://docs.datasette.io/en/latest/json_api.html#json-api-row). A new `<datasette-copy-button>` Web Component provides copy-schema in various places. JSON in columns on the row page can be pretty-printed. There's a new [DatasetteModal.confirm()](https://docs.datasette.io/en/latest/javascript_plugins.html#javascript-plugins-modal-confirm) JavaScript utility method. Plus dozens of bug fixes, including contributions by [Zihan Dai](https://github.com/PDGGK), [Peter Olkhovets](https://github.com/peterolkhov), [Ilya Khalafi](https://github.com/IlyaKhalafi), and [Ankita Advitot](https://github.com/AnkitaAdvitot).

The feature I'm most excited about is a pretty tiny one: I've added CSS multi-page view transitions to Datasette! [Here's the commit](https://github.com/simonw/datasette/commit/7da8a85ea77786edef975a4066bbadfab0966a0c) - key CSS is as follows:

```
/* Enable cross-document view transitions,
   for anyone without prefers-reduced-motion */
@media (prefers-reduced-motion: no-preference) {
    @view-transition {
        navigation: auto;
    }
}
/* .facet-results should morph from old position to new */
html:active-view-transition .content > .facet-results {
    view-transition-name: facet-results;
}
/* So should a .table-wrapper, provided it contains .rows-and-columns */
html:active-view-transition .table-wrapper:has(> table.rows-and-columns) {
    view-transition-name: rows-table;
}
```

With that in place, navigations within Datasette - still staunchly a multi-page application - feel more like an SPA. This works on Safari and Chrome at the moment and I believe supports for Firefox is due to land in [Firefox 162](https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/162#changes_for_web_developers) on December 8th 2026 (seeing as they are no longer feature-flagged in Firefox Nightly.)

Tags: [security](https://simonwillison.net/tags/security), [datasette](https://simonwillison.net/tags/datasette), [css](https://simonwillison.net/tags/css), [browsers](https://simonwillison.net/tags/browsers), [annotated-release-notes](https://simonwillison.net/tags/annotated-release-notes), [firefox](https://simonwillison.net/tags/firefox), [javascript](https://simonwillison.net/tags/javascript), [safari](https://simonwillison.net/tags/safari), [chrome](https://simonwillison.net/tags/chrome)
