Release Maturity And Compatibility Alignment

Issue 82 Edition 2026-03-23 4 min read

General

Sources: 1 • Confidence: High • Updated: 2026-04-12 10:20

Key takeaways

datasette-files now configures columns using Datasette 1.0a26's column_types system.
The datasette-files plugin adds the ability to upload files directly into a Datasette instance.
datasette-files adds a file_actions plugin hook.
datasette-files generates thumbnails for uploaded image files and stores them in an internal datasette_files_thumbnails table.
datasette-files can import an uploaded CSV or TSV file into a table.

datasette-files now configures columns using Datasette 1.0a26's column_types system.
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 supports uploading multiple files at once through a UI that uses a documented JSON upload API.

datasette-files generates thumbnails for uploaded image files and stores them in an internal datasette_files_thumbnails table.

What are the minimum required Datasette versions (and any constraints) for datasette-files 0.1a2 to function correctly, given its use of column_types?
What authentication/authorization controls govern who can upload files and who can invoke the JSON upload API?
What limits and failure modes exist for uploads (file size limits, concurrency, storage backend behavior, resumability, error reporting)?
How does CSV/TSV import map schema (types, column naming, primary keys), and what validation or sanitization is applied during import?
What are the lifecycle and storage-management behaviors for generated thumbnails (regeneration, cleanup, deduplication, and storage growth characteristics)?

Datasette is evolving toward ingestion workflows, not just publishing, as plugins add direct uploads, JSON upload APIs, and CSV TSV import into tables.
Plugin ecosystem stability risk increases because datasette-files ties configuration to Datasette 1.0 alpha column_types, implying tighter coupling to core version changes.
Growing need for storage and lifecycle management inside Datasette as derived artifacts like image thumbnails are generated and persisted in internal tables.

Clear minimum Datasette version constraints documented for datasette-files 0.1a2 and continued updates tracking Datasette pre 1.0 changes without breaking users.
Published guidance or controls for authentication and authorization on uploads and the JSON upload API, indicating production hardening beyond alpha.
Documented limits, error modes, and lifecycle behaviors for uploads, CSV TSV import, and thumbnail storage, suggesting operational readiness and predictable footprint.

Frequent breaking changes driven by Datasette alpha internals, unclear compatibility, or inability to run on stable Datasette versions.
Uploads and JSON upload API lack clear access controls, creating security concerns that block adoption in real deployments.
Unbounded storage growth or unreliable behavior from thumbnail generation or CSV TSV import, with limited tooling for cleanup, validation, and monitoring.