Release Checkpoint And New Schema-Metadata Surface

Issue 77 Edition 2026-03-18 3 min read

Not accepted General

Sources: 1 • Confidence: Medium • Updated: 2026-04-13 03:50

Key takeaways

Datasette version 1.0a26 has been released.
Datasette includes built-in semantic column types that include url, email, and json.
Datasette supports assigning semantic column types to columns.
Datasette plugins can register additional semantic column types via a register_column_types() plugin hook.

Datasette includes built-in semantic column types that include url, email, and json.
Datasette plugins can register additional semantic column types via a register_column_types() plugin hook.

What specific behaviors change when a column is assigned a semantic type (UI rendering, API output, validation, search, export, etc.)?
How are semantic column types stored and surfaced (database metadata tables, Datasette config, per-table JSON, plugin-managed storage), and are they portable across instances?
Is the register_column_types() plugin hook documented as stable, and what is the expected compatibility contract for plugin authors across 1.0 alpha releases?
Are there additional built-in semantic types beyond url, email, and json, and is there a standard taxonomy or naming convention expected for new types?
Is there any clear operator, product, or investor decision-readthrough described (upgrade urgency, breaking changes, performance impacts, migration steps)?

Semantic column types and a plugin hook suggest a push toward a more extensible ecosystem, which could increase plugin activity and downstream integration demand if widely adopted.
Expanding schema metadata may change rendering and automation behaviors, potentially increasing operator attention to upgrades and compatibility if semantic types influence UI or APIs.

Documentation or release notes describing concrete behavior changes when semantic types are assigned, such as UI rendering or API output, indicating real product impact.
Evidence of third party plugin uptake using register_column_types and additional semantic types emerging, signaling ecosystem traction.
Clear statements on stability and compatibility guarantees for the plugin hook across 1.0 alpha releases, supporting sustained plugin investment.

Semantic types end up being largely cosmetic with minimal effect on UI, APIs, search, or export, limiting practical adoption and ecosystem pull through.
The plugin hook is unstable or changes frequently across alpha releases, discouraging plugin authors and reducing extensibility value.
No portable or standardized way to store and surface semantic types across instances, making configurations fragile and limiting multi environment use.