App update system revision

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

• My suggestion is NOT about adding a new provider
• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

No files, tests, or entry points are named. Start by locating the app update-checking and notification logic, then clarify whether the project wants separate stable and experimental channels or an opt-in development-update toggle; completion criteria are not defined in the issue.