[TechoMan]

This PR shouldn't break any of existing features.

Example of version that is considered Invalid: 2019.1.0a10
Example of download link: https://unity3d.com/unity/alpha/2019.1.0a10
Example of exception that this PR should fix:

Exception setting "Version": "Cannot convert value "2019.1.0a10" to type "UnityVersion". Error: "Invalid unity version: 2019.1.0a10""
At C:\Users\Artem\Documents\WindowsPowerShell\Modules\UnitySetup\4.0.97\UnitySetup.psm1:128 char:9
+         $this.Version = $fileVersion
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], SetValueInvocationException
    + FullyQualifiedErrorId : ExceptionWhenSetting

[Josh Wittner (jwittner)]

Awesome change! Thanks for pushing for more versions to be available through UnitySetup! =)

This change doesn't seem to be enough as it fails to find any components for the version you mention. There are several places that will need the 'a' added to 'fbp', and it looks like the link to the core component for alpha versions doesn't match the UnitySetup64-$version.exe naming scheme of the other download types.

[Stephen Hodgson (StephenHodgson)]

Any update to this?

[Stephen Hodgson (StephenHodgson)]

We can probably close this now, correct?

[Stephen Hodgson (StephenHodgson)]

Josh Wittner (@jwittner) I think we can close this, I'm pretty sure the changes were superseded by #170