Support ContentPlaceHolder inside CompositeControl templates (deferred master page composition) #3769
tomashercegmain.yml
on: pull_request
Build all projects without errors
5m 55s
JS unit tests
1m 3s
Matrix: Build published projects without warnings
Matrix: .NET unit tests
Matrix: UI tests
Annotations
20 errors and 23 warnings
|
.NET unit tests (macOS-latest)
Process completed with exit code 1.
|
|
SerializeDefaultConfig:
src/Tests/Runtime/ConfigurationSerializationTests.cs#L72
Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeDefaultConfig threw exception:
System.Exception: ConfigurationSerializationTests.SerializeDefaultConfig.json has changed, the actual output differs from the previous accepted output:
diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
index d135300..8463a4f 100644
--- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
+++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
@@ -1192,11 +1192,16 @@
"type": "System.Int32",
"defaultValue": -1
},
+ "MasterPageChildPage": {
+ "type": "DotVVM.Framework.Controls.DotvvmControl, DotVVM.Framework",
+ "isValueInherited": true
+ },
"PathFragment": {
"type": "System.String"
},
"PendingMasterPageCompositions": {
- "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]"
+ "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]",
+ "isValueInherited": true
},
"ReferencedViewModuleInfo": {
"type": "DotVVM.Framework.Binding.ViewModuleReferenceInfo, DotVVM.Framework"
@@ -1206,7 +1211,8 @@
"isValueInherited": true
},
"ResolvedMasterPageCompositionIds": {
- "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]"
+ "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]",
+ "isValueInherited": true
},
"UniqueID": {
"type": "System.String"
Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file
|
|
.NET unit tests (ubuntu-latest)
Process completed with exit code 1.
|
|
SerializeDefaultConfig:
src/Tests/Runtime/ConfigurationSerializationTests.cs#L72
Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeDefaultConfig threw exception:
System.Exception: ConfigurationSerializationTests.SerializeDefaultConfig.json has changed, the actual output differs from the previous accepted output:
diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
index d135300..8463a4f 100644
--- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
+++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
@@ -1192,11 +1192,16 @@
"type": "System.Int32",
"defaultValue": -1
},
+ "MasterPageChildPage": {
+ "type": "DotVVM.Framework.Controls.DotvvmControl, DotVVM.Framework",
+ "isValueInherited": true
+ },
"PathFragment": {
"type": "System.String"
},
"PendingMasterPageCompositions": {
- "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]"
+ "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]",
+ "isValueInherited": true
},
"ReferencedViewModuleInfo": {
"type": "DotVVM.Framework.Binding.ViewModuleReferenceInfo, DotVVM.Framework"
@@ -1206,7 +1211,8 @@
"isValueInherited": true
},
"ResolvedMasterPageCompositionIds": {
- "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]"
+ "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]",
+ "isValueInherited": true
},
"UniqueID": {
"type": "System.String"
Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file
|
|
.NET unit tests (windows-2022)
Process completed with exit code 1.
|
|
SerializeDefaultConfig:
src/Tests/Runtime/ConfigurationSerializationTests.cs#L72
Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeDefaultConfig threw exception:
System.Exception: ConfigurationSerializationTests.SerializeDefaultConfig.json has changed, the actual output differs from the previous accepted output:
diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
index d135300..8463a4f 100644
--- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
+++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
@@ -1192,11 +1192,16 @@
"type": "System.Int32",
"defaultValue": -1
},
+ "MasterPageChildPage": {
+ "type": "DotVVM.Framework.Controls.DotvvmControl, DotVVM.Framework",
+ "isValueInherited": true
+ },
"PathFragment": {
"type": "System.String"
},
"PendingMasterPageCompositions": {
- "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]"
+ "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]",
+ "isValueInherited": true
},
"ReferencedViewModuleInfo": {
"type": "DotVVM.Framework.Binding.ViewModuleReferenceInfo, DotVVM.Framework"
@@ -1206,7 +1211,8 @@
"isValueInherited": true
},
"ResolvedMasterPageCompositionIds": {
- "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]"
+ "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]",
+ "isValueInherited": true
},
"UniqueID": {
"type": "System.String"
Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file
|
|
.NET unit tests (windows-2022)
Process completed with exit code 1.
|
|
SerializeDefaultConfig:
src/Tests/Runtime/ConfigurationSerializationTests.cs#L72
Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeDefaultConfig threw exception:
System.Exception: ConfigurationSerializationTests.SerializeDefaultConfig.json has changed, the actual output differs from the previous accepted output:
diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
index d135300..8463a4f 100644
--- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
+++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json
@@ -1192,11 +1192,16 @@
"type": "System.Int32",
"defaultValue": -1
},
+ "MasterPageChildPage": {
+ "type": "DotVVM.Framework.Controls.DotvvmControl, DotVVM.Framework",
+ "isValueInherited": true
+ },
"PathFragment": {
"type": "System.String"
},
"PendingMasterPageCompositions": {
- "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]"
+ "type": "System.Collections.Generic.List`1[[DotVVM.Framework.Controls.PendingMasterPageComposition, DotVVM.Framework, Version=***, Culture=neutral, PublicKeyToken=23f3607db32275da]]",
+ "isValueInherited": true
},
"ReferencedViewModuleInfo": {
"type": "DotVVM.Framework.Binding.ViewModuleReferenceInfo, DotVVM.Framework"
@@ -1206,7 +1211,8 @@
"isValueInherited": true
},
"ResolvedMasterPageCompositionIds": {
- "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]"
+ "type": "System.Collections.Generic.HashSet`1[[System.String, CoreLibrary]]",
+ "isValueInherited": true
},
"UniqueID": {
"type": "System.String"
Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file
|
|
UI tests (chrome, ubuntu-latest, Production, ExperimentalFeaturesTests)
Process completed with exit code 1.
|
|
UI tests (chrome, ubuntu-latest, Production, ExperimentalFeaturesTests)
Action failed since 4 tests failed.
|
|
UI tests (firefox, ubuntu-latest, Production, Default)
Process completed with exit code 1.
|
|
UI tests (firefox, ubuntu-latest, Production, Default)
Action failed since 4 tests failed.
|
|
UI tests (chrome, ubuntu-latest, Production, Default)
Process completed with exit code 1.
|
|
UI tests (chrome, ubuntu-latest, Production, Default)
Action failed since 4 tests failed.
|
|
UI tests (firefox, ubuntu-latest, Development, ExperimentalFeaturesTests)
Process completed with exit code 1.
|
|
UI tests (firefox, ubuntu-latest, Development, ExperimentalFeaturesTests)
Action failed since 5 tests failed.
|
|
UI tests (firefox, ubuntu-latest, Development, Default, /test-basepath)
Process completed with exit code 1.
|
|
UI tests (firefox, ubuntu-latest, Development, Default, /test-basepath)
Action failed since 6 tests failed.
|
|
UI tests (chrome, windows-2022, Development, Default)
Process completed with exit code 1.
|
|
UI tests (chrome, windows-2022, Development, Default)
Action failed since 6 tests failed.
|
|
JS unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
.NET unit tests (macOS-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 published projects without warnings (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 published projects without warnings (Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 all projects without errors
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, microsoft/setup-msbuild@v1.1, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 all projects without errors
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
|
|
Build all projects without errors
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
|
|
Build all projects without errors
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
|
|
Build all projects without errors
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
|
|
Build all projects without errors
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
|
|
.NET unit tests (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
.NET unit tests (windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
UI tests (chrome, ubuntu-latest, Production, ExperimentalFeaturesTests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
UI tests (chrome, ubuntu-latest, Production, ExperimentalFeaturesTests):
src/Samples/Tests/Tests/Feature/LateContentPlaceHoldersTests.cs#L77
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)
|
|
UI tests (firefox, ubuntu-latest, Production, Default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
UI tests (firefox, ubuntu-latest, Production, Default):
src/Samples/Tests/Tests/Feature/LateContentPlaceHoldersTests.cs#L77
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)
|
|
UI tests (chrome, ubuntu-latest, Production, Default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
UI tests (chrome, ubuntu-latest, Production, Default):
src/Samples/Tests/Tests/Feature/LateContentPlaceHoldersTests.cs#L77
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)
|
|
UI tests (firefox, ubuntu-latest, Development, ExperimentalFeaturesTests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
UI tests (firefox, ubuntu-latest, Development, ExperimentalFeaturesTests):
src/Samples/Tests/Tests/Feature/LateContentPlaceHoldersTests.cs#L77
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)
|
|
UI tests (firefox, ubuntu-latest, Development, Default, /test-basepath)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
UI tests (firefox, ubuntu-latest, Development, Default, /test-basepath):
src/Samples/Tests/Tests/Feature/LateContentPlaceHoldersTests.cs#L77
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)
|
|
UI tests (chrome, windows-2022, Development, Default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-dotnet@v4, actions/setup-node@v3, actions/upload-artifact@v4, microsoft/setup-msbuild@v1.1, nuget/setup-nuget@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
analyzers-tests-net8.0-Debug-Linux
|
13.3 KB |
sha256:3e3c45b60a395428e45fa01a6a61dd3e604ccbbfb80ecff145731c1917b5d69d
|
|
|
analyzers-tests-net8.0-Debug-Windows
|
13.2 KB |
sha256:34addc23251c1352e2cdd8d63eb347af11774c6aae3a0332977f9db77c48c236
|
|
|
analyzers-tests-net8.0-Debug-macOS
|
13.1 KB |
sha256:d7eef2a6b3ba8fcf458d134246835d54d097554d550602c6cd5b5b8c744f56ed
|
|
|
analyzers-tests-net8.0-Release-Linux
|
13.2 KB |
sha256:72eb0f7f9ed0561d6064ef1b829a08aef6e719d958002cb8f577274ae582e42d
|
|
|
analyzers-tests-net8.0-Release-Windows
|
13.1 KB |
sha256:bd1669c12bfa5c46e3a1bdefd383eccd4be281a3a7cbeab9ca82482c0ec16ac3
|
|
|
analyzers-tests-net8.0-Release-macOS
|
13 KB |
sha256:f36decb3bade12be4e1dd0bd6b2a4c2af2f2e8fdb816f8ba429a957720c12703
|
|
|
chrome-tests-Linux-Production-Default
|
164 KB |
sha256:3831cd187e309745221e187074cf5be4601611a9f0a90022c733b3820c780c58
|
|
|
chrome-tests-Linux-Production-ExperimentalFeaturesTests
|
138 KB |
sha256:696ed0a74f03d86cfe2d788e829388c71f52bb1e21c77adb61c0a470dd6ec12e
|
|
|
chrome-tests-Windows-Development-Default
|
209 KB |
sha256:d93319265da1027ce1babb30c88db55c51e70528eb3f19c444ced7c453542953
|
|
|
firefox-tests-Linux-Development-Default
|
222 KB |
sha256:ab3fd4432722b993dafc98910117f2d7d9132b5e68c24f18b411e9ba9d748145
|
|
|
firefox-tests-Linux-Development-ExperimentalFeaturesTests
|
215 KB |
sha256:4fbaa1fa1b6dd68e4cb200d31fbd6207688f9b3fb43bcd5936094dfd8a14f9f9
|
|
|
firefox-tests-Linux-Production-Default
|
190 KB |
sha256:b9a08db66d270f520c49f1045153fc5413422713c7f5944bc91d3d56992700a5
|
|
|
integration-tests-net10.0-Debug-Linux
|
4.41 KB |
sha256:faf53046165b42c8518d8f36015a1bb90b78b5c168eb08ab7f1c0e20c1b1c593
|
|
|
integration-tests-net10.0-Release-Linux
|
4.23 KB |
sha256:8aeec330b9a893bca4f30cd069cec514353b4e1cc01c240bf223771e524967e5
|
|