Tags: ShadowRZ/ruma
Tags
ruma-state-res 0.13.0 Bug fixes: - Fix tiebreaking logic in state resolution. Improvements: - The `unstable-exhaustive-types` cargo feature was replaced by the `ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg` settings, it can be enabled at compile-time with the `RUSTFLAGS` environment variable, or inside `.cargo/config.toml`. It can also be enabled by setting the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable.
ruma-signatures 0.17.0 Improvements: - The `unstable-exhaustive-types` cargo feature was replaced by the `ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg` settings, it can be enabled at compile-time with the `RUSTFLAGS` environment variable, or inside `.cargo/config.toml`. It can also be enabled by setting the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable.
ruma-server-util 0.5.0 No changes for this version
ruma-push-gateway-api 0.11.0
Improvements:
- The `unstable-exhaustive-types` cargo feature was replaced by the
`ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg`
settings, it can be enabled at compile-time with the `RUSTFLAGS` environment
variable, or inside `.cargo/config.toml`. It can also be enabled by setting
the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable.
- `PusherData` allows to set custom data for the pusher in the `data` field, due
to a clarification in the spec.
- The `default_payload` field that was behind the `unstable-unspecified` was
removed. It can be added manually to the custom data.
ruma-identity-service-api 0.11.0 Improvements: - The `unstable-exhaustive-types` cargo feature was replaced by the `ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg` settings, it can be enabled at compile-time with the `RUSTFLAGS` environment variable, or inside `.cargo/config.toml`. It can also be enabled by setting the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable.
ruma-federation-api 0.11.0 Improvements: - The `unstable-exhaustive-types` cargo feature was replaced by the `ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg` settings, it can be enabled at compile-time with the `RUSTFLAGS` environment variable, or inside `.cargo/config.toml`. It can also be enabled by setting the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable.
ruma-events 0.30.0 Improvements: - Add unstable support for MSC4171 for the m.member_hints state event. - The `ruma_identifiers_storage` compile-time `cfg` setting can also be configured by setting the `RUMA_IDENTIFIERS_STORAGE` environment variable at compile time. It has the benefit of not requiring to re-compile all the crates of the dependency chain when the value is changed. - The `unstable-exhaustive-types` cargo feature was replaced by the `ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg` settings, it can be enabled at compile-time with the `RUSTFLAGS` environment variable, or inside `.cargo/config.toml`. It can also be enabled by setting the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable. Breaking changes: - Take newly introduced `DirectUserIdentifier(str)` as a key for `DirectEventContent`. This change allows to have an email or MSISDN phone number as a key for example, which can be used when issuing invites through third-party systems. `DirectUserIdentifier` can easily be converted to an `UserId`.
ruma-common 0.15.0
Breaking changes:
- `#[serde(flatten)]` on the only body field of a `#[request]` or `#[response]`
struct is disallowed. `#[ruma_api(body)]` must be used instead.
Improvements:
- The `ruma_identifiers_storage` compile-time `cfg` setting can also be
configured by setting the `RUMA_IDENTIFIERS_STORAGE` environment variable at
compile time. It has the benefit of not requiring to re-compile all the crates
of the dependency chain when the value is changed.
- The `unstable-exhaustive-types` cargo feature was replaced by the
`ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg`
settings, it can be enabled at compile-time with the `RUSTFLAGS` environment
variable, or inside `.cargo/config.toml`. It can also be enabled by setting
the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable.
- `HttpPusherData` allows to set custom data for the pusher in the `data` field,
due to a clarification in the spec.
- The `default_payload` field that was behind the `unstable-unspecified` was
removed. It can be added manually to the custom data.
ruma-client-api 0.20.0 Breaking changes: - `ErrorKind` does not implement `AsRef<str>` and `Display` anymore. To get the same result, use `ErrorKind::errcode()`. The `ErrorCode` that is returned implements those traits. Improvements: - Add unstable support for reporting rooms, according to MSC4151. - The `unstable-exhaustive-types` cargo feature was replaced by the `ruma_unstable_exhaustive_types` compile-time `cfg` setting. Like all `cfg` settings, it can be enabled at compile-time with the `RUSTFLAGS` environment variable, or inside `.cargo/config.toml`. It can also be enabled by setting the `RUMA_UNSTABLE_EXHAUSTIVE_TYPES` environment variable. - Add `ErrorKind::ThreepidMediumNotSupported`, according to MSC4178. - Add `ErrorKind::UserSuspended`, according to MSC3823. - `EmailPusherData` allows to set custom data for the pusher in the `data` field, due to a clarification in the spec.
PreviousNext