Release 0.63a1

Refs #1646, #1819, #1825, #1829, #1831, #1832, #1834, #1844, #1848

datasette/version.py

@@ -1,2 +1,2 @@
-__version__ = "0.63a0"
+__version__ = "0.63a1"
 __version_info__ = tuple(__version__.split("."))

docs/changelog.rst

@@ -4,6 +4,20 @@
 Changelog
 =========
 
+.. _v0_63a1:
+
+0.63a1 (2022-10-23)
+-------------------
+
+- SQL query is now re-displayed when terminated with a time limit error. (:issue:`1819`)
+- New documentation on :ref:`deploying_openrc` - thanks, Adam Simpson. (`#1825 <https://github.com/simonw/datasette/pull/1825>`__)
+- The :ref:`inspect data <performance_inspect>` mechanism is now used to speed up server startup - thanks, Forest Gregg. (:issue:`1834`)
+- In :ref:`config_dir` databases with filenames ending in ``.sqlite`` or ``.sqlite3`` are now automatically added to the Datasette instance. (:issue:`1646`)
+- Breadcrumb navigation display now respects the current user's permissions. (:issue:`1831`)
+- Screenshots in the documentation are now maintained using `shot-scraper <https://shot-scraper.datasette.io/>`__, as described in `Automating screenshots for the Datasette documentation using shot-scraper <https://simonwillison.net/2022/Oct/14/automating-screenshots/>`__. (:issue:`1844`)
+- The :ref:`datasette.check_visibility() <datasette_check_visibility>` method now accepts an optional ``permissions=`` list, allowing it to take multiple permissions into account at once when deciding if something should be shown as public or private. This has been used to correctly display padlock icons in more places in the Datasette interface. (:issue:`1829`)
+
+
 .. _v0_63a0:
 
 0.63a0 (2022-09-26)
@@ -91,7 +105,7 @@ Datasette also now requires Python 3.7 or higher.
 - Python 3.6 is no longer supported. (:issue:`1577`)
 - Tests now run against Python 3.11-dev. (:issue:`1621`)
 - New :ref:`datasette.ensure_permissions(actor, permissions) <datasette_ensure_permissions>` internal method for checking multiple permissions at once. (:issue:`1675`)
-- New :ref:`datasette.check_visibility(actor, action, resource=None) <datasette_check_visibilty>` internal method for checking if a user can see a resource that would otherwise be invisible to unauthenticated users. (:issue:`1678`)
+- New :ref:`datasette.check_visibility(actor, action, resource=None) <datasette_check_visibility>` internal method for checking if a user can see a resource that would otherwise be invisible to unauthenticated users. (:issue:`1678`)
 - Table and row HTML pages now include a ``<link rel="alternate" type="application/json+datasette" href="...">`` element and return a ``Link: URL; rel="alternate"; type="application/json+datasette"`` HTTP header pointing to the JSON version of those pages. (:issue:`1533`)
 - ``Access-Control-Expose-Headers: Link`` is now added to the CORS headers, allowing remote JavaScript to access that header.
 - Canned queries are now shown at the top of the database page, directly below the SQL editor. Previously they were shown at the bottom, below the list of tables. (:issue:`1612`)

docs/internals.rst

@@ -364,7 +364,7 @@ This is useful when you need to check multiple permissions at once. For example,
         ],
     )
 
-.. _datasette_check_visibilty:
+.. _datasette_check_visibility:
 
 await .check_visibility(actor, action=None, resource=None, permissions=None)
 ----------------------------------------------------------------------------

docs/performance.rst

@@ -24,6 +24,8 @@ To open a file in immutable mode pass it to the datasette command using the ``-i
 
 When you open a file in immutable mode like this Datasette will also calculate and cache the row counts for each table in that database when it first starts up, further improving performance.
 
+.. _performance_inspect:
+
 Using "datasette inspect"
 -------------------------