-
Notifications
You must be signed in to change notification settings - Fork 33
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
latest_stable turns out 2019.1.0f1 - but it's still in beta #357
Comments
Ooops! Yes I found the issue. We fetch those from Unity's own json, but we map them to stable. It will be fixed in coming days. We'll probably add support for the older betas as well. Thanks for reporting! |
Hey @Duobix ! I just took a look at your issue and we will not be addressing it in the upcoming release, ie soon. It would require a fairly large refactor for an issue that we feel is not critical. For future reference, and if anyone wants to address this, the issue comes from the fact that the .json file that we get from the Hub offers several "channels", ie {
"official": [],
"beta": []
} But u3d does not parse those channels: Lines 168 to 174 in aa6b6be
However, as said earlier, the underlying model is simply a dictionary of 'version' => 'url' which does not support the idea of channel introduced in the hub, and would need to be changed. |
@niezbop Would this cause |
@M1kep It doesn't! Note that
So the issue is probably that the central cache hasn't updated yet! However if you run the command I just ran, it will update your local versions cache so you'll be able to download and install whichever version you like! |
Issue Checklist
u3d --help
Issue Description
latest_stable returns a probably wrong version, that is - it's still a beta.
I ran "u3d install latest_stable -p Unity,Android,iOS", and got:
Version 'latest_stable' is 2019.1.0f1.
The latest stable version from what I know is now 2018.3.12f1, even 'u3d available'
returns a link to beta:
"Version 2019.1.0f1: https://beta.unity3d.com/download/5c52223b18d4/"
The text was updated successfully, but these errors were encountered: