Skip to content

feat: net10

feat: net10 #1498

Triggered via push April 26, 2026 15:37
Status Failure
Total duration 2m 20s
Artifacts 1

dotnet-core.yml

on: push
Build - Windows .NET Framework Zip
39s
Build - Windows .NET Framework Zip
Run Tests & Publish Dev Package
2m 15s
Run Tests & Publish Dev Package
Matrix: Build Single-File Artifact
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 42 warnings
Build Single-File Artifact (linux-arm64, Cpp2IL)
Process completed with exit code 1.
Build Single-File Artifact (linux-arm64, Cpp2IL)
Assets file '/home/runner/work/Cpp2IL/Cpp2IL/Cpp2IL/obj/project.assets.json' doesn't have a target for 'net9.0'. Ensure that restore has run and that you have included 'net9.0' in the TargetFrameworks for your project.
Build Single-File Artifact (win-x64, Cpp2IL)
The strategy configuration was canceled because "release-net9.linux-arm64_Cpp2IL" failed
Build Single-File Artifact (win-x64, Cpp2IL)
Process completed with exit code 1.
Build Single-File Artifact (win-x64, Cpp2IL)
Assets file '/home/runner/work/Cpp2IL/Cpp2IL/Cpp2IL/obj/project.assets.json' doesn't have a target for 'net9.0'. Ensure that restore has run and that you have included 'net9.0' in the TargetFrameworks for your project.
Build Single-File Artifact (osx-arm64, Cpp2IL)
The strategy configuration was canceled because "release-net9.linux-arm64_Cpp2IL" failed
Build Single-File Artifact (osx-arm64, Cpp2IL)
Process completed with exit code 1.
Build Single-File Artifact (osx-arm64, Cpp2IL)
Assets file '/home/runner/work/Cpp2IL/Cpp2IL/Cpp2IL/obj/project.assets.json' doesn't have a target for 'net9.0'. Ensure that restore has run and that you have included 'net9.0' in the TargetFrameworks for your project.
Build Single-File Artifact (win-arm64, Cpp2IL)
The strategy configuration was canceled because "release-net9.linux-arm64_Cpp2IL" failed
Build Single-File Artifact (win-arm64, Cpp2IL)
Process completed with exit code 1.
Build Single-File Artifact (win-arm64, Cpp2IL)
Assets file '/home/runner/work/Cpp2IL/Cpp2IL/Cpp2IL/obj/project.assets.json' doesn't have a target for 'net9.0'. Ensure that restore has run and that you have included 'net9.0' in the TargetFrameworks for your project.
Build Single-File Artifact (osx-x64, Cpp2IL)
The strategy configuration was canceled because "release-net9.linux-arm64_Cpp2IL" failed
Build Single-File Artifact (osx-x64, Cpp2IL)
The operation was canceled.
Build Single-File Artifact (linux-x64, Cpp2IL)
The strategy configuration was canceled because "release-net9.linux-arm64_Cpp2IL" failed
Build Single-File Artifact (linux-x64, Cpp2IL)
The operation was canceled.
Run Tests & Publish Dev Package
Process completed with exit code 1.
Build Single-File Artifact (linux-arm64, Cpp2IL)
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Build Single-File Artifact (linux-arm64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (linux-arm64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (win-x64, Cpp2IL)
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Build Single-File Artifact (win-x64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (win-x64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (osx-arm64, Cpp2IL)
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Build Single-File Artifact (osx-arm64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (osx-arm64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (win-arm64, Cpp2IL)
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Build Single-File Artifact (win-arm64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (win-arm64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (osx-x64, Cpp2IL)
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Build Single-File Artifact (osx-x64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (osx-x64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (linux-x64, Cpp2IL)
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Build Single-File Artifact (linux-x64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Single-File Artifact (linux-x64, Cpp2IL)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build - Windows .NET Framework Zip
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/setup-dotnet@v4.1.0, 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/
Build - Windows .NET Framework Zip: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L13
Non-nullable field 'methods' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build - Windows .NET Framework Zip: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L12
Non-nullable field 'properties' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build - Windows .NET Framework Zip: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L11
Non-nullable field 'events' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build - Windows .NET Framework Zip: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L10
Non-nullable field 'string' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build - Windows .NET Framework Zip: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L9
Non-nullable field 'stringLiteralData' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build - Windows .NET Framework Zip: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L8
Non-nullable field 'stringLiteral' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Build - Windows .NET Framework Zip: LibCpp2IL/LibCpp2IlUtils.cs#L348
Possible null reference argument for parameter 'forWhat' in 'Il2CppTypeReflectionData LibCpp2ILUtils.GetTypeReflectionData(Il2CppType forWhat)'.
Build - Windows .NET Framework Zip: LibCpp2IL/LibCpp2IlUtils.cs#L302
Dereference of a possibly null reference.
Build - Windows .NET Framework Zip: LibCpp2IL/LibCpp2IlUtils.cs#L145
Possible null reference argument for parameter 'type' in 'string LibCpp2ILUtils.GetTypeName(Il2CppMetadata metadata, Il2CppBinary cppAssembly, Il2CppType type, bool fullName = false)'.
Build - Windows .NET Framework Zip: LibCpp2IL/LibCpp2IlUtils.cs#L130
Dereference of a possibly null reference.
Run Tests & Publish Dev Package
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/github-script@v7, actions/setup-dotnet@v4.1.0. 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/
Run Tests & Publish Dev Package: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L13
Non-nullable field 'methods' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Run Tests & Publish Dev Package: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L12
Non-nullable field 'properties' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Run Tests & Publish Dev Package: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L11
Non-nullable field 'events' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Run Tests & Publish Dev Package: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L10
Non-nullable field 'string' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Run Tests & Publish Dev Package: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L9
Non-nullable field 'stringLiteralData' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Run Tests & Publish Dev Package: LibCpp2IL/Metadata/Il2CppGlobalMetadataHeader.cs#L8
Non-nullable field 'stringLiteral' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Run Tests & Publish Dev Package: LibCpp2IL/LibCpp2IlUtils.cs#L348
Possible null reference argument for parameter 'forWhat' in 'Il2CppTypeReflectionData LibCpp2ILUtils.GetTypeReflectionData(Il2CppType forWhat)'.
Run Tests & Publish Dev Package: LibCpp2IL/LibCpp2IlUtils.cs#L302
Dereference of a possibly null reference.
Run Tests & Publish Dev Package: LibCpp2IL/LibCpp2IlUtils.cs#L145
Possible null reference argument for parameter 'type' in 'string LibCpp2ILUtils.GetTypeName(Il2CppMetadata metadata, Il2CppBinary cppAssembly, Il2CppType type, bool fullName = false)'.
Run Tests & Publish Dev Package: LibCpp2IL/LibCpp2IlUtils.cs#L130
Dereference of a possibly null reference.
Run Tests & Publish Dev Package
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run Tests & Publish Dev Package
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Artifacts

Produced during runtime
Name Size Digest
Cpp2IL-Netframework472-Windows
2.71 MB
sha256:f350ad1990f0860e60c33b9a70b2d80cba92c7e3c33ebaecc2b12b15a617421a