Datasette 1.0a31 alpha release: bug fixes & plugin updates
Simon Willison's alpha update delivers bug fixes, dependency bumps, and small plugin and UI tweaks for Datasette users.
TL;DR
- 01Simon Willison's alpha update delivers bug fixes, dependency bumps, and small plugin and UI tweaks for Datasette users.
- 02Simon Willison released Datasette 1.0a31 on May 29, 2026.
- 03Datasette is a data publishing and exploration tool built around SQLite.
Simon Willison released Datasette 1.0a31 on May 29, 2026. The update is an alpha build in the 1.0 series and is positioned as an incremental maintenance release that addresses bugs, updates dependencies, and makes modest improvements to plugin compatibility and the web interface.
Datasette is a data publishing and exploration tool built around SQLite. This release continues the project's pattern of frequent alpha and patch updates, aimed at developers and organizations that host public data or embed queryable datasets in applications. The 1.0a31 tag signals changes that are intended for testing and adoption by early users rather than production-only deployments.
What changed in 1.0a31
The release notes for 1.0a31 list a set of small, focused changes covering stability and ecosystem upkeep. The most notable categories of change are:
- Bug fixes that resolve recent regressions and edge cases in query rendering and CSV import paths.
- Dependency updates to address security or compatibility issues in third party libraries used by Datasette.
- Minor user interface tweaks that improve table rendering and navigation for datasets with large schemas.
- Adjustments to the plugin API to clarify extension points and to maintain compatibility with a range of third party plugins.
- Documentation updates and clarifications for common developer workflows.
The maintainer emphasizes that this is not a feature-heavy update. Instead, the changes are targeted at improving reliability and developer experience. Users who rely on community plugins should check plugin compatibility notes before upgrading, since alpha series releases may introduce subtle API changes.
Upgrading and verification
Developers who want to try 1.0a31 can install the specific alpha release through Python package tooling. Typical installation commands reference the alpha tag explicitly to avoid unintentionally moving from a stable release to an alpha build. It is recommended to test the upgrade in a staging environment and to review the project changelog for any migration notes.
Operators of public data endpoints should pay attention to dependency updates included in this release. Dependency bumps can resolve vulnerabilities but may also require retesting integration points such as authentication middleware and reverse proxy configurations. Plugin authors should run their test suites against the new alpha to surface any compatibility gaps.
The release continues a practice of small, iterative updates that keep the core codebase current while minimizing disruptive changes. Community contributors often follow alpha releases closely to validate fixes and help harden the code before broader rollouts.
Why it matters
Datasette 1.0a31 signals ongoing maintenance and active stewardship of the project, which matters for teams that publish data and depend on a stable queryable interface. The alpha release model lets developers test fixes and dependency updates early, reducing the risk of latent bugs in later stable releases. Organizations that rely on Datasette should track alpha changelogs and validate plugins before applying updates in production.
Written by The Brieftide · Source: Simon Willison
The Brieftide Daily · 06:00
Briefs like this one, in your inbox every morning.
Continue reading
More in Benchmarks & EvalsSWE-Explore benchmark: AI coding agents find files but miss lines
SWE-Explore shows Claude Code, Codex and peers usually locate the correct source file but fail to return the exact lines needed for fixes.
olmo-eval: AllenAI launches evaluation workbench for model
Open-source olmo-eval bundles dataset connectors, metric runners and reproducible evaluation for iterative model testing.
Claude Fable 5 benchmark: SWE-bench 95% but costly, filtered
Anthropic's Mythos Claude Fable 5 scores 95% on SWE-bench Verified, tops public tests but adds heavy safety filters and higher cost.
Anthropic releases Claude Fable 5 and Mythos 5 with coding gains
Anthropic says the new Claude Fable 5 and Mythos 5 outperform the Opus generation on coding and scientific benchmarks.