Repository navigation
feat(update): install updates from within the application - #222
Merged
Razzmatazzz merged 2 commits intoSep 7, 2026
Merged
Razzmatazzz merged 2 commits into
Razzmatazzz merged 2 commits into
Conversation
Updating meant downloading the release archive from GitHub, deleting the old folder, and unpacking the new one by hand. The update check already detected new releases, but could only offer a link to the download page. The new-version notification now carries an "Install and restart" button. The release archive is downloaded to the local profile with progress reported in place, verified, and unpacked; the running executable then copies itself to staging and relaunches in --apply-update mode. That copy waits for the application to exit, replaces the installation directory, and starts the new version. Reusing the running executable as the launcher avoids shipping a second artifact, and keeps the command line contract the one that build was compiled against. Every replaced file is backed up first. If a copy fails after retries the previous version is restored, so a failed update leaves a working install rather than a mixed one. Locked files are retried, because anti-virus scanners hold handles briefly after exit, and an installation directory that is not writable requests elevation instead of failing. Nothing is downloaded until the user asks for it, and the confirmation dialog warns against restarting mid-raid. The release workflow now also passes AssemblyVersion. Version is set from the tag but does not override the AssemblyVersion held in the project file, so the two only matched because the value was bumped by hand. A passive notification tolerates that drift; an updater does not, since a missed bump would make it reoffer a version already installed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Razzmatazzz
approved these changes
Sep 7, 2026
Razzmatazzz
left a comment
Member
There was a problem hiding this comment.
Thanks for taking on the work of adding this feature!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updating meant downloading the release archive from GitHub, deleting the old folder, and unpacking the new one by hand. The update check already detected new releases, but could only offer a link to the download page.
The new-version notification now carries an "Install and restart" button. The release archive is downloaded to the local profile with progress reported in place, verified, and unpacked; the running executable then copies itself to staging and relaunches in --apply-update mode. That copy waits for the application to exit, replaces the installation directory, and starts the new version. Reusing the running executable as the launcher avoids shipping a second artifact, and keeps the command line contract the one that build was compiled against.
Every replaced file is backed up first. If a copy fails after retries the previous version is restored, so a failed update leaves a working install rather than a mixed one. Locked files are retried, because anti-virus scanners hold handles briefly after exit, and an installation directory that is not writable requests elevation instead of failing.
Nothing is downloaded until the user asks for it, and the confirmation dialog warns against restarting mid-raid.
The release workflow now also passes AssemblyVersion. Version is set from the tag but does not override the AssemblyVersion held in the project file, so the two only matched because the value was bumped by hand. A passive notification tolerates that drift; an updater does not, since a missed bump would make it reoffer a version already installed.