Repository navigation
Tags
Tags
v0.102.2 - SVR: Update production SVRB/SVR2 to use 2026Q3. - Backups: Validate the new sharedName field on Contact and the new aci, nickname, and note fields on ContactAttachment. - Backups: Validate the new sharedName option in LearnedProfileChatUpdate.previousName.
v0.102.0
- All libsignal-net-chat APIs that have both WebSocket and gRPC implementations will default to gRPC. This was already the case in practice for all three Signal clients due to remote configs *except* for `UnauthBackupsService.getUploadForm` and `getMediaUploadForm` (controlled by `grpc.BackupsAnonymousGetUploadForm`). This does not affect APIs that only have one implementation (a few older ones that are WebSocket-only still, and all the new ones that are gRPC-only).
- New typed APIs:
- `AuthAccountsService.deleteAccount()`
- `checkSVRCredentials()`
- `getCurrencyConversions()`
- `AuthKeysService.getPreKeyCount()`
- `createLoginReceiptCredential()`
- `AuthDevicesService.setCapabilities()`
- `AuthStickersService.getStickerUploadForms()`
- MFA key management on `AuthAccountsService`: `generateTotpKey`, `confirmTotpKey`,
`listMfaKeys`, `setMfaKeyMetadata`, and `removeMfaKey`
- MSRV bumped to 1.93.1
- registration: Add support for registration without E.164
- libsignal builds off stable Rust by default
v0.101.1 - Typescript targets ES2025 - backups: Add support for new notification settings - gRPC-level errors are treated as transport errors if there is no more specific classification. (Previously they were "unexpected, likely-indicates-a-bug" errors.) - Back to a nightly toolchain to avoid miscompile in Rust 1.98.0
v0.101.0
- zkgroup: Update the implementation of GenericServerSecretParams and
GenericServerPublicParams.
- These types no longer implement `serde::Deserialize`. If you were
using zkgroup's bincode-based serialization, you should switch to
`TryFrom<&[u8]>` instead.
- The call link credentials, CallLinkAuthCredential and
CreateCallLinkCredential, track which version of
GenericServerSecretParams they were issued from. A temporary
helper method `verify_against_appropriate_params` has been added
to both of their presentation types to allow a verifying server to
pass both old and new params and have them chosen based on the
credential's version indicator.
- The other credentials issued from GenericServerSecretParams,
BackupAuthCredential and AvatarUploadCredential, were not directly
affected by this change, and support both old and new
versions.
- ServerSecretParams and ServerPublicParams continue to use the old
key behavior for compatibility.
- If you were using zkcredential directly, consider regenerating
your keys; if you need a migration period, you can use
`zkcredential::credentials::LegacyMode` to continue with the old
behavior.
- Update boring-rs dependency to v5.2.0 (includes a BoringSSL update
as well).
- Typed APIs:
- `submitCallQualitySurvey()`
- `AuthUsernamesService.confirmUsername()`
v0.99.3 - zkgroup: AuthCredentialWithPni can now be issued *without* a PNI; instead, a structurally valid "false PNI" will be derived from the ACI and a server-provided salt, which the encrypted presentation will not distinguish from a user with a real PNI. - SVR: Enforce that entire replica group connects to nodes with high enough TCB levels.
PreviousNext