Release And Version Increment

Issue 91 Edition 2026-04-01 3 min read

Not accepted General

Sources: 1 • Confidence: Medium • Updated: 2026-04-12 09:58

Key takeaways

datasette-llm version 0.1a6 has been released.
In datasette-llm 0.1a6, setting a model ID as the default model automatically adds it to the allowed models list.
In datasette-llm 0.1a6, the documentation for Python API usage has been improved.

In datasette-llm 0.1a6, setting a model ID as the default model automatically adds it to the allowed models list.

In datasette-llm 0.1a6, the documentation for Python API usage has been improved.

What specific changes (breaking or non-breaking) are included in datasette-llm 0.1a6 beyond the two mentioned items?
How does the default-model-implies-allowed-model behavior interact with existing configurations that intentionally separated defaults from allowlists?
What concrete improvements were made to the Python API documentation (new examples, clarified signatures, new workflows, or corrected inaccuracies)?
Is there any direct decision read-through (operator, product, or investor) implied by these deltas?

Incremental maturity signal: continued maintenance and responsiveness may sustain integrator confidence and reduce perceived platform risk.
Lower integration friction: default model automatically being allowed may reduce configuration errors and support burden for operators deploying the plugin.
Documentation improvements may increase Python API adoption by making integrations easier, potentially broadening the user base among developers.

Release notes or changelog show additional nontrivial fixes or features beyond the two highlighted configuration and documentation items.
User feedback or issue tracker activity indicates fewer misconfiguration reports related to default model versus allowlist after the release.
Documentation changes include concrete examples or clarified workflows, followed by increased usage or fewer questions about the Python API.

The new default implies allowed behavior causes unexpected access exposure or breaks configurations that intentionally separated defaults from allowlists.
Post release reports show new bugs or regressions, prompting pinning to older versions or rapid follow-on hotfixes.
Documentation updates are minor edits with no observable reduction in integration confusion or support requests.