Release Maturity And Risk Envelope

Issue 82 Edition 2026-03-23 4 min read

General

Sources: 1 • Confidence: High • Updated: 2026-03-25 17:55

Key takeaways

datasette-files 0.1a2 is an alpha release of the datasette-files plugin.
The datasette-files plugin adds the ability to upload files directly into a Datasette instance.
datasette-files configures columns using Datasette 1.0a26's column_types system.
datasette-files adds a file_actions plugin hook and can import an uploaded CSV or TSV file into a table.
datasette-files supports uploading multiple files at once via a UI that uses a documented JSON upload API.

The datasette-files plugin adds the ability to upload files directly into a Datasette instance.

datasette-files configures columns using Datasette 1.0a26's column_types system.

datasette-files adds a file_actions plugin hook and can import an uploaded CSV or TSV file into a table.

datasette-files supports uploading multiple files at once via a UI that uses a documented JSON upload API.

What minimum Datasette version is required for datasette-files 0.1a2 to function correctly, and what breaks on older versions?
What authentication/authorization controls govern who can upload files and trigger CSV/TSV imports?
What file size limits, storage backends, and retention behaviors apply to uploaded files and generated thumbnails?
What is the schema and lifecycle policy for internal tables such as datasette_files_thumbnails (migrations, cleanup, backup/restore expectations)?
How does CSV/TSV import handle typing, column inference, conflicts, and error reporting during import?

Alpha file upload and CSV or TSV import suggests Datasette usage could expand from read only publishing into ingestion workflows, potentially increasing plugin adoption if stability and access controls are adequate.
Dependency on Datasette 1.0a26 column_types implies alignment with newer core releases; could accelerate upgrades among users who want file upload and typed columns.
Documented JSON upload API and multi file UI hint at integration use cases beyond the browser; could pull in automation oriented users if auth, limits, and error handling are robust.

Clear documentation of minimum Datasette version and defined behavior on older versions, plus explicit stability commitments beyond alpha.
Explicit authentication and authorization model for uploads and imports, including who can trigger table creation and file actions.
Published limits and operational details such as file size, storage backend, retention, thumbnail table lifecycle, and CSV or TSV typing, conflict handling, and error reporting.

Inability to clearly specify required Datasette version or frequent breakage across core versions due to column_types or other dependencies.
Lack of adequate access controls for uploads and imports, or unclear security model for the new inbound workflow surface.
Operational gaps such as undefined storage and retention, unmanaged internal tables, or unreliable CSV or TSV imports with poor error visibility.