Datasette 1.0a10 is a focused alpha that changes some internal details about how Datasette handles transactions. The datasette.execute_write_fn() internal method now wraps the function in a database transaction unless you pass transaction=False.

Datasette 1.0a9 adds basic alter table support to the JSON API, tweaks how permissions works and introduces some new plugin debugging utilities.

Datasette 1.0a8 introduces several new plugin hooks, a JavaScript plugin system and moves plugin configuration from metadata.yaml to datasette.yaml. Read more about the release in the annotated release notes for 1.0a8.

Datasette Enrichments is a new feature for Datasette that supports enriching data by running custom code against every selected row in a table. Read Datasette Enrichments: a new plugin framework for augmenting your data for more details, plus a video demo of enrichments for geocoding addresses and processing text and images using GPT-4.

datasette-comments is a new plugin by Alex Garcia which adds collaborative commenting to Datasette. Alex built the plugin for Datasette Cloud, but it's also available as an open source package for people who are hosting their own Datasette instances. See Annotate and explore your data with datasette-comments on the Datasette Cloud blog for more details.

Datasette 1.0a4 has a fix for a security vulnerability in the Datasette 1.0 alpha series: the API explorer interface exposed the names of private databases and tables in public instances that were protected by a plugin such as datasette-auth-passwords, though not the actual content of those tables. See the security advisory for more details and workarounds for if you can't upgrade immediately. The latest edition of the Datasette Newsletter also talks about this issue.

datasette-write-ui: a Datasette plugin for editing, inserting, and deleting rows introduces a new plugin adding add/edit/delete functionality to Datasette, developed by Alex Garcia. Alex built this for Datasette Cloud, and this post is the first announcement made on the new Datasette Cloud blog - see also Welcome to Datasette Cloud.

Datasette 1.0a3 is an alpha release of Datasette that previews the new default JSON API design that’s coming in version 1.0 - the single most significant change planned for that 1.0 release.

New tutorial: Data analysis with SQLite and Python. This tutorial, originally presented at PyCon 2023, includes a 2h45m video and an extensive handout that should be useful with or without the video. Topics covered include Python's sqlite3 module, sqlite-utils, Datasette, Datasette Lite, advanced SQL patterns and more.

I built a ChatGPT plugin to answer questions about data hosted in Datasette describes a new experimental Datasette plugin to enable people to query data hosted in a Datasette interface via ChatGPT, asking human language questions that are automatically converted to SQL and used to generate a readable response.

Using Datasette in GitHub Codespaces is a new tutorial showing how Datasette can be run in GitHub's free Codespaces browser-based development environments, using the new datasette-codespaces plugin.

Examples of sites built using Datasette now includes screenshots of Datasette deployments that illustrate a variety of problems that can be addressed using Datasette and its plugins.

Semantic search answers: Q&A against documentation with GPT3 + OpenAI embeddings shows how Datasette can be used to implement semantic search and build a system for answering questions against an existing corpus of text, using two new plugins: datasette-openai and datasette-faiss, and a new tool: openai-to-sqlite.

Datasette 0.64 is out, and includes a strong warning against running SpatiaLite in production without disabling arbitrary SQL queries, plus a new --setting default_allow_sql off setting to make it easier to do that. See Datasette 0.64, with a warning about SpatiaLite for more about this release. A new tutorial, Building a location to time zone API with SpatiaLite, describes how to safely use SpatiaLite and Datasette to build and deploy an API for looking up time zones for a latitude/longitude location.

Datasette 1.0a2: Upserts and finely grained permissions describes the new upsert API and much improved permissions capabilities introduced in the latest Datasette 1.0a2 alpha release.

• Upgrade to asgi_cors>=1.0.1 to address a bug that could cause duplicate CORS headers. #13

• Now uses the newly released gpt-4-turbo model, which also handles image inputs. #8

• Added description to menu items for Datasette 1.0. #7

• Handle case where no enrichments plugins are installed. #43
• Added description to the menu items.

• This plugin now uses the general availability gpt-4-turbo model, which adds structured function support to GPT-4 Vision. #19
• If an error occurs during an extraction operation it is now displayed on the progress page. #10
• Table and database action menu items now have better copy. #20

• headers option for setting access-control-allow-headers. #5
• methods option for setting access-control-allow-methods.
• max_age option for setting access-control-max-age.
• Now tested against Datasette 1.0 as well as Datasette <1.0.

• JavaScript functions can now return an object of key/value pairs, and columns will be created for each of those returned values. #5

• Fixed documentation bug. s3-credentials.readthedocs.io should now show the most recent stable release documentation.

• New command: s3-credentials debug-bucket bucket-name. #86
• Fixed bug where calling s3-credentials create bucket-name --create-bucket --public did not make the contents of the bucket available to the public. #88
• s3-credentials list-bucket bucket-name --urls option. #89

• Fix for a bug where the row action menu did not work correctly for tables with primary keys starting with an underscore. #42

• Removed unnecessary print() debug statement.

• Now adds an "Enrich this row" row action menu item on Datasette 1.0a13 and higher. #41

• Switch from pkg_resources to importlib.metadata to fix a deprecation warning. Dropped support for Python 3.7. #6

• Temporary files created for the user to download are now deleted after the download finishes, and any stale ones are cleared out when Datasette first starts running. #5

• Database action menu now shows the size of the database in the menu item description. #3
• Confirm that signed URL token is from the same user based on their csrftoken cookie. #4