chore(project): upgrade to Unity 2021.3.34f1 #168
jonisavoAnnotations
14 errors and 16 warnings
|
Test on 2023.2.27f1 (StandaloneLinux64)
The process '/usr/bin/docker' failed with exit code 125
|
|
Test on 2023.2.27f1 (StandaloneWindows64)
The process '/usr/bin/docker' failed with exit code 125
|
|
Test on 2022.3.18f1 (StandaloneWindows64)
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.
|
|
Test on 2022.3.18f1 (StandaloneWindows64)
The process '/usr/bin/docker' failed with exit code 1
|
|
Test on 2021.3.34f1 (StandaloneLinux64)
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.
|
|
Test on 2021.3.34f1 (StandaloneLinux64)
The process '/usr/bin/docker' failed with exit code 1
|
|
Test on 2022.3.18f1 (StandaloneLinux64)
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.
|
|
Test on 2022.3.18f1 (StandaloneLinux64)
The process '/usr/bin/docker' failed with exit code 1
|
|
Test on 2020.3.48f1 (StandaloneWindows64)
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.
|
|
Test on 2020.3.48f1 (StandaloneWindows64)
The process '/usr/bin/docker' failed with exit code 1
|
|
Test on 2021.3.34f1 (StandaloneWindows64)
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.
|
|
Test on 2021.3.34f1 (StandaloneWindows64)
The process '/usr/bin/docker' failed with exit code 1
|
|
Test on 2020.3.48f1 (StandaloneLinux64)
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.
|
|
Test on 2020.3.48f1 (StandaloneLinux64)
The process '/usr/bin/docker' failed with exit code 1
|
|
Test on 2023.2.27f1 (StandaloneLinux64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2023.2.27f1 (StandaloneLinux64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2023.2.27f1 (StandaloneWindows64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2023.2.27f1 (StandaloneWindows64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2022.3.18f1 (StandaloneWindows64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2022.3.18f1 (StandaloneWindows64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2021.3.34f1 (StandaloneLinux64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2021.3.34f1 (StandaloneLinux64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2022.3.18f1 (StandaloneLinux64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2022.3.18f1 (StandaloneLinux64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2020.3.48f1 (StandaloneWindows64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2020.3.48f1 (StandaloneWindows64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2021.3.34f1 (StandaloneWindows64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2021.3.34f1 (StandaloneWindows64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|
|
Test on 2020.3.48f1 (StandaloneLinux64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test on 2020.3.48f1 (StandaloneLinux64)
No files were found with the provided path: artifacts. No artifacts will be uploaded.
|