Release ruma-identifiers-validation 0.9.3

This commit is contained in:
Jonas Platte 2023-10-11 21:25:13 +02:00
parent 11e38d23dd
commit a9f42be255
No known key found for this signature in database
GPG Key ID: AAA7A61F696C3E0C
3 changed files with 15 additions and 2 deletions

View File

@ -23,7 +23,7 @@ ruma-client-api = { version = "0.17.0", path = "crates/ruma-client-api" }
ruma-events = { version = "0.27.3", path = "crates/ruma-events" }
ruma-federation-api = { version = "0.8.0", path = "crates/ruma-federation-api" }
ruma-html = { version = "0.1.0", path = "crates/ruma-html" }
ruma-identifiers-validation = { version = "0.9.2", path = "crates/ruma-identifiers-validation" }
ruma-identifiers-validation = { version = "0.9.3", path = "crates/ruma-identifiers-validation" }
ruma-identity-service-api = { version = "0.8.0", path = "crates/ruma-identity-service-api" }
ruma-macros = { version = "=0.12.0", path = "crates/ruma-macros" }
ruma-push-gateway-api = { version = "0.8.0", path = "crates/ruma-push-gateway-api" }

View File

@ -1,5 +1,18 @@
# [unreleased]
# 0.9.3
Improvements:
- Don't require room IDs to contain a server name
- Room IDs being splittable into localpart and servername does not have
much inherent value and there are proposals like [MSC4051] that propose
changing the format. Relaxing the rules makes Ruma forwards-compatible
with those proposals. The server_name accessor is kept because it is
used by at least one downstream, but is updated to return an `Option`.
[MSC4051]: https://github.com/matrix-org/matrix-spec-proposals/pull/4051
# 0.9.2
Bug fixes:

View File

@ -4,7 +4,7 @@ description = "Validation logic for ruma-common and ruma-macros"
homepage = "https://www.ruma.io/"
repository = "https://github.com/ruma/ruma"
license = "MIT"
version = "0.9.2"
version = "0.9.3"
edition = "2021"
rust-version = { workspace = true }