Skip to content

Merge branch 'fork/ctzcs/fix-bug' #167

Merge branch 'fork/ctzcs/fix-bug'

Merge branch 'fork/ctzcs/fix-bug' #167

Triggered via push March 23, 2026 01:01
Status Success
Total duration 8m 47s
Artifacts 9
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

90 errors and 20 warnings
Build-StandaloneWindows-2020.3.48f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2020.3.48f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-StandaloneWindows-2020.3.48f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2020.3.48f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2020.3.48f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2020.3.48f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2020.3.48f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2020.3.48f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2020.3.48f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2020.3.48f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2021.3.45f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2021.3.45f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-StandaloneWindows-2021.3.45f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2021.3.45f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2021.3.45f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2021.3.45f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2021.3.45f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2021.3.45f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2021.3.45f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2021.3.45f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2022.3.43f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2022.3.43f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-StandaloneWindows-2022.3.43f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2022.3.43f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2022.3.43f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2022.3.43f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2022.3.43f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2022.3.43f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2022.3.43f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2022.3.43f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.0.64f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.0.64f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-StandaloneWindows-6000.0.64f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.0.64f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.0.64f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.0.64f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.0.64f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.0.64f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.0.64f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.0.64f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-StandaloneWindows-2019.4.40f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2019.4.40f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2019.4.40f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2019.4.40f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-2019.4.40f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.3.2f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.3.2f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-StandaloneWindows-6000.3.2f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.3.2f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.3.2f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.3.2f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.3.2f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.3.2f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-6000.3.2f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-StandaloneWindows-6000.3.2f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried loading an aseprite file "NuclearBlaze_by_deepnight.aseprite", but the aseprite importer is not installed or below version 1.0.0. Add: com.unity.2d.aseprite. Requires Unity 2021.3.15 or newer
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-WebGL-6000.0.23f1
AssetImporter is referencing an asset from the previous import. This should not happen.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Tried to build the internal icons "Internal_Icons", But the internal icons was not assigned in Unity's project settings. You can add the texture by going to Edit > Project Settings > LDtk To Unity
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-2019.3.15f1
<color=#997A00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2020.3.48f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-2020.3.48f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-StandaloneWindows-2021.3.45f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-2021.3.45f1
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
Build-StandaloneWindows-2021.3.45f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-StandaloneWindows-2022.3.43f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-2022.3.43f1
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
Build-StandaloneWindows-2022.3.43f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-StandaloneWindows-6000.0.64f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-6000.0.64f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-StandaloneWindows-2019.4.40f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-2019.4.40f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-StandaloneWindows-6000.3.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.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-6000.3.2f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-StandaloneWindows-2019.3.15f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-StandaloneWindows-2019.3.15f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-WebGL-6000.0.23f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-WebGL-6000.0.23f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build-WebGL-2019.3.15f1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.1.4, actions/upload-artifact@v4.3.3, game-ci/unity-builder@v4.3.0. 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/
Build-WebGL-2019.3.15f1
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

Artifacts

Produced during runtime
Name Size Digest
Build-StandaloneWindows-2019.3.15f1
18.2 MB
sha256:5ee1b16c294011c7f650574e6828d007d8e94ff89f71e58d29e33f0dd7b177fc
Build-StandaloneWindows-2019.4.40f1
18.3 MB
sha256:bcfe8658b48e6e6e69bd2e3e94bd11b593eb1a88297bc38390376cc98c5873dd
Build-StandaloneWindows-2020.3.48f1
20 MB
sha256:e5b8942858b098372d4625f0f9a562716fc9735109d2739428c28b0698fb8840
Build-StandaloneWindows-2021.3.45f1
22.3 MB
sha256:1ad56019f6d1b40744e81e88d6f93194eb1e543adbbb1706a391f5e005c31bbc
Build-StandaloneWindows-2022.3.43f1
22.2 MB
sha256:2d679e5a4efb73f87316177fce76aa3c3ace0b9d3499074fd389058af4d33fbe
Build-StandaloneWindows-6000.0.64f1
25.9 MB
sha256:0d692fabcffb83bd51d9c868a6a2eef11e7c4cb6ca7f51592736e95409d55ec8
Build-StandaloneWindows-6000.3.2f1
27.4 MB
sha256:d0a8018b2d7f6c90f49f7db1c14d5cbf6c386759b83ec7980f6f6db61c405939
Build-WebGL-2019.3.15f1
3.62 MB
sha256:1ea5ee63258aa394ee6e20273f38e962d34d015a17cb6ef0592cd93cd12ec03f
Build-WebGL-6000.0.23f1
3.92 MB
sha256:6a3c81997320c5484bf6922242a8178c842ffd8e8825eb891bb84b7270b24cb3