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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

Activation failed, attempting retry #2

Activation failed, attempting retry #1

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

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/upload-artifact@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/

M UnityProject/Packages/manifest.json M UnityProject/ProjectSettings/ProjectVersion.txt

Changes were made to the following files and folders:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'NetworkObject.m_IsPrefab' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'NetworkObject.m_IsPrefab' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'NetworkObject.m_IsPrefab' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'NetworkObject.m_IsPrefab' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'NetworkObject.m_IsPrefab' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'SinglePlayerTransport.m_Initialized' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

'NetworkDriver.RemoteEndPoint(NetworkConnection)' is obsolete: 'RemoteEndPoint has been renamed to GetRemoteEndpoint. (UnityUpgradable) -> GetRemoteEndpoint(*)'

The field 'NetworkObject.m_IsPrefab' is never used

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'NetworkObject.m_IsPrefab' is never used

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'NetworkObject.m_IsPrefab' is never used

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'NetworkObject.m_IsPrefab' is never used

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

'NetworkDriver.RemoteEndPoint(NetworkConnection)' is obsolete: 'RemoteEndPoint has been renamed to GetRemoteEndpoint. (UnityUpgradable) -> GetRemoteEndpoint(*)'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

'NetworkDriver.RemoteEndPoint(NetworkConnection)' is obsolete: 'RemoteEndPoint has been renamed to GetRemoteEndpoint. (UnityUpgradable) -> GetRemoteEndpoint(*)'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'NetworkObject.m_IsPrefab' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'SinglePlayerTransport.m_Initialized' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

The field 'SinglePlayerTransport.m_Initialized' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SinglePlayerTransport.m_Initialized' is never used

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SinglePlayerTransport.m_Initialized' is never used

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

The field 'SceneEventData.m_SceneNetworkObjectDataOffsets' is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/

The field 'NetworkManagerEditor.m_MaxObjectUpdatesPerTickProperty' is never used

The field 'UnityTransportEditor.m_AllowIncomingConnections' is never used

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Non-nullable field 'm_AssemblyResolver' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).

Nullability of return type doesn't match overridden member (possibly because of nullability attributes).