refactor: Switch to upstream Ruma #1656

Merged
ginger merged 108 commits from ginger/ruma-upstreaming into main 2026-04-29 13:37:55 +00:00
Owner

This pull request switches from https://forgejo.ellis.link/continuwuation/ruwuma to upstream Ruma, reducing code rot and allowing us to use upstream features missing from ruwuma.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request switches from https://forgejo.ellis.link/continuwuation/ruwuma to upstream Ruma, reducing code rot and allowing us to use upstream features missing from ruwuma. <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
Co-authored-by: Jade Ellis <jade@ellis.link>
Sent from my Steam Deck
chore: Clippy fixes
Some checks failed
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m26s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m54s
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 9s
Documentation / Build and Deploy Documentation (pull_request) Successful in 5m22s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Successful in 8m59s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 9m47s
2497a959c9
ginger changed title from refactor: Switch to upstream Ruma to WIP: refactor: Switch to upstream Ruma 2026-04-13 22:39:30 +00:00
Author
Owner

Blocked on upstream merging some PRs. For now this uses my own fork of ruma.

Blocked on upstream merging some PRs. For now this uses my own fork of ruma.
chore: Changelog
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 32s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m19s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m56s
Documentation / Build and Deploy Documentation (pull_request) Successful in 4m31s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Successful in 7m54s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
1ed620c524
fix: Fix failing test
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 34s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m14s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m36s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m59s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Successful in 8m1s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 10m16s
2b0b3669fc
refactor: Improve summary service logging
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m14s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m24s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Successful in 8m8s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m49s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m12s
e8967c43bb
nex requested changes 2026-04-14 15:00:16 +00:00
Dismissed
nex left a comment

preliminary comments

