fix(common): add nil safety and normalize version comparison in CheckVersionUpdate - #599
Open
Tyagiquamar wants to merge 2 commits into
Open
fix(common): add nil safety and normalize version comparison in CheckVersionUpdate#599Tyagiquamar wants to merge 2 commits into
Tyagiquamar wants to merge 2 commits into
Conversation
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
2 participants
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.
\CheckVersionUpdate\ in \common/common.go\ could previously panic if
es\ or
es.TagName\ was nil (e.g. from network or rate-limiting error paths). Additionally, the version tag checks contained nested logic that did not consistently handle \�-prefix version strings across binary build flags and GitHub release tag names.
This fix:
es == nil || res.TagName == nil\ safety checks before dereferencing release tag names.
Fixes #313.