@eb5fd7e6 It doesn't seem to be a problem with Forgejo Next, so maybe it's fixed in the new version coming out?