Skip to content

feat: read dependency paths from files passed to --dependency-file #93

feat: read dependency paths from files passed to --dependency-file

feat: read dependency paths from files passed to --dependency-file #93

Triggered via push April 8, 2026 22:59
Status Failure
Total duration 9m 39s
Artifacts

build.yml

on: push
Matrix: Get reference assemblies from Unity
Matrix: build-patchers
Build patcher archive
0s
Build patcher archive
Build CLI .nupkg
0s
Build CLI .nupkg
Build NetcodePatcher.MSBuild
0s
Build NetcodePatcher.MSBuild
Matrix: build-cli-binaries
Fit to window
Zoom out
Zoom in

Annotations

77 errors and 189 warnings
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Build failed with exit code 1
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
There was an error while trying to activate the Unity license.
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Build failed with exit code 1
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
There was an error while trying to activate the Unity license.
Get reference assemblies from Unity (2022.3.9, 1.12.2, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.12.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.8.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.8.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.12.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.13.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.13.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.5.2, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.7.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.8.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.12.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.14.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.7.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.8.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.12.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.8.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.12.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.12.2, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.6.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.12.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.14.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.8.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.6.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.12.2, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.5.2, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.13.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.14.0, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.14.0, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.14.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.14.1, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.14.0, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.14.0, 1.0.0)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.14.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.13.1, 1.0.0)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.13.1, 2.2.1)
The strategy configuration was canceled because "grab-reference-assemblies._2022_3_62_1_12_0_1_0_0" failed
Get reference assemblies from Unity (2022.3.62, 1.13.1, 2.2.1)
The operation was canceled.
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.62, 1.13.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.62, 1.12.0, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.5.2, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.7.0, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.5.2, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.8.1, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.7.1, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.12.2, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.6.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.13.1, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.7.1, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.62, 1.7.1, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.6.0, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.12.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.8.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.7.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.14.1, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.13.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.7.0, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Activation failed, attempting retry #5
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Activation failed, attempting retry #4
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Activation failed, attempting retry #3
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Activation failed, attempting retry #2
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Activation failed, attempting retry #1
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.9, 1.14.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.14.0, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.14.0, 2.2.1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.14.1, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.14.1, 1.0.0)
M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt
Get reference assemblies from Unity (2022.3.62, 1.14.1, 1.0.0)
Changes were made to the following files and folders:
Get reference assemblies from Unity (2022.3.62, 1.14.1, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.14.0, 1.0.0)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Get reference assemblies from Unity (2022.3.62, 1.14.0, 1.0.0)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Get reference assemblies from Unity (2022.3.62, 1.13.1, 2.2.1)
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, game-ci/unity-builder@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/