Kévin Commaille b1790e05ce push: Allow to add custom data for pushers
Due to a clarification in the spec.
2024-12-15 03:10:09 -05:00

81 lines
1.5 KiB
Markdown

# [unreleased]
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.
# 0.10.0
Upgrade `ruma-events` to 0.29.0.
# 0.9.0
Breaking changes:
- The http crate had a major version bump to version 1.1
# 0.8.0
No changes for this version
# 0.7.1
Improvements:
* Update links to the latest version of the Matrix spec
# 0.7.0
No changes for this version
# 0.6.0
Breaking changes:
* Remove `PartialEq` implementation for `NotificationCounts`
# 0.5.0
Breaking changes:
* Upgrade dependencies
# 0.4.0
Breaking changes:
* Upgrade dependencies
# 0.3.0
Breaking changes:
* Upgrade dependencies
# 0.2.0
Breaking changes:
* Upgrade ruma-events to 0.23.0
# 0.1.0
Breaking changes:
* Remove `Copy` implementation for `NotificationCounts` to avoid simple changes
being breaking
* Change `Box<RawJsonValue>` to `&RawJsonValue` in request types
* Upgrade public dependencies
# 0.0.1
* Add endpoint `send_event_notification::v1`