Describe your suggested feature
Hello, i have used the app for a couple of weeks.
Correct me if i'm wrong, but i noticed that the app update system checks every single new hash commit and notify the user that an update is available.
Since at the moment the last "stable" build is stuck at October 2025 and since the pull requests are merged directly on the master branch, my personal opinion is to split from "stable" update channel and "experimental" channel.
This could be done either by
-
merging pull requests on a detached development branch and consolidates all on master when releasing a new stable build
-
extending the logics on the app introducing a new toggle to enable the notifications also for development updates
Other details
No response
Acknowledgements
Describe your suggested feature
Hello, i have used the app for a couple of weeks.
Correct me if i'm wrong, but i noticed that the app update system checks every single new hash commit and notify the user that an update is available.
Since at the moment the last "stable" build is stuck at October 2025 and since the pull requests are merged directly on the master branch, my personal opinion is to split from "stable" update channel and "experimental" channel.
This could be done either by
merging pull requests on a detached development branch and consolidates all on master when releasing a new stable build
extending the logics on the app introducing a new toggle to enable the notifications also for development updates
Other details
No response
Acknowledgements