v0.80.1

- Sealed sender SenderCertificates can now use a `bytes`
  representation for the sender, and may avoid embedding their signing
  ServerCertificate in favor of referencing a "known" certificate
  baked into libsignal. See sealed_sender.proto and the
  `KNOWN_SERVER_CERTIFICATES` list in the source for more details.

v0.80.0

- backups: relax restriction that backups with backup_tier == free cannot have backupsSubscriberData

- Migrate crates to Rust 2024 edition.

- Desktop: add a distinct error type for incremental mac verification failures.

v0.79.1

- The first "Typed API" service interface for chat-server, UnauthUsernamesService, has been added to libsignal's app layer.

- The libsignal-net remote config option `chatRequestConnectionCheckTimeoutMillis` controls a new check: if a chat request hasn't been responded to in this amount of time, libsignal will check if the connection is using the preferred network interface, and close it early if not.

- Java: `CertificateValidator.validate(SenderCertificate, long)` is once again `open` for testing.

- backups: Validate quote body length

- MSRV has been increased to 1.85

v0.79.0

- Rust: libsignal-protocol's fingerprint-related operations have a dedicated error type now, FingerprintError, rather than reusing SignalProtocolError.

- backups: validate presence of `OutgoingMessageDetails.dateReceived`, remove deprecated BackupLocator/AttachmentLocator/LocalLocator

v0.78.3

- keytrans: Distinguish self-monitoring from monitoring for others

- Net: Shadow Chat websocket connections in staging with Noise Direct connections when enabled via remote config.

v0.78.2

- Finalize errors produced by SVR-B operations.

v0.78.1

- backups: Add support for call link epochs.

- Rust: libsignal_net_infra::ws2 has been merged into libsignal_net_infra::ws, with Connection and Config included directly and helper types available under ws::connection. The old ws::WebSocketConfig has been removed.

- Android: run TLS verification on a dedicated thread.

v0.78.0

SVR-B
-----

- Operations have been consistently renamed to `store` and `restore`.

- `restore` now returns an object containing both the
  BackupForwardSecrecyToken for decryption, and "secret data" to be
  used in the first `store` after restoration.

- `SvrB` now has a `createNewBackupChain` method, allowing you to
  locally persist the backup "secret data" *before* the first store to
  SVR-B for a fresh install.

- With the first two changes, the secret data argument to `restore` is
  now required. See doc comments for more details.

Other Changes
-------------

- Rust: `SessionRecord::has_usable_sender_chain` now takes an
  additional parameter to specify which criteria make a session
  "usable" beyond simply *having* a sender chain. The previous
  behavior can be requested by using
  `SessionUsabilityRequirements::NotStale`.

v0.77.1

- Add more logging for network connectivity issues

v0.77.0

- Java: Align cancellation behavior of our CompletableFuture with the one from OpenJDK:

    - The parameter to `cancel()` is ignored.
    - `completeExceptionally(someCancellationException)` is treated as a cancellation.
    - `get()` can now directly throw CancellationExceptions (as documented) instead of wrapping them in ExecutionException.

    Cancellations of libsignal operations continue to propagate bidirectionally when using CompletableFuture's transformation methods, unlike the version in OpenJDK.

    As a bonus, CompletableFuture now supports the `handle()` transformation.

- Exposed the new SVR-B API to TypeScript, Swift, and Kotlin.

- BackupForwardSecrecyTokens can now be used to derive MessageBackupKeys.

- Downgraded some networking-related error logs to warnings.