Add auto-update workflow #786
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
|
I can take a crack at rebasing this after the next 2 frontend refactors are done @garrettmflynn the next one was the separation of frontend tests and stories from other assets/pages, correct? |
|
Yep! I'll make the final changes noted yesterday after that's merged |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
|
OK this PR is rebased; however, it always looks as if it triggered some problem in the Windows test (perhaps that same you alluded to about modals popping up and closing?) |
|
Worked great on Windows! |
Where did it do this? I have no idea what's going on here 😅 |
I mean the full build and distributable on Windows; it showed the auto-update thing in settings and it all looked perfect; auto-updating installed the current released version in the previous installation directory |
|
Ah awesome! |
This PR implements a user-driven update workflow for the GUIDE that notifies users of a new release on the Settings page. This should only show if a new release is actually present compared to the current version.
Clicking the info icon will display a record of the release notes.
The Update button then triggers the
electron-updaterpackage to download the latest release (with a related progress bar) and asks the user if they'd like to restart the application now (activating the downloaded release) or defer this until a manual close.To test, I'd suggest that you create a local build and go through this workflow. The success of this process on Mac depends on proper code-signing, but I believe you should be able to complete this on a Windows PC.