Let maintainers know that an action is required on their side

• Add the label release-required Please cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module) when you request a maintainer to cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)

• Add the label release-blocker Follow-up is required before cutting a new release if a follow-up is required before cutting a new release

• Add the label publish-required Please publish libraries (`Devolutions.Gateway.Utils`, OpenAPI clients, etc) when you request a maintainer to publish libraries (Devolutions.Gateway.Utils, OpenAPI clients, etc.)

• Add the label publish-blocker Follow-up is required before publishing libraries if a follow-up is required before publishing libraries

CI failed with some weird errors:

I hope a rerun will help.
EDIT: I didn't help

@RRRadicalEdward should be fixed if you rebase on master!

@RRRadicalEdward It also occurred to me that this could be a "runtime" option in top bar so the user can adjust even after starting the session.

@RRRadicalEdward It also occurred to me that this could be a "runtime" option in top bar so the user can adjust even after starting the session.

We can do it. It will require some refactoring in IronVNC since right now the setting can't be changed after the session is started - https://github.com/Devolutions/IronVNC/blob/master/crates/ironvnc-web/src/session.rs#L807

@RRRadicalEdward should be fixed if you rebase on master!

Seems like, there are still some issues

@RRRadicalEdward now this should be fixed for real, I rebased the PR 🙂

EDIT: Apparently it’s still red. I reported to our DevOps team.

@RRRadicalEdward It also occurred to me that this could be a "runtime" option in top bar so the user can adjust even after starting the session.

We can do it. It will require some refactoring in IronVNC since right now the setting can't be changed after the session is started - https://github.com/Devolutions/IronVNC/blob/master/crates/ironvnc-web/src/session.rs#L807

I see, yes. We could add a new event UiEvent::SetWheelSpeedFactor that is triggered by passing a set_wheel_speed_factor extension to extension_call. That would be a good opportunity to test the design of extension_call.