-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Unity 2019.4.30f1 #350
Unity 2019.4.30f1 #350
Conversation
@@ -31,7 +31,7 @@ jobs: | |||
unity-installation-path: /Applications/Unity/ | |||
unity-root: /Applications/Unity/Hub/Editor/ | |||
unity-path: Unity.app/Contents/MacOS | |||
- unity-version: 2019.4.21f1 | |||
- unity-version: 2019.4.30f1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need this here if we have it in the matrix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We intend to run CI with multiple Unity versions: 2019, 2020, 2021, and I put it there so I can associate the version changeset with the version number for installing via the hub.
Like .NET does it here.
"com.unity.ide.rider": "1.1.4", | ||
"com.unity.test-framework": "1.1.24", | ||
"com.unity.ide.rider": "1.2.1", | ||
"com.unity.ide.visualstudio": "2.0.11", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should updating unity also add an extra entry com.unity.ide.visualstudio
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair point! A Unity-Package cleanup: #351 has been on my "want to do" for ages!
Added a changelog entry since this could affect how building/testing and packaging is done.