-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix auto updater #2875
Fix auto updater #2875
Conversation
5703a29
to
155fb8f
Compare
82746b1
to
e549efb
Compare
Is the info at https://github.com/balena-io/etcher/blob/master/docs/USER-DOCUMENTATION.md#simulate-an-update-alert now out of date? |
a84fa5d
to
a1c2b7b
Compare
a1c2b7b
to
957942b
Compare
try { | ||
const release = await autoUpdater.checkForUpdates() | ||
const isOutdated = semver.compare(release.updateInfo.version, version) > 0 | ||
const shouldUpdate = parseInt(release.updateInfo.stagingPercentage, 10) > 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure this is necessary? Nothing I can find at https://www.electron.build/auto-update#staged-rollouts suggests you manually need to check the stagingPercentage value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lurch It's because we manually check and then download, so it's an extra safety step before triggering the download for those connected with a data plan. One thing I didn't check is if release.updateInfo.version
is unchanged in case no release is available (i.e. a newer release's stagingPercentage
is 0), but I will
Change-type: patch Changelog-entry: Fix auto-updater check for updates Signed-off-by: Lorenzo Alberto Maria Ambrosi <[email protected]>
957942b
to
8c2c4e2
Compare
No description provided.