releases
3 rows where target_commitish = "0.63.x"
This data as json, CSV (advanced)
Suggested facets: created_at (date), published_at (date)
| id ▼ | html_url | node_id | tag_name | target_commitish | name | draft | author | prerelease | created_at | published_at | body | repo | reactions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 83624627 | https://github.com/simonw/datasette/releases/tag/0.63.2 | RE_kwDOBm6k_c4E_AKz | 0.63.2 | 0.63.x | 0.63.2 | 0 | simonw 9599 | 0 | 2022-11-19T00:53:05Z | 2022-11-19T00:58:27Z | - Fixed a bug in `datasette publish heroku` where deployments failed due to an older version of Python being requested. ([#1905](https://github.com/simonw/datasette/issues/1905)) - New `datasette publish heroku --generate-dir <dir>` option for generating a Heroku deployment directory without deploying it. | datasette 107914493 | |
| 86425242 | https://github.com/simonw/datasette/releases/tag/0.63.3 | RE_kwDOBm6k_c4FJr6a | 0.63.3 | 0.63.x | 0.63.3 | 0 | simonw 9599 | 0 | 2022-12-18T03:08:01Z | 2022-12-18T03:10:52Z | - Fixed a bug where `datasette --root`, when running in Docker, would only output the URL to sign in as root when the server shut down, not when it started up. ([#1958](https://github.com/simonw/datasette/issues/1958)) - You no longer need to ensure `await datasette.invoke_startup()` has been called in order for Datasette to start correctly serving requests - this is now handled automatically the first time the server receives a request. This fixes a bug experienced when Datasette is served directly by an ASGI application server such as Uvicorn or Gunicorn. It also fixes a bug with the [datasette-gunicorn](https://datasette.io/plugins/datasette-gunicorn) plugin. ([#1955](https://github.com/simonw/datasette/issues/1955)) | datasette 107914493 | |
| 88331580 | https://github.com/simonw/datasette/releases/tag/0.64 | RE_kwDOBm6k_c4FQ9U8 | 0.64 | 0.63.x | 0.64 | 0 | simonw 9599 | 0 | 2023-01-09T16:37:21Z | 2023-01-09T16:49:04Z | - Datasette now **strongly recommends against allowing arbitrary SQL queries if you are using SpatiaLite**. SpatiaLite includes SQL functions that could cause the Datasette server to crash. See [SpatiaLite](https://docs.datasette.io/en/stable/spatialite.html#spatialite) for more details. - New [default_allow_sql](https://docs.datasette.io/en/stable/settings.html#setting-default-allow-sql) setting, providing an easier way to disable all arbitrary SQL execution by end users: `datasette --setting default_allow_sql off`. See also [Controlling the ability to execute arbitrary SQL](https://docs.datasette.io/en/stable/authentication.html#authentication-permissions-execute-sql). ([#1409](https://github.com/simonw/datasette/issues/1409)) - [Building a location to time zone API with SpatiaLite](https://datasette.io/tutorials/spatialite) is a new Datasette tutorial showing how to safely use SpatiaLite to create a location to time zone API. - New documentation about [how to debug problems loading SQLite extensions](https://docs.datasette.io/en/stable/installation.html#installation-extensions). The error message shown when an extension cannot be loaded has also been improved. ([#1979](https://github.com/simonw/datasette/issues/1979)) - Fixed an accessibility issue: the `<select>` elements in the table filter form now show an outline when they are currently focused. ([#1771](https://github.com/simonw/datasette/issues/1771)) | datasette 107914493 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [releases] (
[html_url] TEXT,
[id] INTEGER PRIMARY KEY,
[node_id] TEXT,
[tag_name] TEXT,
[target_commitish] TEXT,
[name] TEXT,
[draft] INTEGER,
[author] INTEGER REFERENCES [users]([id]),
[prerelease] INTEGER,
[created_at] TEXT,
[published_at] TEXT,
[body] TEXT,
[repo] INTEGER REFERENCES [repos]([id])
, [reactions] TEXT);
CREATE INDEX [idx_releases_repo]
ON [releases] ([repo]);
CREATE INDEX [idx_releases_author]
ON [releases] ([author]);