Rename Cloud Runner to Orchestrator (#775) #1
kitlithAnnotations
192 errors and 286 warnings
|
StandaloneWindows64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2021.3.32f1
Build failed with exit code 1
|
|
WebGL on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2021.3.32f1
Build failed with exit code 1
|
|
WebGL on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2021.3.32f1
Build failed with exit code 1
|
|
WebGL on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneOSX on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneOSX on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneOSX on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneOSX on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneOSX on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneOSX on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneOSX on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneOSX on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneOSX on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneOSX on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2023.2.2f1
Build failed with exit code 1
|
|
iOS on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2023.2.2f1
Build failed with exit code 1
|
|
iOS on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2023.2.2f1
Build failed with exit code 1
|
|
iOS on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 6000.0.36f1
Build failed with exit code 1
|
|
WebGL on 6000.0.36f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 6000.0.36f1
Build failed with exit code 1
|
|
WebGL on 6000.0.36f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 6000.0.36f1
Build failed with exit code 1
|
|
WebGL on 6000.0.36f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2022.3.13f1
Build failed with exit code 1
|
|
Android on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2022.3.13f1
Build failed with exit code 1
|
|
Android on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2022.3.13f1
Build failed with exit code 1
|
|
Android on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2022.3.13f1
Build failed with exit code 1
|
|
iOS on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2022.3.13f1
Build failed with exit code 1
|
|
iOS on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2022.3.13f1
Build failed with exit code 1
|
|
iOS on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2021.3.32f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2022.3.13f1
Build failed with exit code 1
|
|
StandaloneWindows64 on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2023.2.2f1
Build failed with exit code 1
|
|
WebGL on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2023.2.2f1
Build failed with exit code 1
|
|
WebGL on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2023.2.2f1
Build failed with exit code 1
|
|
WebGL on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneLinux64 on 2023.2.2f1
Build failed with exit code 1
|
|
StandaloneLinux64 on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2021.3.32f1
Build failed with exit code 1
|
|
iOS on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2021.3.32f1
Build failed with exit code 1
|
|
iOS on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
iOS on 2021.3.32f1
Build failed with exit code 1
|
|
iOS on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2023.2.2f1
Build failed with exit code 1
|
|
Android on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2023.2.2f1
Build failed with exit code 1
|
|
Android on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2023.2.2f1
Build failed with exit code 1
|
|
Android on 2023.2.2f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Build failed with exit code 1
|
|
WebGL on 6000.0.36f1 (via Build Profile)
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Build failed with exit code 1
|
|
WebGL on 6000.0.36f1 (via Build Profile)
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Build failed with exit code 1
|
|
WebGL on 6000.0.36f1 (via Build Profile)
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2022.3.13f1
Build failed with exit code 1
|
|
WebGL on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2022.3.13f1
Build failed with exit code 1
|
|
WebGL on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
WebGL on 2022.3.13f1
Build failed with exit code 1
|
|
WebGL on 2022.3.13f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2021.3.32f1
Build failed with exit code 1
|
|
Android on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2021.3.32f1
Build failed with exit code 1
|
|
Android on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
Android on 2021.3.32f1
Build failed with exit code 1
|
|
Android on 2021.3.32f1
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. See more info at https://game.ci/docs/github/activation
|
|
StandaloneWindows64 on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneWindows64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneWindows64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneWindows64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
WebGL on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
WebGL on 2021.3.32f1
Changes were made to the following files and folders:
|
|
WebGL on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
WebGL on 2021.3.32f1
Changes were made to the following files and folders:
|
|
WebGL on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
WebGL on 2021.3.32f1
Changes were made to the following files and folders:
|
|
WebGL on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneOSX on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneOSX on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneOSX on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneOSX on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneOSX on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneWindows64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneOSX on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneOSX on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneOSX on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneOSX on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneOSX on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneOSX on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneOSX on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneOSX on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneOSX on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneOSX on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneOSX on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
iOS on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
iOS on 2023.2.2f1
Changes were made to the following files and folders:
|
|
iOS on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
iOS on 2023.2.2f1
Changes were made to the following files and folders:
|
|
iOS on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
iOS on 2023.2.2f1
Changes were made to the following files and folders:
|
|
iOS on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 6000.0.36f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
WebGL on 6000.0.36f1
?? dist/unity-config/services-config.json
|
|
WebGL on 6000.0.36f1
Changes were made to the following files and folders:
|
|
WebGL on 6000.0.36f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 6000.0.36f1
?? dist/unity-config/services-config.json
|
|
WebGL on 6000.0.36f1
Changes were made to the following files and folders:
|
|
WebGL on 6000.0.36f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 6000.0.36f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Android on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
Android on 2022.3.13f1
Changes were made to the following files and folders:
|
|
Android on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
Android on 2022.3.13f1
Changes were made to the following files and folders:
|
|
Android on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
Android on 2022.3.13f1
Changes were made to the following files and folders:
|
|
Android on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
iOS on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
iOS on 2022.3.13f1
Changes were made to the following files and folders:
|
|
iOS on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
iOS on 2022.3.13f1
Changes were made to the following files and folders:
|
|
iOS on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
iOS on 2022.3.13f1
Changes were made to the following files and folders:
|
|
iOS on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2021.3.32f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneWindows64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2023.2.2f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneWindows64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2022.3.13f1
?? dist/unity-config/services-config.json
|
|
StandaloneWindows64 on 2022.3.13f1
Changes were made to the following files and folders:
|
|
StandaloneWindows64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneWindows64 on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
WebGL on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
WebGL on 2023.2.2f1
Changes were made to the following files and folders:
|
|
WebGL on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
WebGL on 2023.2.2f1
Changes were made to the following files and folders:
|
|
WebGL on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
WebGL on 2023.2.2f1
Changes were made to the following files and folders:
|
|
WebGL on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
StandaloneLinux64 on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
StandaloneLinux64 on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
StandaloneLinux64 on 2023.2.2f1
Changes were made to the following files and folders:
|
|
StandaloneLinux64 on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
iOS on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
iOS on 2021.3.32f1
Changes were made to the following files and folders:
|
|
iOS on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
iOS on 2021.3.32f1
Changes were made to the following files and folders:
|
|
iOS on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
iOS on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
iOS on 2021.3.32f1
Changes were made to the following files and folders:
|
|
iOS on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2023.2.2f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Android on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
Android on 2023.2.2f1
Changes were made to the following files and folders:
|
|
Android on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
Android on 2023.2.2f1
Changes were made to the following files and folders:
|
|
Android on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2023.2.2f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
Android on 2023.2.2f1
Changes were made to the following files and folders:
|
|
Android on 2023.2.2f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
WebGL on 6000.0.36f1 (via Build Profile)
?? dist/unity-config/services-config.json
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Changes were made to the following files and folders:
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 6000.0.36f1 (via Build Profile)
?? dist/unity-config/services-config.json
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Changes were made to the following files and folders:
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 6000.0.36f1 (via Build Profile)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2022.3.13f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
WebGL on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
WebGL on 2022.3.13f1
Changes were made to the following files and folders:
|
|
WebGL on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
WebGL on 2022.3.13f1
Changes were made to the following files and folders:
|
|
WebGL on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
WebGL on 2022.3.13f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
WebGL on 2022.3.13f1
Changes were made to the following files and folders:
|
|
WebGL on 2022.3.13f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2021.3.32f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Android on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
Android on 2021.3.32f1
Changes were made to the following files and folders:
|
|
Android on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
?? dist/unity-config/services-config.json
|
|
Android on 2021.3.32f1
Changes were made to the following files and folders:
|
|
Android on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
Android on 2021.3.32f1
M test-project/ProjectSettings/ProjectSettings.asset
D test-project/ProjectSettings/ProjectSettingsIl2cpp.asset
|
|
Android on 2021.3.32f1
Changes were made to the following files and folders:
|
|
Android on 2021.3.32f1
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|