Add MSRV exception for ruma-client

This commit is contained in:
Jonas Platte 2020-12-30 19:20:58 +01:00
parent 91dd6383c5
commit 2b91b07c7b
No known key found for this signature in database
GPG Key ID: CC154DE0E30B7C67
2 changed files with 6 additions and 20 deletions

View File

@ -58,27 +58,10 @@ tasks:
popd
# Test non-default configurations of ruma-client
pushd ruma-client
cargo check --no-default-features --quiet
client_1_exit=$?
cargo check --no-default-features --features http1,http2,tls-rustls-native-roots --quiet
client_2_exit=$?
cargo check --no-default-features --features http1,http2,tls-rustls-webpki-roots --quiet
client_3_exit=$?
popd
exit $(( \
$ruma_build_exit \
|| $client_build_exit \
|| $id_build_1_exit \
|| $id_build_2_exit \
|| $client_api_build_exit \
|| $client_1_exit \
|| $client_2_exit \
|| $client_3_exit \
))

View File

@ -26,9 +26,12 @@ Ruma currently requires Rust 1.43.0. 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.
The exception to this is ruma-signatures (and hence ruma with the federation-api
feature) since it depends on [ring][], which is only guaranteed to work on the
latest stable.
There are two exceptions to this:
* ruma-signatures (and hence ruma with the federation-api feature) since it
depends on [ring][], which is only guaranteed to work on the latest stable.
* ruma-client depends on some I/O libraries (and also on ring, conditionally),
so it is also only guaranteed to work on the latest stable.
[ring]: https://github.com/briansmith/ring/