Update Rust crate matrix-sdk to 0.8.0 #14
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/matrix-sdk-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.7.1
->0.8.0
Release Notes
matrix-org/matrix-rust-sdk (matrix-sdk)
v0.8.0
: matrix-sdk 0.8.0Compare Source
What's Changed
Bug Fixes
Add more invalid characters for room aliases.
Match the right status code in
Client::is_room_alias_available
.Fix a bug where room keys were considered to be downloaded before backups were
enabled. This bug only affects the
BackupDownloadStrategy::AfterDecryptionFailure
, where no attempt would bemade to download a room key, if a decryption failure with a given room key
would have been encountered before the backups were enabled.
Documentation
Client::observe_events
.Features
Add
create_room_alias
function.Client::cross_process_store_locks_holder_name
is used everywhere:StoreConfig::new()
now takes across_process_store_locks_holder_name
argument.StoreConfig
no longer implementsDefault
.BaseClient::new()
has been removed.BaseClient::clone_with_in_memory_state_store()
now takes across_process_store_locks_holder_name
argument.BaseClient
no longer implementsDefault
.EventCacheStoreLock::new()
no longer takes akey
argument.BuilderStoreConfig
no longer hascross_process_store_locks_holder_name
field forSqlite
andIndexedDb
.EncryptionSyncService
andNotification
are usingClient::cross_process_store_locks_holder_name
.Allow passing a custom
RequestConfig
to an upload request.Retry uploads if they've failed with transient errors.
Implement
EventHandlerContext
for tuples.Introduce a mechanism similar to
Client::add_event_handler
andClient::add_room_event_handler
but with a reactive programming pattern. AddClient::observe_events
andClient::observe_room_events
.When calling
observe_events
, one has to specify the type of event (in theexample,
SyncRoomMessageEvent
) and a context (in the example,(Room, Vec<Action>)
, respectively for the room and the push actions).Implement unwedging for media uploads.
Send state from state sync and not from timeline to widget (#4254)
Allow aborting media uploads.
Add
RoomPreviewInfo::num_active_members
.Use room directory search as another data source.
Check if the user is allowed to do a room mention before trying to send a call
notify event.
(#4271)
Add
Client::cross_process_store_locks_holder_name()
.Add a
PreviouslyVerified
variant toVerificationLevel
indicating that theidentity is unverified and previously it was verified.
New
UserIdentity::pin
method.New
ClientBuilder::with_decryption_trust_requirement
method.New
ClientBuilder::with_room_key_recipient_strategy
methodNew
Room.set_account_data
andRoom.set_account_data_raw
RoomAccountDatasetters, analogous to the GlobalAccountData
New
RequestConfig.max_concurrent_requests
which allows to limit the maximumnumber of concurrent requests the internal HTTP client issues (all others have
to wait until the number drops below that threshold again)
Implement proper redact handling in the widget driver. This allows the Rust
SDK widget driver to support widgets that rely on redacting.
Refactor
[breaking] Rename
DisplayName
toRoomDisplayName
.Improve
is_room_alias_format_valid
so it's more strict.Remove duplicated fields in media event contents.
Use
SendHandle
for media uploads too.Move
event_cache_store/
toevent_cache/store/
inmatrix-sdk-base
.Move
linked_chunk
frommatrix-sdk
tomatrix-sdk-common
.Move
Event
andGap
intomatrix_sdk_base::event_cache
.Move
formatted_caption_from
to the SDK, rename it.Tidy up and start commenting the widget code.
Get rid of
ProcessingContext
and inline it in its callers.Get rid of unused
limits
parameter when constructing aWidgetMachine
.Use a specialized mutex for locking access to the state store and
being_sent
.Renamed
VerificationLevel::PreviouslyVerified
toVerificationLevel::VerificationViolation
.[breaking] Replace the
Notification
type from Ruma inSyncResponse
andClient::register_notification_handler
by a custom one.[breaking] The ambiguity maps in
SyncResponse
are moved toJoinedRoom
and
LeftRoom
.[breaking]
Room::can_user_redact
andMember::can_redact
are splitbetween
*_redact_own
and*_redact_other
.[breaking]
AmbiguityCache
contains the room member's user ID.[breaking] Replace
impl MediaEventContent
with&impl MediaEventContent
inMedia::get_file
/Media::remove_file
/Media::get_thumbnail
/Media::remove_thumbnail
[breaking] A custom sliding sync proxy set with
ClientBuilder::sliding_sync_proxy
now takes precedence over a discoveredproxy.
[breaking]
Client::get_profile
was moved toAccount
and renamed toAccount::fetch_user_profile_of
.Account::get_profile
was renamed toAccount::fetch_user_profile
.[breaking] The
HttpError::UnableToCloneRequest
error variant has beenremoved because it was never used or generated by the SDK.
[breaking] The
Error::InconsistentState
error variant has been removedbecause it was never used or generated by the SDK.
[breaking] The widget capabilities in the FFI now need two additional
flags:
update_delayed_event
,send_delayed_event
.[breaking]
Room::event
now takes an optionalRequestConfig
to allowfor tweaking the network behavior.
[breaking] The
instant
module was removed, use theruma::time
moduleinstead.
[breaking] Add
ClientBuilder::sqlite_store_with_cache_path
to build aclient that stores caches in a different directory to state/crypto.
[breaking] The
body
parameter inget_media_file
has been replaced witha
filename
parameter now that Ruma has afilename()
method.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: Cargo.lock
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.