recent_releases (view)
1 row where body_markdown = "The key new feature in this release is the **column actions** menu on the table page ([#891](https://github.com/simonw/datasette/issues/891)). This can be used to sort a column in ascending or descending order, facet data by that column or filter the table to just rows that have a value for that column. Plugin authors can use the new [datasette.client](https://docs.datasette.io/en/stable/internals.html#internals-datasette-client) object to make internal HTTP requests from their plugins, allowing them to make use of Datasette's JSON API. ([#943](https://github.com/simonw/datasette/issues/943)) New [Deploying Datasette](https://docs.datasette.io/en/stable/deploying.html#deploying) documentation with guides for deploying Datasette on a Linux server [using systemd](https://docs.datasette.io/en/stable/deploying.html#deploying-systemd) or to hosting providers [that support buildpacks](https://docs.datasette.io/en/stable/deploying.html#deploying-buildpacks). ([#514](https://github.com/simonw/datasette/issues/514), [#997](https://github.com/simonw/datasette/issues/997)) Other improvements in this release: - [Publishing to Google Cloud Run](https://docs.datasette.io/en/stable/publish.html#publish-cloud-run) documentation now covers Google Cloud SDK options. Thanks, Geoffrey Hing. ([#995](https://github.com/simonw/datasette/pull/995)) - New `datasette -o` option which opens your browser as soon as Datasette starts up. ([#970](https://github.com/simonw/datasette/issues/970)) - Datasette now sets `sqlite3.enable_callback_tracebacks(True)` so that errors in custom SQL functions will display tracebacks. ([#891](https://github.com/simonw/datasette/issues/891)) - Fixed two rendering bugs with column headers in portrait mobile view. ([#978](https://github.com/simonw/datasette/issues/978), [#980](https://github.com/simonw/datasette/issues/980)) - New `db.table_column_details(table)` introspection method for retrieving full details of the columns in a specific table, see [Database introspection](https://docs.datasette.io/en/stable/internals.html#internals-database-introspection). - Fixed a routing bug with custom page wildcard templates. ([#996](https://github.com/simonw/datasette/issues/996)) - `datasette publish heroku` now deploys using Python 3.8.6. - New `datasette publish heroku --tar=` option. ([#969](https://github.com/simonw/datasette/issues/969)) - `OPTIONS` requests against HTML pages no longer return a 500 error. ([#1001](https://github.com/simonw/datasette/issues/1001)) - Datasette now supports Python 3.9." and topics contains "datasette-io"
This data as json, CSV (advanced)
Suggested facets: date (date), published_at (date), topics (array)
rowid | repo | release | date | body_markdown | published_at | topics |
---|---|---|---|---|---|---|
107914493 | https://github.com/simonw/datasette | https://github.com/simonw/datasette/releases/tag/0.50 | 2020-10-09 | The key new feature in this release is the column actions menu on the table page (#891). This can be used to sort a column in ascending or descending order, facet data by that column or filter the table to just rows that have a value for that column. Plugin authors can use the new datasette.client object to make internal HTTP requests from their plugins, allowing them to make use of Datasette's JSON API. (#943) New Deploying Datasette documentation with guides for deploying Datasette on a Linux server using systemd or to hosting providers that support buildpacks. (#514, #997) Other improvements in this release:
|
2020-10-09T17:58:27Z | [ "asgi", "automatic-api", "csv", "datasets", "datasette", "datasette-io", "docker", "json", "python", "sql", "sqlite" ] |
Advanced export
JSON shape: default, array, newline-delimited
CREATE VIEW recent_releases AS select repos.rowid as rowid, repos.html_url as repo, releases.html_url as release, substr(releases.published_at, 0, 11) as date, releases.body as body_markdown, releases.published_at, coalesce(repos.topics, '[]') as topics from releases join repos on repos.id = releases.repo order by releases.published_at desc;