[afonsojramos]

Summary

Gitify keeps updating itself by default and leaves updates to the package manager only where one owns them, so a Scoop installation no longer gets a second copy installed outside Scoop's directory. A persistent Default / On / Off choice under Settings > System lets every user decide.

• Automatic updates default to off for Scoop (detected from its installation metadata), Flatpak, and Snap. deb, rpm, Homebrew, AppImage, direct downloads, and unidentified installations keep them on.
• Package maintainers can select the managed default with an empty disable-auto-updates file in the resources directory or GITIFY_DISABLE_AUTO_UPDATE=1 in the launcher.
• Turning updates off cancels scheduled checks and active downloads, prevents installation on quit, and changes the tray item to View releases.

On macOS, the native update handoff waits for Restart or for a quit with updates on, because an update already handed to Squirrel cannot be revoked. A plain quit installs without relaunching. A failed later check keeps a downloaded update installable, while a replacement download drops the ready state until it finishes.

Validation

• pnpm check, pnpm i18n:check, and all 2,179 unit tests pass.
• Checked the Settings choice in a local Linux build: the captions follow Default, On, and Off, and the choice persists.
• Native package-manager installations and the Windows/macOS installer flows have not been exercised on their platforms.

Closes #3283

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
88.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[setchy]

This does seem to be a recurring question... my hope is we maintain a user-base which keeps up with our releases and doesn't drift behind 🥲

[setchy]

Thanks Afonso — nice work, and the tests around flipping the setting quickly are great.

some new feedback areas to consider:

1. Rebase. Conflicts with main in 8 files. When resolving: drop the Settings snapshot (main deleted it in #3514), and re-check the new radio buttons against the updated Settings layout (#3492–#3496). Then re-run the unit and visual tests.

2. Defaults — shall we keep Gitify keep handling updates itself where it can.

• Off: Scoop (the bug in #3283), Flatpak, Snap.
• On: deb, rpm, Homebrew, AppImage, direct downloads, and anything we can't identify.

That lets us delete the dpkg/rpm/pacman ownership checks and their tests — less code, no commands at startup. Keep the packager marker/env var, and keep Off available to everyone. Heads up: #3374 (FlatPark) wraps our .deb in a Flatpak, so the Flatpak check needs to stay ahead of any deb/rpm logic.

[afonsojramos]

Rebased onto main and defaults are now Off only for Scoop, Flatpak, and Snap. The pacman/dpkg/rpm ownership checks and their tests are deleted, so detection runs no commands.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
89.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[setchy]

Approved. I assume you're feeling highly confidence that the OS / package update managers will keep gitify updates going forward once released. I guess users can always override in Settings, correct?