16de61357e
This field is marked as required in the spec. Before 7caa8f2739e38c43effd8a215e788cc1aece13c8, the fact that we had it marked as `skip_serializing_if` didn't really matter, because we were skipping the entire timeline object when `events` was empty. Now that we can serialize timelines with zero events, we always need to include the field.
Ruma – Your home in Matrix.
A set of Rust crates (libraries) for interacting with the Matrix chat network.
website • chat • documentation (unstable)
Getting started
If you want to build a Matrix client or bot, have a look at matrix-rust-sdk. It builds on Ruma and includes handling of state storage, end-to-end encryption and many other useful things.
For homeservers, bridges and harder-to-categorize software that works with
Matrix, you're at the right place. To get started, add ruma to your
dependencies:
# crates.io release
ruma = { version = "0.9.0", features = ["..."] }
# git dependency
ruma = { git = "https://github.com/ruma/ruma", branch = "main", features = ["..."] }
ruma re-exports all of the other crates, so you don't have to worry about
them as a user. Check out the documentation on docs.rs (or on
docs.ruma.dev if you use use the git dependency).
Status
Ruma 0.9.0 supports all events and REST endpoints of Matrix 1.8.
Various changes from in-progress or finished MSCs are also implemented, gated
behind the unstable-mscXXXX (where XXXX is the MSC number) Cargo features.
A few less formalized things are gated behind the unstable-unspecified Cargo
feature.
Contributing
See CONTRIBUTING.md.
Minimum Rust version
Ruma currently requires Rust 1.75. In general, we will never require beta or nightly for crates.io releases of our crates, and we will try to avoid releasing crates that depend on features that were only just stabilized.
ruma-signatures is an exception: It uses cryptographic libraries that often
use relatively new features and that we don't want to use outdated versions of.
It is guaranteed to work with whatever is the latest stable version though.