preliminary comments
@ -242,3 +235,1 @@
"Tried to change an existing master key, UIA required"
)));
}
return Err!(Request(Forbidden(
Owner

UIA is supposed to be skipped if the keys are also the same, not just if it's new

UIA is supposed to be skipped if the keys are also the same, not just if it's new
ginger marked this conversation as resolved
@ -258,3 +248,1 @@
"Tried to change an existing user signing key, UIA required"
)));
}
return Err!(Request(Forbidden(
Owner

UIA is supposed to be skipped if the keys are also the same, not just if it's new

UIA is supposed to be skipped if the keys are also the same, not just if it's new
ginger marked this conversation as resolved
@ -278,3 +265,1 @@
"Tried to update an existing self signing key, UIA required"
)));
}
return Err!(Request(Forbidden(
Owner

UIA is supposed to be skipped if the keys are also the same, not just if it's new

UIA is supposed to be skipped if the keys are also the same, not just if it's new
ginger marked this conversation as resolved
@ -33,3 +33,4 @@
.await
.unwrap_or_else(|_| RoomMemberEventContent::new(MembershipState::Ban));
content.membership = MembershipState::Ban;
Owner

it'd make more sense to just create a new RoomMemberEventContent here, the only fields we want for a ban are membership, reason, and redact_events (MSC4293)

it'd make more sense to just create a new RoomMemberEventContent here, the only fields we want for a ban are `membership`, `reason`, and `redact_events` (MSC4293)
ginger marked this conversation as resolved
@ -36,0 +40,4 @@
content.is_direct = None;
content.join_authorized_via_users_server = None;
content.third_party_invite = None;
// TODO(upstream): MSC4293
Owner

MSC4293 is an important T&S feature we actively use, I don't think we can merge this until support is upstreamed

MSC4293 is an important T&S feature we actively use, I don't think we can merge this until support is upstreamed
Author
Owner

This is blocked on your own PR 🧌

This is blocked on [your own PR](https://github.com/ruma/ruma/pull/2453) 🧌
Owner

I know, just saying

I know, just saying
ginger marked this conversation as resolved
@ -389,3 +384,3 @@
// How did we get here?
return Err!(BadServerResponse(
"Remote room version {room_version_id} is not supported by conduwuit"
"Remote room version {room_version} is not supported by conduwuit"
Owner

conduwuit -> continuwuity

conduwuit -> continuwuity
ginger marked this conversation as resolved
@ -44,0 +42,4 @@
event.reason.clone_from(&body.reason);
event.is_direct = None;
event.join_authorized_via_users_server = None;
event.third_party_invite = None;
Owner

Same thing as for ban. Also, MSC4293 will need adding here, it was missed in the ruwuma impl

Same thing as for ban. Also, MSC4293 will need adding here, it was missed in the ruwuma impl
ginger marked this conversation as resolved
fix: Enable compatibility feature to fix federation with old conduit-family homeservers
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 34s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m21s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m32s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m59s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Successful in 8m6s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m36s
7eededadfe
@ -0,0 +5,4 @@
use crate::Ruma;
/// # `GET /_matrix/client/unstable/uk.half-shot.msc2666/user/mutual_rooms`
Owner

This endpoint is stable now

This endpoint is stable now
Author
Owner

That's a matter for upstream, they haven't added the stable version yet

That's a matter for upstream, they haven't added the stable version yet
Owner

lmao what

lmao what
nex marked this conversation as resolved
@ -249,0 +112,4 @@
};
// Update our local copies of their profile fields
services.users.clear_profile(user_id).await;
Owner

Should probably only do this if there's actually a difference

Should probably only do this if there's actually a difference
Author
Owner

I don't think checking that will provide a meaningful performance boost

I don't think checking that will provide a meaningful performance boost
ginger marked this conversation as resolved
@ -249,0 +121,4 @@
};
set_profile_field(services, user_id, ProfileFieldChange::Set(value)).await;
}
Owner

Needs to make sure the total profile in canonical representation does not exceed 64KiB

Needs to make sure the total profile in canonical representation does not exceed 64KiB
ginger marked this conversation as resolved
@ -249,0 +156,4 @@
if let Ok(value) = ProfileFieldValue::new(field.as_str(), value) {
set_profile_field(services, user_id, ProfileFieldChange::Set(value.clone())).await;
Ok(Some(value))
Owner

Needs to make sure the total profile in canonical representation does not exceed 64KiB

Needs to make sure the total profile in canonical representation does not exceed 64KiB
ginger marked this conversation as resolved
@ -266,0 +252,4 @@
}
}
async fn set_profile_field(services: &Services, user_id: &UserId, change: ProfileFieldChange) {
Owner

This function needs bounds checking really. Individual fields shouldn't be more than 64KiB and the entire profile shouldn't either

This function needs bounds checking really. Individual fields shouldn't be more than 64KiB and the entire profile shouldn't either
ginger marked this conversation as resolved
@ -41,2 +39,2 @@
reason: body.reason.clone(),
})
..PartialPdu::timeline(
&assign!(RoomRedactionEventContent::new_v11(body.event_id.clone()), {
Owner

uhhh new_v11? What about other room versions?

uhhh `new_v11`? What about other room versions?
Author
Owner

new_v11 sets the redacts field in the content, as opposed to new_v1 which doesn't. We set both redacts-in-content and redacts-in-PDU for all room versions.

`new_v11` sets the `redacts` field in the content, as opposed to `new_v1` which doesn't. We set both `redacts`-in-content and `redacts`-in-PDU for all room versions.
nex marked this conversation as resolved
@ -145,3 +140,3 @@
}
if body.reason.as_ref().is_some_and(|s| s.len() > 750) {
if body.reason.len() > 750 {
Owner

Can we drop this arbitrary limit? or raise it to something sensible like 2000?

Can we drop this arbitrary limit? or raise it to something sensible like 2000?
ginger marked this conversation as resolved
@ -201,3 +195,3 @@
}
if reason.as_ref().is_some_and(|s| s.len() > 750) {
if reason.len() > 750 {
Owner

same as prior

same as prior
ginger marked this conversation as resolved
@ -444,3 +461,3 @@
debug_warn!("skipping empty initial state event with content of `{{}}`: {event:?}");
debug_warn!("content: {}", pdu_builder.content.get());
debug_warn!("content: {}", partial_pdu.content.get());
continue;
Owner

Wait, we're not supposed to do this per the spec, why do we do this at all? This if statement should be dropped

Wait, we're not supposed to do this per the spec, why do we do this at all? This if statement should be dropped
ginger marked this conversation as resolved
@ -91,2 +89,2 @@
} else {
None
let room_id: Option<OwnedRoomId> = match room_version_rules.room_id_format {
| RoomIdFormatVersion::V1 => Some(RoomId::new_v1(services.globals.server_name())),
Owner

Can we not drop the custom room ID stuff? That's like one of the coolest features conduwuit had and it'd be a shame to see it go

Can we not drop the custom room ID stuff? That's like one of the coolest features conduwuit had and it'd be a shame to see it go
ginger marked this conversation as resolved
@ -245,1 +269,3 @@
membership: MembershipState::Join,
PartialPdu::state(
sender_user.as_str(),
&assign!(RoomMemberEventContent::new(MembershipState::Join), {
Owner

Nit: maybe clone the invoking user's membership content in the tombstoned room to the new one? not sure if it's worth it

Nit: maybe clone the invoking user's membership content in the tombstoned room to the new one? not sure if it's worth it
Author
Owner

I don't think that's necessary

I don't think that's necessary
nex marked this conversation as resolved
@ -0,0 +19,4 @@
rate_limited: false,
authentication: AccessToken,
history: {
unstable => "/_matrix/client/unstable/uk.timedout.msc4323/admin/suspend/{user_id}",
Owner

This is stable in v1.18 now -> /_matrix/client/v1/admin/suspend/{userId}

This is stable in v1.18 now -> `/_matrix/client/v1/admin/suspend/{userId}`
ginger marked this conversation as resolved
@ -0,0 +19,4 @@
rate_limited: false,
authentication: AccessToken,
history: {
unstable => "/_matrix/client/unstable/uk.timedout.msc4323/admin/suspend/{user_id}",
Owner

Stable in v1.18 -> /_matrix/client/v1/admin/suspend/{userId}

Stable in v1.18 -> `/_matrix/client/v1/admin/suspend/{userId}`
ginger marked this conversation as resolved
@ -0,0 +1,271 @@
//! Types for invite filtering ([MSC4155]).
Owner

Does this not want upstreaming?

Does this not want upstreaming?
ginger marked this conversation as resolved
@ -0,0 +1,91 @@
//! Types for the [`org.matrix.msc4284.policy`] event.
Owner

No point migrating this, once this PR is merged I'll rebase #1487 on it and use upstreamed structs

No point migrating this, once this PR is merged I'll rebase #1487 on it and use upstreamed structs
Owner

no no nvm you'll need it in order to merge current code lmao

no no nvm you'll need it in order to merge current code lmao
nex marked this conversation as resolved
@ -0,0 +1,58 @@
//! `GET /_matrix/federation/*/rooms/{roomId}/report/{eventId}`
Owner

We support this?

We support this?
Author
Owner

I don't know if we use the route, but it was in ruwuma, so I copied it to ruminuwuity

I don't know if we use the route, but it was in ruwuma, so I copied it to ruminuwuity
Owner

you can probably drop it i dont think we support that

you can probably drop it i dont think we support that
ginger marked this conversation as resolved
@ -165,0 +218,4 @@
let power_levels_event: RoomPowerLevelsEventContent = self
.room_state_get_content(room_id, &StateEventType::RoomPowerLevels, "")
.await
.unwrap_or_else(|_| {
Owner

This silently swallows deserialisation errors doesn't it? That's probably bad

This silently swallows deserialisation errors doesn't it? That's probably bad
ginger marked this conversation as resolved
nex left a comment

finished reviewing now

finished reviewing now
ginger force-pushed ginger/ruma-upstreaming from 7eededadfe
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 34s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m21s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m32s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m59s
Deploy Element Web / 🏗️ Build and Deploy (pull_request) Successful in 8m6s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 11m36s
to d20707533a
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m16s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m41s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 10m35s
2026-04-22 14:44:54 +00:00
Compare
ginger force-pushed ginger/ruma-upstreaming from cabd559ae2 to 5add5b6a13
Some checks failed
Checks / Prek / Check changed files (pull_request) Successful in 8s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 37s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m25s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m35s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 10m47s
2026-04-24 13:00:06 +00:00
Compare
ginger force-pushed ginger/ruma-upstreaming from 5add5b6a13
Some checks failed
Checks / Prek / Check changed files (pull_request) Successful in 8s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 37s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m25s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m35s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 10m47s
to 58b716e264
Some checks failed
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 35s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m25s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m29s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m47s
2026-04-24 17:39:57 +00:00
Compare
ginger changed title from WIP: refactor: Switch to upstream Ruma to refactor: Switch to upstream Ruma 2026-04-25 03:12:56 +00:00
ginger force-pushed ginger/ruma-upstreaming from 58b716e264
Some checks failed
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 35s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m25s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m29s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m48s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 5m47s
to 561a7dccd3
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Checks / Prek / Check changed files (pull_request) Successful in 35s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m15s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m46s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 2m42s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 4m18s
2026-04-25 13:41:35 +00:00
Compare
fix: Re-add support for MSC4293
Some checks failed
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 35s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m23s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m33s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m49s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
3bb97ff6b5
refactor: Drop unused MSC3843 endpoint definition
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Checks / Prek / Check changed files (pull_request) Successful in 8s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m17s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m28s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m44s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
7f78348a42
chore: Update news fragment
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 34s
Checks / Prek / Check changed files (pull_request) Successful in 33s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m14s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m21s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m57s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m16s
9168eb1ed7
ginger force-pushed ginger/ruma-upstreaming from 9168eb1ed7
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 34s
Checks / Prek / Check changed files (pull_request) Successful in 33s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m14s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m21s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m57s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m16s
to 7b99757337
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Checks / Prek / Check changed files (pull_request) Successful in 35s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m15s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m45s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m46s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 10m39s
2026-04-28 13:23:55 +00:00
Compare
nex approved these changes 2026-04-28 14:55:24 +00:00
Dismissed
nex requested changes 2026-04-29 03:14:09 +00:00
Dismissed
nex left a comment

blocking until bugs fixed. Found so far: appservice puppeting broken, creating a v12 room seemingly fails (see maintainer room for more info)

blocking until bugs fixed. Found so far: appservice puppeting broken, creating a v12 room seemingly fails (see maintainer room for more info)
fix: Fix appservice authentication
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 29s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m13s
Checks / Prek / Check changed files (pull_request) Successful in 9s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m28s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m53s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m16s
049babc7ca
fix: Fix panic when creating rooms
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Checks / Prek / Check changed files (pull_request) Successful in 33s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m12s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m28s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m46s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m15s
Checks / Prek / Check changed files (push) Successful in 32s
Checks / Prek / Pre-commit & Formatting (push) Successful in 1m18s
Documentation / Build and Deploy Documentation (push) Successful in 1m24s
Checks / Prek / Clippy and Cargo Tests (push) Successful in 9m28s
Release Docker Image / Build linux-amd64 (release) (push) Successful in 17m16s
Release Docker Image / Build linux-arm64 (release) (push) Successful in 17m24s
Release Docker Image / Create Multi-arch Release Manifest (push) Successful in 18s
Release Docker Image / Build linux-arm64 (max-perf) (push) Has been cancelled
Release Docker Image / Build linux-amd64 (max-perf) (push) Has been cancelled
Release Docker Image / Create Max-Perf Manifest (push) Has been cancelled
Release Docker Image / Release Binaries (push) Has been cancelled
Release Docker Image / Mirror Images (push) Has been cancelled
9491be928d
nex approved these changes 2026-04-29 13:35:30 +00:00
nex left a comment

Let me OUT

Let me OUT
ginger merged commit 9491be928d into main 2026-04-29 13:37:55 +00:00
Sign in to join this conversation.
No reviewers
nex
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
continuwuation/continuwuity!1656
No description provided.