-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable of auto-update #1211
Comments
Note that a community user in a public Slack message recently expressed what they believed was a valid reason to want to continue using an older release. If they happen to be on Windows or macOS, they'd only be able to use it for one session as long as they're Internet-connected since the auto-update would kick in. Just wanted to cite at least one real request for this in the wild. |
@jameskerr recently expressed an interest in adding a user Preference to include support for auto-updates via Channels (https://www.electron.build/tutorials/release-using-channels.html). This would allow users to express a willingness to opt in to beta releases should we choose to start producing them. And this would seem like a logical place to also put in the option to disable the auto-updates entirely. |
I did an exhaustive verification of this feature in a personal fork (based on Zui commit d938f8e) where I created GA-style releases tagged Below are detailed notes on the variations I performed on macOS, Windows, and Linux. Before the steps in each block of bullets I've done just a "fresh" install of "On Startup"
"Manually"
"On Startup & Daily"
Finally, the two requirements described earlier in this issue that we did not end up addressing as part of the linked PR #2866 are tracked in new issues #2944 and #2945. Thanks @jameskerr! |
Right now auto-update is always enabled on macOS and Windows. Let's imagine a scenario where the user intentionally wants to keep running a build that's different than the latest GA one. While they can install it and start using it, within minutes they'll be informed that the latest GA version has been downloaded/installed in the background and they will be given the option to restart into that new version now/later. This means they effectively can't quit & restart the app and remain on their different build. Therefore it seems like we'd need to have a Preference option to disable the auto-update.
One example use case for this involves Support. We may at some point want to offer special builds to users that provide early access to experimental functionality. We'd like them to be able to continue running such builds and quit/restart as necessary until they explicitly "opt in" to upgrade to a GA release.
Yet another example use case might just be a conservative user that likes to always manually upgrade so they can take their time browsing release notes and confronting the potential hit to productivity should they fear hitting new bugs or climbing the learning curve of new features in a new release.
Another variation of this came up while responding to community issue #2685. In brief, as a government agency, they summarized one of their policies:
In that case, just having a Preference would probably be inadequate since a user could conceivably just go into the Preferences menu and re-enable auto-updates. Therefore we likely would want to also provide an install-time option so that the app would never permit auto-update under any circumstances.
The text was updated successfully, but these errors were encountered: