This release introduces support for finely grained per-database and per-table permissions, plus integration with the new [Datasette Events](https://docs.datasette.io/en/latest/events.html) mechanism added in Datasette 1.0a8.
- This release requires Datasette 1.0a9 or higher.
- Finely grained permissions: the `edit-schema` permission is still supported, but you can also control access to this plugin using the `create-table`, `drop-table` and `alter-table` permissions from Datasette core. These can be used to control access on a per-table and per-database level. [22](https://github.com/simonw/datasette-edit-schema/issues/22), [#55](https://github.com/simonw/datasette-edit-schema/issues/55)
- Now tracks `create-table`, `alter-table` and `drop-table` events using the new [Datasette Events](https://docs.datasette.io/en/latest/events.html) system introduced in Datasette 1.0a8. [#50](https://github.com/simonw/datasette-edit-schema/issues/50)
- Primary keys can now also be set as foreign keys, useful for many-to-many relationship tables. [52](https://github.com/simonw/datasette-edit-schema/issues/52)
- Now runs `VACUUM` using `db.execute_isolated_fn()` to avoid being caught out by any connection permission handlers. [47](https://github.com/simonw/datasette-edit-schema/issues/47)
- Tightened up display on mobile screens. [45](https://github.com/simonw/datasette-edit-schema/issues/45)
- Fixed a bug where the SQL schema for a table was not shown correctly on the edit schema page. [49](https://github.com/simonw/datasette-edit-schema/issues/49)
- Fixed a 500 error if a table only consists of primary keys. [51](https://github.com/simonw/datasette-edit-schema/issues/51)