Enhance Updater to properly support Pre-Releases - #69
Merged
Conversation
…t valid release and handling prerelease updates
JacksonTheMaster
commented
Aug 6, 2025
JacksonTheMaster
left a comment
Member
Author
There was a problem hiding this comment.
verified update functionality
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.
This PR fixes the updater to properly handle pre-release versions by querying the GitHub /releases endpoint instead of /releases/latest. The change ensures that users with
AllowPrereleaseUpdates= true can detect and update to pre-releases, while those withAllowPrereleaseUpdates= false only get stable releases. It also improves logging to clearly inform users about pre-release availability and adds consistent countdowns for warnings.Changes
Updated
getLatestRelease:Updated
UpdateExecutable: