v3.0.0-beta.2

Fixed

• Upgrading from v2 no longer stops with V2_WAL_PRESENT. v2 keeps recent
  changes in library.db-wal and leaves that file behind even after a
  clean stop, so the upgrade refused almost every v2. It now reads a
  recovered copy of the database and that file, so those changes come
  across. It also works after a v2 that crashed or was killed: what v2 had
  saved comes across, a half-written last change is dropped, as v2 itself
  would drop it. v2's own files are never changed, so going back to v2
  stays exact.

Trying it

Use droppedneedle/droppedneedle:beta. It always points at the newest
beta, so a docker compose pull gets you this one. :latest stays on v2.

Coming from v2, read
What changed in v3
and Before you upgrade
first.

Problems: open an issue on GitHub
or post in the Discord beta channel, and say which beta you're on
(Settings shows it).