-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Popup with showing new version, but this is the newest version #289
Comments
Whoops! How did the wrong version number end up in the Windows build? Are the other builds with correct version number? |
@achimmihca linux build is also effected |
The version was set already in January Weird. |
The new GitHub Actions build artifacts have the correct version number. Will check this when creating the next release. |
Indeed, the new builds have again the wrong version number. It shows 0.4.0 but VERSION.txt already has 0.5.0. Furthermore, the git commit hash is missing now because of a Git security update that prevents running Git commands as before.
Guess I have to setup docker to debug this. Sucks... |
I debugged the issue, not via docker, but via GitHub Actions and Looks like the Unity API returns an old value for Anyway, it works when fetching the value directly from the file instead of using Unity's API. The commit hash can also be read from a file inside Will open a PR soon. |
Issue type: Bug report
Actual behaviour
On Windows 10 64bit with the current version:
Expected behaviour
Popup should not be shown currently and version number in left bottom corner should show the right version
Steps to reproduce
the commit hash seems to be right
The text was updated successfully, but these errors were encountered: