v0.56.0

- PreKeyRecords (all three kinds) lazily validate their keys. This was
  not properly reflected in the Java and Swift APIs, which have now
  been updated to produce errors if the keys are invalid when loaded.
  This is a breaking change.

- Renames of the "reconnect" libsignal-net ChatService types.

- Several updates to the backup validator.

v0.55.1

Further updates to the backup validator

v0.55.0

- libsignal-net: auto-reconnect logic is removed for ChatService and corresponding API changes made to Node and Swift bridges
- Legacy SSv2 receive support removed

v0.54.2

- Java: Handle absurd numbers of recipients in multi-recipient messages

- Java: Exclude native libraries from the "sources" artifacts uploaded
  to Maven

- Java: Special-case the arch-specific load to handle JREs that use
  "x86_64" instead of "amd64"

- Node: Don't force binary encoding for incremental MAC streams

- Further updates to the backup validator, including omitting the
  backup timestamp and sorting reactions in the canonical string

- Update to boring v4.9.0

v0.54.1

- libsignal-server now includes builds for aarch64 Linux, with a
  minimum requirement of ARMv8.2

- The Net/Network class now exposes an "onNetworkChanged" event,
  which will clear certain caches and reset cooldowns

- Minor improvements to the backup validator

- Rolled back some dependencies in Cargo.lock to preserve our current
  MSRV

v0.54.0

- Node, Swift: changes in the libsignal-net API
- Android: include debug info in the AAR
- Internal improvements and housekeeping changes

v0.53.0

- Node: Split ChatService into AuthenticatedChatService and
  UnauthenticatedChatService. We plan to make a similar split for the
  other platforms in the future.

- Node: Upload Breakpad syms files for debug info instead of using
  per-platform formats

- Server: Added SealedSenderMultiRecipientMessage#serializedRecipientView,
  to save on repeated parsing

- iOS: ComparableBackup is now correctly implemented as
  simulator-only, fixing builds for device broken in v0.52.4

v0.52.4

- Android: include debug info in the AAR
- Backups: ComparableMessageBackup can be used to check message backups for equality
- Java: ChatServiceException extends IOException
- SVR3: implement migration support, improve resilience to connection failures

v0.52.3

- Node: The "install" action no longer tries to build the Rust library
  even if there are no available prebuilds. This should only have an
  effect if you were doing local development of libsignal.

  (This now actually works.)

v0.52.2

- Infrastructure for client testing APIs has been added (that is,
  APIs that exist for clients of libsignal to write tests).

  - Java/Android: There is a new libsignal_jni_testing.so library
    in both the JAR and AAR products. This can safely be filtered
    out of the final built app when code size is a concern.

  - Swift: The testing APIs are only available on simulator builds.

  - Node: The testing APIs are included in the regular build.

- SVR3: Restores can now fall back to previous environments.

- SVR3: Provide a migration API, for backing up to the latest
  environment and clearing from previous ones.

- ChatService: 4xx messages from proxies will no longer be considered
  authoritative.

- ChatService: Fixed a hang when the same instance was used for both
  auth and unauth connections.

- Node: libsignal will drop log events if they are not being drained
  from the Node event loop fast enough, rather than continue to
  saturate the event loop.

- Node: The "install" action no longer tries to build the Rust library
  even if there are no available prebuilds. This should only have an
  effect if you were doing local development of libsignal.

- Node: Debug info for the Rust library is saved as part of the build.

- Further updates to the backup validator