You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: In‑App Update Check & Auto‑Update from GitHub Releases #368
Currently, OpenScreen is evolving quickly and we’re seeing frequent updates. While that’s great, it’s a bit difficult to manually download each new release from GitHub and set it up from scratch every time.
Request:
Could we add support for in‑app update checks and automatic updates? Ideally:
The app should check for new releases on GitHub (via the GitHub Releases API).
Notify the user when a new version is available.
Optionally download and install the update directly in‑app, without requiring manual setup.
Technical Approach (possible options):
Use the GitHub Releases API to fetch the latest release metadata.
Compare the current app version with the latest release tag.
Provide a UI prompt for the user to update.
For Windows/macOS/Linux, integrate with existing auto‑update frameworks:
Windows: Squirrel.Windows or WinSparkle
macOS: Sparkle framework
Linux: AppImageUpdate or package manager hooks
Alternatively, bundle a lightweight updater that downloads the latest binary from GitHub and replaces the current installation.
Benefits:
Saves time for users by avoiding repeated manual downloads.
Ensures everyone stays on the latest version with bug fixes and new features.
Improves adoption of updates, especially for non‑technical users.
Refs #313 + #358, which land most of this: a tray Check for Updates, the GitHub Releases API, version comparison, and in-place download + install on Windows, macOS and Linux — omitted where a package manager already owns the update (Store, Flathub, Snap, Nix).
Unreleased; ships after 1.9.6.
Keeping this open for the part that is not done: there is no automatic check. checkForUpdates() has exactly one caller, the tray menu entry.
Will ship in 1.10.0. The check itself landed with the auto-updater; #414 gave it the entry points.
The latest release is read from the GitHub Releases API and compared against the running version.
A dialog names both versions when a newer one exists.
It downloads and installs in place on the builds we ship (NSIS, DMG, AppImage, deb, rpm, pacman), with no manual setup. On Microsoft Store, Flathub, Snap, and Nix nothing is offered at all, because the package manager already updates the app there — offering a second install path would leave the user with two copies.
Reachable from the tray, the app menu (Help on Windows/Linux), the editor's wordmark menu, and the HUD settings panel, which also shows the running version.
One thing it does not do: check on its own. There is no scheduled or background check — you ask, it answers. #301 tracks the preferences that would change that.
Activity
EtienneLescot commentedon Aug 20, 2026
Refs #313 + #358, which land most of this: a tray Check for Updates, the GitHub Releases API, version comparison, and in-place download + install on Windows, macOS and Linux — omitted where a package manager already owns the update (Store, Flathub, Snap, Nix).
Unreleased; ships after 1.9.6.
Keeping this open for the part that is not done: there is no automatic check.
checkForUpdates()has exactly one caller, the tray menu entry.EtienneLescot commentedon Aug 20, 2026
Will ship in 1.10.0. The check itself landed with the auto-updater; #414 gave it the entry points.
One thing it does not do: check on its own. There is no scheduled or background check — you ask, it answers. #301 tracks the preferences that would change that.
Generated by Claude Code