-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
Update message popping up even though I am on the latest version #445
Comments
I updated by downloading the deb file from the assets section of the Release 1.4 tab, and used the dpkg command to perform the update. I did this because I wasn't sure if the update script would work correctly with my "modified" version of the package. |
I see this same behavior, however I also had a little bit of a strange upgrade. I was following the upgrade instructions from the wiki and blindly posted in end download line that pulled down version 1.0.0. so I went from 1.3.3 to 1.0.0 and then up to 1.4.0 |
I think I messed up something with the version check there ... Will update once I get back home. Sorry for that! |
Well, I did something really stupid this time around. Accidentally labeled the GitHub release v.1.4.0, see that point in front of the 1. That is what threw everything off. Good thing is, that this is now fixed, just needed to update the GitHub Release name, no update needed for OctoDash. Thanks for pointing this out! |
Describe the bug
The update notification message is popping up when I am using the newly released 1.4.0 version.
Expected behavior
Since I am current, I wouldn't expect to see this notification.
Screenshots
Additional context
This may be a special case, as I updated over top of the modified version you posted here when you were working on a fix for the saving of settings black screen of death.
The text was updated successfully, but these errors were encountered: