Skip to content

Logto

Logto #2804

Triggered via pull request April 15, 2026 10:31
Status Failure
Total duration 49m 33s
Artifacts 262

dotnet-ci.yml

on: pull_request
Matrix: run-tests / test
Matrix: build
package  /  package
package / package
publish-coverage  /  publish-coverage
publish-coverage / publish-coverage
publish-azure-artifacts
publish-azure-artifacts
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 145 warnings
run-tests / Hosting.MongoDB.Extensions.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/mongodb-ext/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.MongoDB.Extensions -WaitForResources mongo,dbgate,mongo-named' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.csproj (in 539 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 540 ms). CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.MongoDB.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.MongoDB.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.dll CommunityToolkit.Aspire.Hosting.MongoDB.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.dll Successfully created package '/tmp/ct-polyglot-9e0b31d021e5494eb04cc0b523eab5ea/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json Error: Restore failed: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json ❌ Failed to prepare AppHost server. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | �[31;
run-tests / Hosting.Redis.Extensions.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.Redis.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Redis.Extensions.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/redis-ext/CommunityToolkit.Aspire.Hosting.Redis.Extensions.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Redis.Extensions/CommunityToolkit.Aspire.Hosting.Redis.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.Redis.Extensions -WaitForResources cache,cache-dbgate -WaitStatus up' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 523 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Redis.Extensions/CommunityToolkit.Aspire.Hosting.Redis.Extensions.csproj (in 523 ms). CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Redis.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Redis.Extensions/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Redis.Extensions.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Redis.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Redis.Extensions/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Redis.Extensions.dll CommunityToolkit.Aspire.Hosting.Redis.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Redis.Extensions/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Redis.Extensions.dll Successfully created package '/tmp/ct-polyglot-07b9f195263b467ab691f54f0d13a7d4/CommunityToolkit.Aspire.Hosting.Redis.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json Error: Restore failed: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json ❌ Failed to prepare AppHost server. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~
run-tests / GoFeatureFlag.Tests-windows-latest
The process 'C:\Program Files\PowerShell\7\pwsh.exe' failed with exit code 1
run-tests / Hosting.McpInspector.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.McpInspector.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.McpInspector.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/mcp-inspector/CommunityToolkit.Aspire.Hosting.McpInspector.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.McpInspector/CommunityToolkit.Aspire.Hosting.McpInspector.csproj -PackageName CommunityToolkit.Aspire.Hosting.McpInspector -WaitForResources inspector-default,inspector-configured,inspector-yarn,inspector-pnpm,inspector-bun -RequiredCommands yarn,pnpm,bun' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.McpInspector/CommunityToolkit.Aspire.Hosting.McpInspector.csproj (in 490 ms). CommunityToolkit.Aspire.Hosting.McpInspector -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.McpInspector/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.McpInspector.dll CommunityToolkit.Aspire.Hosting.McpInspector -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.McpInspector/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.McpInspector.dll CommunityToolkit.Aspire.Hosting.McpInspector -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.McpInspector/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.McpInspector.dll Successfully created package '/tmp/ct-polyglot-741e2e4396de4fe7a64476e5d30b3c67/CommunityToolkit.Aspire.Hosting.McpInspector.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 3s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. { "appHostPath": "/home/runner/work/Aspire/Aspire/examples/mcp-inspector/CommunityToolkit.Aspire.Hosting.McpInspector.AppHost.TypeScript/apphost.ts", "appHostPid": 5811, "cliPid": 5755, "dashboardUrl": "https://localhost:29750/login?t=dc914760fadbed663d91cff47aaeec7f", "logFile": "/home/runner/.aspire/logs/cli_20260415T103353845_detach-child_20664eab8bf74c2089cfc728de2ba822.log" } Waiting for resource 'inspector-default' to be healthy... ✔ Resource 'inspector-default' is healthy. (5.8s) Waiting for resource 'inspector-configured' to be healthy... ❌ Resource 'inspector-configured' entered a failed state: Stopped waiting for resource 'inspector-configured' to become healthy because it failed to start.. 📦 Found running AppHost: apphost.ts 🛑 Sending stop signal... Stopping Aspire apphost... ✔ Apphost stopped successfully. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Starting Aspire apphost in the background... DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 18: aspire wait inspector-configured | �[31
run-tests / Hosting.MySql.Extensions.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.MySql.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.MySql.Extensions.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/mysql-ext/CommunityToolkit.Aspire.Hosting.MySql.Extensions.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/CommunityToolkit.Aspire.Hosting.MySql.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.MySql.Extensions -WaitForResources mysql,mysql-adminer,mysql-dbgate' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 964 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 966 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/CommunityToolkit.Aspire.Hosting.MySql.Extensions.csproj (in 965 ms). CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.MySql.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.MySql.Extensions.dll CommunityToolkit.Aspire.Hosting.MySql.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.MySql.Extensions.dll CommunityToolkit.Aspire.Hosting.MySql.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.MySql.Extensions.dll Successfully created package '/tmp/ct-polyglot-a4d2a9d125354155b47e9e488867bb71/CommunityToolkit.Aspire.Hosting.MySql.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 3s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.Adminer with version (>= 13.2.1-polyglot.local) - Found 160 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-
run-tests / Hosting.Solr.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.Solr.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Solr.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/solr/CommunityToolkit.Aspire.Hosting.Solr.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Solr/CommunityToolkit.Aspire.Hosting.Solr.csproj -PackageName CommunityToolkit.Aspire.Hosting.Solr -WaitForResources solr,solr-bind' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Solr/CommunityToolkit.Aspire.Hosting.Solr.csproj (in 448 ms). CommunityToolkit.Aspire.Hosting.Solr -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Solr/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Solr.dll CommunityToolkit.Aspire.Hosting.Solr -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Solr/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Solr.dll CommunityToolkit.Aspire.Hosting.Solr -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Solr/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Solr.dll Successfully created package '/tmp/ct-polyglot-1c778f0437c64699ae07dde628504b64/CommunityToolkit.Aspire.Hosting.Solr.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. { "appHostPath": "/home/runner/work/Aspire/Aspire/examples/solr/CommunityToolkit.Aspire.Hosting.Solr.AppHost.TypeScript/apphost.ts", "appHostPid": 6995, "cliPid": 6924, "dashboardUrl": "https://localhost:29750/login?t=bb100a88838cd4c92776a07befb1e629", "logFile": "/home/runner/.aspire/logs/cli_20260415T103420537_detach-child_ec3d835511294f64a241f413c429a637.log" } Waiting for resource 'solr' to be healthy... ✔ Resource 'solr' is healthy. (9.0s) Waiting for resource 'solr-bind' to be healthy... ❌ Resource 'solr-bind' entered a failed state: Stopped waiting for resource 'solr-bind' to become healthy because it failed to start.. 📦 Found running AppHost: apphost.ts 🛑 Sending stop signal... Stopping Aspire apphost... ✔ Apphost stopped successfully. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Starting Aspire apphost in the background... DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 18: aspire wait solr-bind --status healthy | --apphost | /home/runner/work/Aspire/Aspire/examples/solr/CommunityToolkit.Aspire.Hosting.Solr.AppHost.TypeScript/apphost.ts --timeout 180
run-tests / Hosting.Ngrok.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.Ngrok.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Ngrok.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/ngrok/CommunityToolkit.Aspire.Hosting.Ngrok.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Ngrok/CommunityToolkit.Aspire.Hosting.Ngrok.csproj -PackageName CommunityToolkit.Aspire.Hosting.Ngrok -WaitForResources upstream,ngrok-parameter,ngrok-value -WaitStatus up' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Ngrok/CommunityToolkit.Aspire.Hosting.Ngrok.csproj (in 369 ms). CommunityToolkit.Aspire.Hosting.Ngrok -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Ngrok/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Ngrok.dll CommunityToolkit.Aspire.Hosting.Ngrok -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Ngrok/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Ngrok.dll CommunityToolkit.Aspire.Hosting.Ngrok -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Ngrok/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Ngrok.dll Successfully created package '/tmp/ct-polyglot-c56a0da76d4e4aafb60e8890febf38ae/CommunityToolkit.Aspire.Hosting.Ngrok.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 2s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. { "appHostPath": "/home/runner/work/Aspire/Aspire/examples/ngrok/CommunityToolkit.Aspire.Hosting.Ngrok.AppHost.TypeScript/apphost.ts", "appHostPid": 5427, "cliPid": 5373, "dashboardUrl": "https://localhost:29750/login?t=098e6ee2a7060841cf60aa4a59821149", "logFile": "/home/runner/.aspire/logs/cli_20260415T103418690_detach-child_7d17fb052e43463fa05234f689316ab6.log" } Waiting for resource 'upstream' to be up (running)... ✔ Resource 'upstream' is up (running). (5.7s) Waiting for resource 'ngrok-parameter' to be up (running)... ❌ Resource 'ngrok-parameter' entered a failed state: FailedToStart. 📦 Found running AppHost: apphost.ts 🛑 Sending stop signal... Stopping Aspire apphost... ✔ Apphost stopped successfully. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Starting Aspire apphost in the background... DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 18: aspire wait ngrok-parameter --status | up --apphost | /home/runner/work/Aspire/Aspire/examples/ngrok/CommunityToolkit.Aspire.Hosting.Ngrok.AppHost.TypeScript/apphost.ts --timeout 180
run-tests / Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/postgres-ext/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions -WaitForResources postgres,postgres-dbgate,postgres-adminer -WaitStatus up' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/CommunityToolkit.Aspire.Hosting.Flyway.csproj (in 1.03 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 1.04 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 1.03 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.csproj (in 1.04 sec). CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Flyway.dll CommunityToolkit.Aspire.Hosting.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Flyway.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Flyway.dll CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.dll CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.dll CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.dll Successfully created package '/tmp/ct-polyglot-6322adb8f2af45b6b2cdd6c52893ed65/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 3s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.Adminer with version (>= 13.2.1-polyglot.local) �[1;3
run-tests / Hosting.Rust.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.Rust.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Rust.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/rust/CommunityToolkit.Aspire.Hosting.Rust.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/CommunityToolkit.Aspire.Hosting.Rust.csproj -PackageName CommunityToolkit.Aspire.Hosting.Rust -WaitForResources rust-app -RequiredCommands cargo,rustc' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/CommunityToolkit.Aspire.Hosting.Rust.csproj (in 482 ms). CommunityToolkit.Aspire.Hosting.Rust -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Rust.dll CommunityToolkit.Aspire.Hosting.Rust -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Rust.dll CommunityToolkit.Aspire.Hosting.Rust -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Rust.dll Successfully created package '/tmp/ct-polyglot-18bc226703b64313b4d9f1c25f9db496/CommunityToolkit.Aspire.Hosting.Rust.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 6s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. { "appHostPath": "/home/runner/work/Aspire/Aspire/examples/rust/CommunityToolkit.Aspire.Hosting.Rust.AppHost.TypeScript/apphost.ts", "appHostPid": 7464, "cliPid": 7360, "dashboardUrl": "https://localhost:29750/login?t=c56e71df8380058bd2e2c5f061b45f4a", "logFile": "/home/runner/.aspire/logs/cli_20260415T103421898_detach-child_46bf7b18bd164c83857475ab84463977.log" } Waiting for resource 'rust-app' to be healthy... ❌ Resource 'rust-app' entered a failed state: Stopped waiting for resource 'rust-app' to become healthy because it failed to start.. 📦 Found running AppHost: apphost.ts 🛑 Sending stop signal... Stopping Aspire apphost... ✔ Apphost stopped successfully. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Starting Aspire apphost in the background... DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 18: aspire wait rust-app --status healthy | --apphost | /home/runner/work/Aspire/Aspire/examples/rust/CommunityToolkit.Aspire.Hosting.Rust.AppHost.TypeScript/apphost.ts --timeout 180
run-tests / Hosting.SqlServer.Extensions.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/sqlserver-ext/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.SqlServer.Extensions -WaitForResources sqlserver -WaitStatus up' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.csproj (in 1.33 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 1.33 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 1.32 sec). CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.SqlServer.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.SqlServer.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.dll CommunityToolkit.Aspire.Hosting.SqlServer.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.dll Successfully created package '/tmp/ct-polyglot-ef34758aae1a4c548e8c9b0b353fc7c1/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 2s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.Adminer with version (>= 13.2.1-polyglot.local) - Found 160 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in
run-tests / Hosting.Logto.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.Logto.Tests.AppHostTest.LogtoResourceStartsAndRespondsOk: tests/CommunityToolkit.Aspire.Hosting.Logto.Tests/AppHostTest.cs#L11
System.Net.Http.HttpRequestException : Connection refused (localhost:3001) ---- System.Net.Sockets.SocketException : Connection refused
run-tests / Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/opentelemetry-collector/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.csproj -PackageName CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector -WaitForResources collector,collector-routed' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.csproj (in 405 ms). CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.dll CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.dll CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.dll Successfully created package '/tmp/ct-polyglot-b54895b0ac744c16bb472bfb2877e5d8/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 3s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump DOTNET_DbgEnableMiniDump is set and the createdump binary does not exist: /opt/hostedtoolcache/aspire/quality-release/x64/createdump Starting Aspire apphost in the background... ❌ Apphost process exited with code 2. 🔎 Check logs for details: /home/runner/.aspire/logs/cli_20260415T103420404_detach-child_9a5422852af542bbbf3c6a6ef387abc9.log Exception: /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | /home/runner/work/Aspire/Aspire/examples/opentelemetry-collector/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.AppHost.TypeScript/apphost.ts --isolated --format Json --non-interactive
run-tests / Hosting.Azure.DataApiBuilder.Tests-windows-latest
Process completed with exit code 1.
run-tests / Hosting.Azure.DataApiBuilder.Tests-windows-latest
Process completed with exit code 1.
run-tests / Hosting.Bun.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Bun.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Bun.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\bun\CommunityToolkit.Aspire.Hosting.Bun.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Bun\CommunityToolkit.Aspire.Hosting.Bun.csproj -PackageName CommunityToolkit.Aspire.Hosting.Bun -WaitForResources bun-app,bun-defaults,bun-watch -WaitStatus up -RequiredCommands bun' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Bun\CommunityToolkit.Aspire.Hosting.Bun.csproj (in 730 ms). CommunityToolkit.Aspire.Hosting.Bun -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Bun\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Bun.dll CommunityToolkit.Aspire.Hosting.Bun -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Bun\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Bun.dll CommunityToolkit.Aspire.Hosting.Bun -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Bun\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Bun.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-5f3b33d2846847599d4540dbca554b2c\CommunityToolkit.Aspire.Hosting.Bun.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103615656_detach-child_a42959a3ebd44375958edba6b7c45b57.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\bun\CommunityToolkit.Aspire.Hosting.Bun.AppHost.TypeScript\apphost.ts --isolated | --format Json --non-interactive
run-tests / Hosting.Rust.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Rust.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Rust.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\rust\CommunityToolkit.Aspire.Hosting.Rust.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Rust\CommunityToolkit.Aspire.Hosting.Rust.csproj -PackageName CommunityToolkit.Aspire.Hosting.Rust -WaitForResources rust-app -RequiredCommands cargo,rustc' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Rust\CommunityToolkit.Aspire.Hosting.Rust.csproj (in 469 ms). CommunityToolkit.Aspire.Hosting.Rust -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Rust\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Rust.dll CommunityToolkit.Aspire.Hosting.Rust -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Rust\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Rust.dll CommunityToolkit.Aspire.Hosting.Rust -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Rust\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Rust.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-67e44939a6ba491d90d3f75c0a9baf1f\CommunityToolkit.Aspire.Hosting.Rust.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 3s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103629693_detach-child_9b7ac8af53424a7e8fe0adcca53ab079.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\rust\CommunityToolkit.Aspire.Hosting.Rust.AppHost.TypeScript\apphost.ts --isolated | --format Json --non-interactive
run-tests / Hosting.Deno.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Deno.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Deno.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\deno\CommunityToolkit.Aspire.Hosting.Deno.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Deno\CommunityToolkit.Aspire.Hosting.Deno.csproj -PackageName CommunityToolkit.Aspire.Hosting.Deno -WaitForResources vite-demo,oak-demo -RequiredCommands deno' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Deno\CommunityToolkit.Aspire.Hosting.Deno.csproj (in 713 ms). CommunityToolkit.Aspire.Hosting.Deno -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Deno\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Deno.dll CommunityToolkit.Aspire.Hosting.Deno -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Deno\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Deno.dll CommunityToolkit.Aspire.Hosting.Deno -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Deno\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Deno.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-0c0b7c2fbdf844cbab3f4da925a5c923\CommunityToolkit.Aspire.Hosting.Deno.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 5s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103628851_detach-child_171fb01e34b84e689ab796ac7bfd11ca.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\deno\CommunityToolkit.Aspire.Hosting.Deno.AppHost.TypeScript\apphost.ts --isolated | --format Json --non-interactive
run-tests / Hosting.Elasticsearch.Extensions.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\elasticsearch-ext\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.csproj (in 570 ms). CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.dll CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.dll CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-aa82d7f111a74f39aaa75e7232a197e5\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 5s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103658755_detach-child_94b9361a449845fab3138443af958ce4.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\elasticsearch-ext\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.AppHost.TypeScript\apphost.ts --isolated --format Json --non-interactive
run-tests / Hosting.Python.Extensions.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Python.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Python.Extensions.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\python\CommunityToolkit.Aspire.Hosting.Python.Extensions.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Python.Extensions\CommunityToolkit.Aspire.Hosting.Python.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.Python.Extensions' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Python.Extensions\CommunityToolkit.Aspire.Hosting.Python.Extensions.csproj (in 500 ms). CommunityToolkit.Aspire.Hosting.Python.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Python.Extensions\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Python.Extensions.dll CommunityToolkit.Aspire.Hosting.Python.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Python.Extensions\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Python.Extensions.dll CommunityToolkit.Aspire.Hosting.Python.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Python.Extensions\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Python.Extensions.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-a9bc233417ab4964b0208442adda41ba\CommunityToolkit.Aspire.Hosting.Python.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103717465_detach-child_463c1a992ab24c55b2786414228acb5c.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\python\CommunityToolkit.Aspire.Hosting.Python.Extensions.AppHost.TypeScript\apphost.ts --isolated --format Json --non-interactive
run-tests / Hosting.Java.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Java.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Java.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\java\CommunityToolkit.Aspire.Hosting.Java.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\CommunityToolkit.Aspire.Hosting.Java.csproj -PackageName CommunityToolkit.Aspire.Hosting.Java' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\CommunityToolkit.Aspire.Hosting.Java.csproj (in 511 ms). CommunityToolkit.Aspire.Hosting.Java -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Java.dll CommunityToolkit.Aspire.Hosting.Java -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Java.dll CommunityToolkit.Aspire.Hosting.Java -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Java.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-719b792092a6418592522551d63516d7\CommunityToolkit.Aspire.Hosting.Java.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103804051_detach-child_8ca651422cdd40f79a6ea323770e8c5f.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\java\CommunityToolkit.Aspire.Hosting.Java.AppHost.TypeScript\apphost.ts --isolated | --format Json --non-interactive
run-tests / Hosting.JavaScript.Extensions.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.Tests/TypeScriptAppHostTests.cs#L7
Command 'pwsh.exe -NoLogo -NoProfile -File D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1 -AppHostPath D:\a\Aspire\Aspire\examples\javascript-ext\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.JavaScript.Extensions -WaitForResources turbo-web -RequiredCommands yarn,pnpm' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.csproj (in 499 ms). CommunityToolkit.Aspire.Hosting.JavaScript.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.dll CommunityToolkit.Aspire.Hosting.JavaScript.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.dll CommunityToolkit.Aspire.Hosting.JavaScript.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-3274a2186f884eaea324881c47741a56\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 4s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T103704785_detach-child_618dd77d1dea49c082c6583c573d68b9.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\javascript-ext\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.AppHost.TypeScript\apphost.ts --isolated --format Json --non-interactive
run-tests / Hosting.Golang.Tests-windows-latest
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
run-tests / Microsoft.Data.Sqlite.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Minio.Client.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / SurrealDb.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Stripe.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / GoFeatureFlag.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Logto.Client.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.Dapr.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.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 / Hosting.Azure.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / MassTransit.RabbitMQ.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Microsoft.EntityFrameworkCore.Sqlite.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Sftp.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / RavenDB.Client.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Meilisearch.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Python.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MongoDB.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MongoDB.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Dapr.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.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 / Hosting.Redis.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Redis.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / OllamaSharp.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.Dapr.Redis.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.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 / Hosting.LavinMQ.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / GoFeatureFlag.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4, timheuer/setup-aspire@v0.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 / GoFeatureFlag.Tests-windows-latest
No files were found with the provided path: C:\\Users\\runneradmin\\.aspire\\logs\\**. No artifacts will be uploaded.
run-tests / GoFeatureFlag.Tests-windows-latest
No files were found with the provided path: testresults/**. No artifacts will be uploaded.
run-tests / GoFeatureFlag.Tests-windows-latest
No files were found with the provided path: **/*.binlog. No artifacts will be uploaded.
run-tests / Hosting.Perl.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.PapercutSmtp.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.RavenDB.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.k6.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.McpInspector.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.McpInspector.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / KurrentDB.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Flagd.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Bun.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Sqlite.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Golang.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Minio.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MySql.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MySql.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Deno.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MailPit.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Solr.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Solr.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Ngrok.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Ngrok.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.PostgreSQL.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Java.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.ActiveMQ.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.GoFeatureFlag.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Ollama.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Adminer.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Umami.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Rust.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Rust.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.KurrentDB.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Meilisearch.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Keycloak.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlServer.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlServer.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Logto.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Logto.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Elasticsearch.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.OpenTelemetryCollector.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.DbGate.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.PowerShell.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Zitadel.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MailPit.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.JavaScript.Extensions.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Stripe.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SurrealDb.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlDatabaseProjects.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.Flyway.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SurrealDb.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlServer.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Sftp.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Sftp.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Redis.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 (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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 (ubuntu-latest)
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
build (ubuntu-latest)
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Minio.Client.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Logto.Client.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.PostgreSQL.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Keycloak.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.PapercutSmtp.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / KurrentDB.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Solr.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.LavinMQ.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Umami.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / RavenDB.Client.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.RavenDB.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.OpenTelemetryCollector.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MongoDB.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.k6.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.ActiveMQ.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Flyway.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / MassTransit.RabbitMQ.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / OllamaSharp.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.KurrentDB.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlDatabaseProjects.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.SqlDatabaseProjects.Tests-windows-latest
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.SqlDatabaseProjects.Tests-windows-latest
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Microsoft.Data.Sqlite.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Zitadel.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Flagd.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Ollama.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.PowerShell.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Dapr.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.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 / Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.Dapr.Redis.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.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 / Meilisearch.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Sqlite.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.DataApiBuilder.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.DataApiBuilder.Tests-windows-latest
No files were found with the provided path: testresults/**. No artifacts will be uploaded.
run-tests / Hosting.Azure.DataApiBuilder.Tests-windows-latest
No files were found with the provided path: **/*.binlog. No artifacts will be uploaded.
run-tests / Hosting.Azure.DataApiBuilder.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@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.GoFeatureFlag.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Logto.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.MySql.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Ngrok.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.DbGate.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Meilisearch.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Perl.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Adminer.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Sftp.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Bun.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Rust.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Deno.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.McpInspector.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Elasticsearch.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Python.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Minio.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / Hosting.Azure.Dapr.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.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 / Hosting.Java.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 / SurrealDb.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 (windows-latest)
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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 (windows-latest)
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
build (windows-latest)
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.JavaScript.Extensions.Tests-windows-latest
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/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.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/

Artifacts

Produced during runtime
Name Size Digest
binlog-GoFeatureFlag.Tests-ubuntu-latest
951 KB
sha256:49d0aff4de9e52929a468893ffdaff7c0f8e3aa7ff284201f052b0067ee2f438
binlog-Hosting.ActiveMQ.Tests-ubuntu-latest
1.4 MB
sha256:a15bc2df35734e6d8b91e26764d2ca3af52155270ad80f76c1d479b338557fed
binlog-Hosting.ActiveMQ.Tests-windows-latest
1.43 MB
sha256:3588e12352e8e1fac32390c368b36ae92cce922011fca4f8ec1cd54bfd8d2721
binlog-Hosting.Adminer.Tests-ubuntu-latest
2.07 MB
sha256:5cf2abed43639d24927768624e567b473ee7fa3fa42678ed4d5b52ddfffba4a4
binlog-Hosting.Adminer.Tests-windows-latest
2.1 MB
sha256:fa90a87450118fc1411cdf99ed68d4977deff0b90b066642ab6158754d318f22
binlog-Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
1.36 MB
sha256:cded25149019df8427df53a632c4dd8b99996eb39bd1fe0b34b194e1b67aa868
binlog-Hosting.Azure.Dapr.Redis.Tests-windows-latest
1.36 MB
sha256:8e5934d102bcf08ac1262652c3297d4882317b7b3cc7c58ad2b3c60214e7d0e3
binlog-Hosting.Azure.Dapr.Tests-ubuntu-latest
1.16 MB
sha256:6e7207fe87a927a824eaac0d921d73b8cdbff97b33116f5974adc590fd4bc002
binlog-Hosting.Azure.Dapr.Tests-windows-latest
1.17 MB
sha256:df9fec8fb8d1dbfeb759e66ad362974e4f3a2aa9b0a86279b6b2a36e403ae89b
binlog-Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
1.46 MB
sha256:b6cd41cecf266231b6c46b8de449cb5992fa340cf9b6e46edc58aae881a1f800
binlog-Hosting.Azure.Extensions.Tests-ubuntu-latest
1.11 MB
sha256:9647737fda51b919907bd5c8ab07f87bccb091a700806f7dfba74353a87c0f98
binlog-Hosting.Azure.Extensions.Tests-windows-latest
1.12 MB
sha256:ae8c8124dd55897ddffddbf6227f95b9c205002d4eefb0fb2fa5caaf76b17dff
binlog-Hosting.Bun.Tests-ubuntu-latest
1.06 MB
sha256:358f4331e0fe5fc8babd98329bb0d72e49027073849703d3a6e4609c1cd8b251
binlog-Hosting.Bun.Tests-windows-latest
1.07 MB
sha256:97e104288501ff7ca9783ead276bb4c563800b2181f56d962d7ed158ac7975c6
binlog-Hosting.Dapr.Tests-ubuntu-latest
1.65 MB
sha256:16302d5ac64d1abacfd83e6d80a422756cce27e171d72c3d3ed62b24b7bbe441
binlog-Hosting.Dapr.Tests-windows-latest
1.66 MB
sha256:80d5befaf2e9c89f5d7a374512ba22b3baff9191a22a8fdffb74dd66664fbcaa
binlog-Hosting.DbGate.Tests-ubuntu-latest
2.53 MB
sha256:72755ab7ccc07d7bf1869de6045a82e1e2c28fb9f5cbcc00cbd521955a5b4ea7
binlog-Hosting.DbGate.Tests-windows-latest
2.54 MB
sha256:803b5ea1e3869f1847b8bd9f5089415de8a359189db1d3fbd3174904924768d8
binlog-Hosting.Deno.Tests-ubuntu-latest
1.07 MB
sha256:0680da042fb95d90628ad3e5c1809fc281058908d28748a5735ce6c6408cc858
binlog-Hosting.Deno.Tests-windows-latest
1.07 MB
sha256:084e5b4ae36d893ca30280dd789d892e6d83b572d07219cefaa0af52017313d3
binlog-Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:3897f782404244b3f28757ead7f48c7c6b5612b21596b4d4e7e7013fd1d0431a
binlog-Hosting.Elasticsearch.Extensions.Tests-windows-latest
1.08 MB
sha256:855d1cdcb41fac58c1b93d08eb727528a1aef74c79a7c2913a8e912f5f1477b4
binlog-Hosting.Flagd.Tests-ubuntu-latest
1.07 MB
sha256:688b4568805fa5d3f1b581ff97e96b379a9bce565a32c759f25207c788e3d9e5
binlog-Hosting.Flagd.Tests-windows-latest
1.08 MB
sha256:bb2796522b9c2d73253fc523cbb1c6a8fe33f27769e204dd8aa7181cba85678d
binlog-Hosting.Flyway.Tests-ubuntu-latest
961 KB
sha256:c01d236ba6ccbd1f0bd43d0dbae34fdb64d574baf03e018cb93df3328d9c7856
binlog-Hosting.Flyway.Tests-windows-latest
979 KB
sha256:3829b23fb9d8e15eb43f89ccbcb5bcb5470854760dbc004c394131c4ca1b56ba
binlog-Hosting.GoFeatureFlag.Tests-ubuntu-latest
1.58 MB
sha256:1049da5c2280cca2d751c1d9037376c183da69c05ee85808e4b932a6056401b6
binlog-Hosting.GoFeatureFlag.Tests-windows-latest
1.59 MB
sha256:78286533ce74a86092018d212b66f1c2aa68eed0b0341ff7e45cac2a4a1023be
binlog-Hosting.Golang.Tests-ubuntu-latest
1.06 MB
sha256:85dbed9db16c1162e72250e096b2a5240b8c247f25e46f4e17afc5fc58ad408c
binlog-Hosting.Java.Tests-ubuntu-latest
1.57 MB
sha256:a02a4a0fe98f6c57824b469cb7a669db785b2bd54abd65cebef564fa98ed86b1
binlog-Hosting.Java.Tests-windows-latest
1.57 MB
sha256:0de8c189c14dd8cb88a0d473a9ec6505db357f33fa565628c9122f6d2a689bc3
binlog-Hosting.JavaScript.Extensions.Tests-ubuntu-latest
1.08 MB
sha256:6d9dbadae606fd117af92c7ddba016fc18b252a0df705d42954f396116484a7c
binlog-Hosting.JavaScript.Extensions.Tests-windows-latest
1.08 MB
sha256:3bdb8107cc60fd48b9adf92811d9b23475f180d37310e64038df553cdcd1c288
binlog-Hosting.Keycloak.Extensions.Tests-ubuntu-latest
975 KB
sha256:01eb45ca3c455ee505b5c32cad114180300490d3bf5e7bfbed7a32daa14ef95d
binlog-Hosting.Keycloak.Extensions.Tests-windows-latest
989 KB
sha256:e2db5981c8d4ec7878218be5c6525d80146b96c4a2afe855bcf252a76c0cd1f4
binlog-Hosting.KurrentDB.Tests-ubuntu-latest
1.11 MB
sha256:f524a6b5ee8ca1828ae88db88b5df67a5c944228cc75647fcef3177ccb9f4afc
binlog-Hosting.KurrentDB.Tests-windows-latest
1.12 MB
sha256:6801935f1a4da3d69708150207d774f6030e7a11c060c10a3638834a85ac0625
binlog-Hosting.LavinMQ.Tests-ubuntu-latest
1.4 MB
sha256:db173989f0d8a984f99f239d3448de55881edd4dca9d025c5b517492c75176d0
binlog-Hosting.LavinMQ.Tests-windows-latest
1.42 MB
sha256:28c53a12739cbf342e846fe326195dcbcb70b7a25a1ca81856c1d905c99c0a9b
binlog-Hosting.Logto.Tests-ubuntu-latest
1.72 MB
sha256:3097df37215d6f074566c6b8a6f2bfedd358320df849271cd81699118299fd63
binlog-Hosting.Logto.Tests-windows-latest
1.73 MB
sha256:68f39ecd564335c8e4e231e1f968fd303cb0163a8597176228466b9ad28565ef
binlog-Hosting.MailPit.Tests-ubuntu-latest
1.4 MB
sha256:cb4d45c3999c17b9cd467f4acf320576886a07aac729094ed8d73878dc747d1b
binlog-Hosting.MailPit.Tests-windows-latest
1.41 MB
sha256:dbb0af293d54f814489ca1ba76c0b4e5b821edd0233eace539ddc03d269a7cdd
binlog-Hosting.McpInspector.Tests-ubuntu-latest
1.28 MB
sha256:ccef98c7e584157caad9fe799aeba350511843c510a6d778bf4864cd27cd26ef
binlog-Hosting.McpInspector.Tests-windows-latest
1.29 MB
sha256:d70462ef6d52109ca717686c5447242809fccfa69e1d0141367f4dcd750873f7
binlog-Hosting.Meilisearch.Tests-ubuntu-latest
1.58 MB
sha256:007d55becdc09b2f1d5cb8c27842df68873ffc3dfc597b5fdb1e5420041622d5
binlog-Hosting.Meilisearch.Tests-windows-latest
1.6 MB
sha256:dffaadcd6cef2060a09042ec5c1106adc3a1fd4df1c9af50a03c60947539cd62
binlog-Hosting.Minio.Tests-ubuntu-latest
1.57 MB
sha256:2b728a5e24e26b40336a0758126414cf5112d6d3d5be6038075f3a908e6ffa6a
binlog-Hosting.Minio.Tests-windows-latest
1.59 MB
sha256:e640c263052fa6f29bf6b14d49739119720b24d2d35927cbd95c36f38707ecdc
binlog-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
1.26 MB
sha256:3ddf26c3551871b4a6921a883c28943f92b1236fd3754b278d9fb68d500f593c
binlog-Hosting.MongoDB.Extensions.Tests-windows-latest
1.28 MB
sha256:b87d63addf894f9b389466188dad26b5f90022a146cef1d8fc382ed03fa62f33
binlog-Hosting.MySql.Extensions.Tests-ubuntu-latest
1.44 MB
sha256:fbd1f0361b1be3ad3e14e67c1315ca291324ef62c9cd08e10e184e0314a0412a
binlog-Hosting.MySql.Extensions.Tests-windows-latest
1.43 MB
sha256:3f3a6ee33b854c331c41a59b24d4a22c46262e10cca1ae1a68a00ffba94a223d
binlog-Hosting.Ngrok.Tests-ubuntu-latest
1.39 MB
sha256:e3721f8692cdbb87507a76b766b67363b55288ceb0765bebac0bf44f873f1749
binlog-Hosting.Ngrok.Tests-windows-latest
1.41 MB
sha256:87c7296409ef876ced598efb893f643fc32b5b56289d02e6d7a22bed9a271c33
binlog-Hosting.Ollama.Tests-ubuntu-latest
1.22 MB
sha256:c9c1546945d8942c0395ff6b1f7264df820c474ea937f84cd61f1ee3f3ded5f3
binlog-Hosting.Ollama.Tests-windows-latest
1.23 MB
sha256:38e2e1ee41278a0774e8974d5c0ed79620c8f59f05998c2f1b3cb6038c2f41b3
binlog-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
958 KB
sha256:fd27fdf289040215f537339cce8bfd03aec71041f98e2a7263ad9b6aac2b0835
binlog-Hosting.OpenTelemetryCollector.Tests-windows-latest
981 KB
sha256:eca99e48badc84c515dce9f152417b1a0d8eb87c40c8f2f6f9760572fc2343ca
binlog-Hosting.PapercutSmtp.Tests-ubuntu-latest
1.4 MB
sha256:4aad25481f994d76359e74c8b46441c5688b80ed786d892ef38b6be3d6eff0a7
binlog-Hosting.PapercutSmtp.Tests-windows-latest
1.41 MB
sha256:20106c19a0bc0b9def88e5d699a974b4089c8700f1d94d8b2134f002f90c7a20
binlog-Hosting.Perl.Tests-ubuntu-latest
1.06 MB
sha256:4e77ec5eebdce1266eb664c54df9710eea3879376eadd4427396682d8a750e6f
binlog-Hosting.Perl.Tests-windows-latest
1.08 MB
sha256:8f496f1382647d17e6c64bbc87875d25156f0df30ee96c1c69196ea61c49d5aa
binlog-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
1.59 MB
sha256:1034b012a8d1a9f7179113242098e35c44e180a0431c5e623a2bd3900a517713
binlog-Hosting.PostgreSQL.Extensions.Tests-windows-latest
1.61 MB
sha256:fe5d0081d0fe7f547ba7e142506302d4e5591b4d943ec316709203a7b85c5440
binlog-Hosting.PowerShell.Tests-ubuntu-latest
1.31 MB
sha256:c4855bdecbcb350d95213d1948c433f10592b39410e957e8b7bab3d08322b172
binlog-Hosting.PowerShell.Tests-windows-latest
1.32 MB
sha256:d0ab52e729292ac17ea37aa1dcef98776fe8eded3e2f2c4451c8008e55a37ce4
binlog-Hosting.Python.Extensions.Tests-ubuntu-latest
1.06 MB
sha256:b75f0b140d02579a72ba90eed48c75042c957a39b56de0f7d06e3e4b6ea84594
binlog-Hosting.Python.Extensions.Tests-windows-latest
1.09 MB
sha256:c53df55171d0e96ac8ef65f5712d7e11e7d4448362437cc6864bc37112ca7a9d
binlog-Hosting.RavenDB.Tests-ubuntu-latest
1.58 MB
sha256:ee5da52f14afafcaa9502ce654314d0493904eb1876f118ac1a969659a5b8f2e
binlog-Hosting.RavenDB.Tests-windows-latest
1.62 MB
sha256:688a99191d86ae6abbcb32d4631a46eb06fb199e972c444ef29ca7d079b679ca
binlog-Hosting.Redis.Extensions.Tests-ubuntu-latest
1.26 MB
sha256:5297b0429815450e80e4b2245e5bd261e8924c0a1b35d535ab7041386f7a34c7
binlog-Hosting.Redis.Extensions.Tests-windows-latest
1.26 MB
sha256:c38461eefef469052e3e824f97c685a5f8b4a2c39ee898b3ab09ecb6d9ceb424
binlog-Hosting.Rust.Tests-ubuntu-latest
1.07 MB
sha256:9c2c9c06422067b90a29220539810763a64ec353cfd524f6aefd3408914d95a1
binlog-Hosting.Rust.Tests-windows-latest
1.07 MB
sha256:d7615699dbbd841ba0e83aa1aaa56d87a85ab18da1f0904c5caefcbc65a4e617
binlog-Hosting.Sftp.Tests-ubuntu-latest
1.58 MB
sha256:46da877bfe2f775e04a64208097c77bb21c9b31539073fb84bcb185952f19541
binlog-Hosting.Sftp.Tests-windows-latest
1.61 MB
sha256:6547993c328d0515ecfb19c985ca2d8448ed91d3ec10f17df35562cc62621b57
binlog-Hosting.Solr.Tests-ubuntu-latest
1.06 MB
sha256:e5448e4ab23cfe139e9877349268ec6d89a55db8fda937d74622be0438a63b53
binlog-Hosting.Solr.Tests-windows-latest
1.07 MB
sha256:9f3259d5f5dbcdf30a5bc5ee44d61debd78b56f3387b3ca6edf6d075366958bc
binlog-Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
1.26 MB
sha256:4a918a0572ff07a66b693a75fb72a2e5c564f4d329dafaad8b5455bcb20c2052
binlog-Hosting.SqlDatabaseProjects.Tests-windows-latest
1.28 MB
sha256:f44cc2b3b72b5bb45d502ef026df6f9cbc1de4bc32dd70f9f4c5931d20d5a2f5
binlog-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
1.47 MB
sha256:83412fed08c4a06d08e7f5478357db1158976438a88c18539c10a5483748af7b
binlog-Hosting.SqlServer.Extensions.Tests-windows-latest
1.49 MB
sha256:08413ad71b73e85edc98920feb99559284899f00ca0ca231260e673bb98bcb9a
binlog-Hosting.Sqlite.Tests-ubuntu-latest
1.79 MB
sha256:2a4d086d7eb74b92c71e45a3f4d9b2d68543aabfdfbcc8ff70b7a5c3a4bd2223
binlog-Hosting.Sqlite.Tests-windows-latest
1.83 MB
sha256:34376943e60686a9953b37c97cc938c7832dd22a7d27236cabb6e1e48daa5257
binlog-Hosting.Stripe.Tests-ubuntu-latest
1.26 MB
sha256:b8339910d50c22ac1f9174672d04a861327bfdd7bb55fa9c53b949bb043ec459
binlog-Hosting.Stripe.Tests-windows-latest
1.28 MB
sha256:998261cf7631896406e482b06c621daaa15293d5619bed969ecdf7dc95c223ea
binlog-Hosting.SurrealDb.Tests-ubuntu-latest
1.6 MB
sha256:180e2d04a0c4f56abc10a4b4fbc6f0e54aa67b73ceb129954d78be9480d2a225
binlog-Hosting.SurrealDb.Tests-windows-latest
1.62 MB
sha256:43c9089ff276175f6222ddb0b2b6eaf89d3b22cf165be7bc9675ac6c2fa2b85c
binlog-Hosting.Umami.Tests-ubuntu-latest
1.07 MB
sha256:c22c40f597c6572729513345cbebecf8569d8389a91c218f296bf96cf84dc1b9
binlog-Hosting.Umami.Tests-windows-latest
1.07 MB
sha256:b60a5b2004dc7e69d7aea77d3d8206b647b4e8a6629668935d5ece50c5e4e3ee
binlog-Hosting.Zitadel.Tests-ubuntu-latest
1.06 MB
sha256:dbfea1e7c98c1a1e9363b41530fe4fa40d9502b3439436d52f30c43adaba1419
binlog-Hosting.Zitadel.Tests-windows-latest
1.07 MB
sha256:57e87111ed90b7a569069b2b6937b885b1a0738fc9710c5d6778f4fc58d4c89f
binlog-Hosting.k6.Tests-ubuntu-latest
1.39 MB
sha256:56caa6940d91f9ddd851ed905a5bff11f413e1ff1788653e80cddc92f7ab59e3
binlog-Hosting.k6.Tests-windows-latest
1.41 MB
sha256:ccd5d433009352e8c72b88bb7eb7e7c6db35d09cd34eb5782ccef7e164688402
binlog-KurrentDB.Tests-ubuntu-latest
952 KB
sha256:0a3b9ebe102d7a88f4de3d586aef7093f4ae18f2ca12c1dc842da270c978e1c9
binlog-KurrentDB.Tests-windows-latest
963 KB
sha256:4bc5e4d864979100688ba94701bb3b42ba101f4fc0f5a8a6ac0beaef41abf526
binlog-Logto.Client.Tests-ubuntu-latest
773 KB
sha256:9c4457e5e1170f2af60e3be8ee31e2ca366b4866514ee92310fdc380273ed5f4
binlog-Logto.Client.Tests-windows-latest
784 KB
sha256:ab28cd65ef96b1e886b5f03bfaad0c112d657d3fe94314584c401f41c6ffea48
binlog-MassTransit.RabbitMQ.Tests-ubuntu-latest
941 KB
sha256:f96185abf5fb6cbb32d38c7800b384d39c08767d9c6dfc63ce4a6ba68559ed68
binlog-MassTransit.RabbitMQ.Tests-windows-latest
954 KB
sha256:696e866135262b78e8752738d318d1ea356dc1c17ec07cf32d16e6bd3780295c
binlog-Meilisearch.Tests-ubuntu-latest
950 KB
sha256:a20fb70dc79dacc609ef564511279878ad6a3484bbb7e6a2885877d28cbd1cc4
binlog-Meilisearch.Tests-windows-latest
960 KB
sha256:e2a07d96c1a6b128415b57f8c21e03b57826ce2bd24f71dab8404cbfbe65e91a
binlog-Microsoft.Data.Sqlite.Tests-ubuntu-latest
947 KB
sha256:66e9fd4083b79246d0745f65ce84241a1797d1dbbfb7df59f5e96e5144fe9b0d
binlog-Microsoft.Data.Sqlite.Tests-windows-latest
963 KB
sha256:4e47d209368412375799d2aa89d2a0a5ba260be62946c6d3ac39a886e5585788
binlog-Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
957 KB
sha256:3a63709e1a42ef2de50b9eee4c1a4b37489c071b679238d95bc32bf8287e24a8
binlog-Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
980 KB
sha256:0f605fa93929572ad3f2bca1bdec02218878fd0bf493fb92d7e158516f852e08
binlog-Minio.Client.Tests-ubuntu-latest
1.1 MB
sha256:8fb670f86484028ffd72211834d5851daf7664395ff6def6087c92ca457a371f
binlog-Minio.Client.Tests-windows-latest
1.11 MB
sha256:526183e65e4aa2c6ed73d396bce54fba4ad35438835669211af825378478fe00
binlog-OllamaSharp.Tests-ubuntu-latest
951 KB
sha256:32e15d21316660624a0ed17cd5b3071302fd2815b9de6c831eddd231aa91cc7b
binlog-OllamaSharp.Tests-windows-latest
963 KB
sha256:7fc23bb5d3ccac2166104b4d9baae2cb5820e84d8a56277f28499360c903969d
binlog-RavenDB.Client.Tests-ubuntu-latest
836 KB
sha256:f3ed62353730b3b461c78b1915957563fa878b2dbbf56b2e8c5ddb076a1d032f
binlog-RavenDB.Client.Tests-windows-latest
851 KB
sha256:fb94ddd4e90010bb7b3fdb74ef6cdf2b711b21b6fc6849432160fb0a725c5110
binlog-Sftp.Tests-ubuntu-latest
940 KB
sha256:37f085188257557a08c50de52d0ebad6d4527e5379dc1f50baaf41fb5eee2ed1
binlog-Sftp.Tests-windows-latest
956 KB
sha256:76a87731bf8e544383f92c56473576a70a7e9fe6f13fda2df1a53d7c1b2a4dc1
binlog-SurrealDb.Tests-ubuntu-latest
960 KB
sha256:d00c17aa8c41ab2cc9488cb635fa7e25a266665a29cae1f20c0f39a2b9b3413d
binlog-SurrealDb.Tests-windows-latest
965 KB
sha256:62fec34921ee212582b204f01937fe177635a44b29ef9595eeb9ca89ca6de521
npm-logs-GoFeatureFlag.Tests-windows-latest
94.8 KB
sha256:bacec2daa06332f069bf103fd94cc2a7f57197ccbc0a4348d3fd0cfc7134a093
npm-logs-Hosting.Azure.DataApiBuilder.Tests-windows-latest
94.8 KB
sha256:bacec2daa06332f069bf103fd94cc2a7f57197ccbc0a4348d3fd0cfc7134a093
npm-logs-Hosting.Bun.Tests-windows-latest
114 KB
sha256:671d587ef2a1f05a497dacacb30a6ef05c8c1700c6b953807875c3c1696c2b3e
npm-logs-Hosting.Deno.Tests-windows-latest
115 KB
sha256:6bee7b87896c02dd67d73ee8fb49fa7cca47ba94c7df385a23cb106e871956c2
npm-logs-Hosting.Elasticsearch.Extensions.Tests-windows-latest
115 KB
sha256:880a579fd5345b2589c0b4ec85f7713f384adcc7a60d87080873f94b4a75aca5
npm-logs-Hosting.Java.Tests-windows-latest
114 KB
sha256:d957c62536f6fc118d857431e8a14014379785f7f6738dcfecb30a2a5ad811cb
npm-logs-Hosting.JavaScript.Extensions.Tests-windows-latest
208 KB
sha256:9b393e1fd71e9b5507e0f3018e8ce9aaf1029937e767f9e19add4548f4a8072c
npm-logs-Hosting.Python.Extensions.Tests-windows-latest
114 KB
sha256:4257e72b466466292243bb7cb916acfbc6c4c0482992197954c23b0d029dc517
npm-logs-Hosting.Rust.Tests-windows-latest
114 KB
sha256:b2cfa1cc08642db16b76e1da264e327d00692fac94c786022177f9ab94206df3
testresults-GoFeatureFlag.Tests-ubuntu-latest
24.6 KB
sha256:34cd3453b4064701ababc1aabbcdfc02589bdb46b40c44a38d2c85dde3e30c86
testresults-Hosting.ActiveMQ.Tests-ubuntu-latest
26 KB
sha256:a7818bec23ffa6052636c18c4baab5037402ec847d175bc4b5ba2450345d1501
testresults-Hosting.ActiveMQ.Tests-windows-latest
22.4 KB
sha256:840aa2cd16e4389a4f4b316999835dd1f0bf12fe31e0c6bb4b018dd77c918b12
testresults-Hosting.Adminer.Tests-ubuntu-latest
27.2 KB
sha256:db74d5ea236edc57f6c82a7d8f9008d014c55c6d79e8cb77db5928fa7e2755f4
testresults-Hosting.Adminer.Tests-windows-latest
25.7 KB
sha256:ad146b691bc79da0a181ba5fd821b9fd212b8188ec943172bf9ba703409f981c
testresults-Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
49.4 KB
sha256:f7e9b2d1fb20ecb366cd01d457954f01c42c15c438183378ae6644659687ca18
testresults-Hosting.Azure.Dapr.Redis.Tests-windows-latest
49.5 KB
sha256:d4151d0248bdb0fb08fd8f1db789052702f4bd94fa4e65451339133438284ae8
testresults-Hosting.Azure.Dapr.Tests-ubuntu-latest
47.4 KB
sha256:699fdb5b1f1eba8c8d9bfc8f3dab9b9a97e232d9a604ca4e5cf39426e1bcdce8
testresults-Hosting.Azure.Dapr.Tests-windows-latest
47.4 KB
sha256:9a32a403dbc97576e41ac8de81314bf854c860024c25bdafa71fb305f13fd5fe
testresults-Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
23.8 KB
sha256:bb64b020a1c26c22279500b72bfb27a7f22f3a9256e9fae66664eae56438ffcf
testresults-Hosting.Azure.Extensions.Tests-ubuntu-latest
20.5 KB
sha256:7526c34abdc24077715c3bf57e04092407903057dbcb3e7606d62aac2318c1fb
testresults-Hosting.Azure.Extensions.Tests-windows-latest
20.1 KB
sha256:3a7f389bf6cd43e367ec506f8c1e7c87bbf88dea5fa4f0c18f2c86d227f12d5c
testresults-Hosting.Bun.Tests-ubuntu-latest
20.9 KB
sha256:e2a1e6817ed5178cbb543eacff4e3c13fbc8b0757c561fdecaa37a84f0b368a4
testresults-Hosting.Bun.Tests-windows-latest
22.4 KB
sha256:467b351ad1748c0231ff3a7ccbf1b53cba8c9130654a0ebd50862f4043451fed
testresults-Hosting.Dapr.Tests-ubuntu-latest
47.2 KB
sha256:0c41bd79f8a0289002b85981100a36f7661de01eea7cad58856e8162062457d4
testresults-Hosting.Dapr.Tests-windows-latest
47 KB
sha256:204a281960c93b8e420071a37a6f6878438d3b3d5a547d1e5163147a204fdbf0
testresults-Hosting.DbGate.Tests-ubuntu-latest
29.4 KB
sha256:ecfbcbe4b6afb166e9755fac600c235237a658fc6cbaa7e60abfac5aac1895d4
testresults-Hosting.DbGate.Tests-windows-latest
27.8 KB
sha256:0fa6e1d4db1e9c5aec54569b4d11d38604f4c508d234db1e234df06f0b2a3eeb
testresults-Hosting.Deno.Tests-ubuntu-latest
20.4 KB
sha256:b447fb610bac9b40e0362a4b792addf84481180e21f091100e589315e7e424c1
testresults-Hosting.Deno.Tests-windows-latest
21.8 KB
sha256:f82921796587bb56d398e1d530dde45af73a93131d9560014200c926469fcb70
testresults-Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
21.3 KB
sha256:f439c87bbec567d6d8a7dbdd7fcc267f104abccd9e94ecfa88ebe11d2e75d872
testresults-Hosting.Elasticsearch.Extensions.Tests-windows-latest
22.3 KB
sha256:18d567672e84961e453ef1b526394829e3d898008f9b727ac871b56a08dd6c71
testresults-Hosting.Flagd.Tests-ubuntu-latest
22.7 KB
sha256:b0278ab076a99b32ae00cf63597cfdfedfae5e6506d3646b716c399d2071afc1
testresults-Hosting.Flagd.Tests-windows-latest
21.7 KB
sha256:58a53e540b25c173aec033fc6b6f49c0a46b161fcb36d7e690ce5caa6ebb0d6b
testresults-Hosting.Flyway.Tests-ubuntu-latest
19.1 KB
sha256:4216d53c7b94707b91d2582ac047b6bd1cd9af6109b2c75721df549f446f7467
testresults-Hosting.Flyway.Tests-windows-latest
18.7 KB
sha256:c36329642799a44dbd399cb6a03f98f864765e61c356fc2a040b5bea7c805f28
testresults-Hosting.GoFeatureFlag.Tests-ubuntu-latest
26.3 KB
sha256:5100a1a1ee4520c5ece99cd02d5cd6760e83aa8983e03e26bbdb8322718577c2
testresults-Hosting.GoFeatureFlag.Tests-windows-latest
21.2 KB
sha256:31c64960fee546aee8a5e85ad6775835d82131e52a6b718d5de2c7ccc98356e1
testresults-Hosting.Golang.Tests-ubuntu-latest
24.3 KB
sha256:f16c41d74a99aba0e825cf16f6f9e63e2193a522212635fc65d2d86c55cd430d
testresults-Hosting.Java.Tests-ubuntu-latest
33.5 KB
sha256:53913c2cb23e7ecd2737a8720c74190d1c099210b2181902bde73d535eb1e126
testresults-Hosting.Java.Tests-windows-latest
29.7 KB
sha256:323b7da68d89ab7658d8ea7595b8d90b59703020589bf4a041c0d77d5c3bdacf
testresults-Hosting.JavaScript.Extensions.Tests-ubuntu-latest
28.8 KB
sha256:967b50c7be008f353b37cb7b8aabf5fa679a3328c0a59c04942c9117d42b5292
testresults-Hosting.JavaScript.Extensions.Tests-windows-latest
31.2 KB
sha256:1e71768c40e51ce1a0b683e7b4346666283daa86f330c8ca5c8875840e218ab0
testresults-Hosting.Keycloak.Extensions.Tests-ubuntu-latest
20 KB
sha256:4afdf6225559a032d82805ec894ed63eae967291d6e45842710a2f26de514d66
testresults-Hosting.Keycloak.Extensions.Tests-windows-latest
19.2 KB
sha256:35a126e577863a7a05f8b25f3a724558e0b92ea34d4625e01bf8b969e8a5a2f7
testresults-Hosting.KurrentDB.Tests-ubuntu-latest
23.8 KB
sha256:46223876c7b7e5673416f8d53859d3002fc42760cdae2ff1091f5349472ef0bf
testresults-Hosting.KurrentDB.Tests-windows-latest
20.7 KB
sha256:4f59d579ba792b6e354234ef0ae1e715cc6d575d510b9b2aab5ed6b8025d2073
testresults-Hosting.LavinMQ.Tests-ubuntu-latest
23.4 KB
sha256:4d58ac048fce0ba3366ffea26a7c47aa54b4b1e0aafa7e0a67d633a3bc142d42
testresults-Hosting.LavinMQ.Tests-windows-latest
19.8 KB
sha256:877d66964e5544dc4e2923f7a622338387513c83bb98e81d4cae80d599022fad
testresults-Hosting.Logto.Tests-ubuntu-latest
26.8 KB
sha256:549ee2ebefa2a87337c3205429d952711f796f575bbab25462db5b40cbf537c9
testresults-Hosting.Logto.Tests-windows-latest
20 KB
sha256:88cb793c20b4c649b5465d42bd670df5a1391aa84abb77134000037c27c4f3eb
testresults-Hosting.MailPit.Tests-ubuntu-latest
20.6 KB
sha256:5492b351805f83956e7587d5b48f6c03502bad4f1458953c8d9b954d1f5d9b37
testresults-Hosting.MailPit.Tests-windows-latest
19.7 KB
sha256:5824adecc567af21bb1b39a607ceff3efff31fcfc53ead6f265fc41a273994a6
testresults-Hosting.McpInspector.Tests-ubuntu-latest
31.5 KB
sha256:9b1acc3acbc9890efa28fd3a2495fefced8b578674d2ae450647a795f25a1c68
testresults-Hosting.McpInspector.Tests-windows-latest
29.4 KB
sha256:46331b72b19602c75ecb29ae7e200bb6ffb3be7a6cd9126304bed7bbc8690347
testresults-Hosting.Meilisearch.Tests-ubuntu-latest
26.8 KB
sha256:af31c57f326e816354ea096e226c253a1f27e50a71b8c56d353704e77c2f9c02
testresults-Hosting.Meilisearch.Tests-windows-latest
21.2 KB
sha256:40f31cd985711c5ed9a4a3e419c839a33c531c7178a458fdeae244738f02a817
testresults-Hosting.Minio.Tests-ubuntu-latest
27.8 KB
sha256:c908443d93059b8134d3609a17a055d5055eb6d39f3ea0719f0f1a4f7f299830
testresults-Hosting.Minio.Tests-windows-latest
21.4 KB
sha256:27a66d3b66278fc74ec88903f1e20aee2a5e3c6f31bb9b1cc0eab910058d11ed
testresults-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
22.7 KB
sha256:5209a36ee0d040c22e4a1a7bc0a41f69ed8ab7f05d4eb569885e84a281780824
testresults-Hosting.MongoDB.Extensions.Tests-windows-latest
20.4 KB
sha256:48d5c6e7e1ea77a600be0b7aa46b936091ae44833567fb114ba7f3afedd13409
testresults-Hosting.MySql.Extensions.Tests-ubuntu-latest
25.6 KB
sha256:b434cc7244ec5ad383350336361a07db58e590d35933de66e03d47f6f4c0a68b
testresults-Hosting.MySql.Extensions.Tests-windows-latest
23.1 KB
sha256:63be709fdcba4a9d28ac9ba16f16a804e33a7c3b7fd422bc8c2defdb5cecc5b5
testresults-Hosting.Ngrok.Tests-ubuntu-latest
25.7 KB
sha256:e3bf487be19bfbc78bf05fdfa16a540b15f48da290b7c1673222670e19d58b79
testresults-Hosting.Ngrok.Tests-windows-latest
23.7 KB
sha256:6e83d6b052560fb9ee07548c0ea86c2309f81dcadd0d95d41341594cca020981
testresults-Hosting.Ollama.Tests-ubuntu-latest
39.2 KB
sha256:cd6696e1d8cc5881cf784fa0beaa4be04da5c0025c6932858b989a1b402c1bfd
testresults-Hosting.Ollama.Tests-windows-latest
38.3 KB
sha256:78b41574f39d12bc64f999a47453e74b036bda8a506cf3a6b2ded6baf20c3cfd
testresults-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
25.3 KB
sha256:1ffafd14cbf990a6e970d782112505324d72376ba324df054bd57a780c8f374e
testresults-Hosting.OpenTelemetryCollector.Tests-windows-latest
23.3 KB
sha256:e1d543cbc4ffcd5f85b3812a8c1175b29875190b624deed866471d6486458a73
testresults-Hosting.PapercutSmtp.Tests-ubuntu-latest
19.9 KB
sha256:744f5f343541f9d184f3989cfdd8cf3596d69ed0f9c0d936f31ce434b52b4dea
testresults-Hosting.PapercutSmtp.Tests-windows-latest
19.1 KB
sha256:920ad07a6c5ddc50a0d3321631c76e06a0b59eb5b6c430327e7b54abdd38cb3f
testresults-Hosting.Perl.Tests-ubuntu-latest
66.1 KB
sha256:e5351cb4d8de05634e9f2e71753b59ea1cf1485e8bbb21ec4f8bc9a707ef5685
testresults-Hosting.Perl.Tests-windows-latest
60.2 KB
sha256:75aaed27613e2d715ae75d214d5288d08cca8166f489b0bf30b19d4f349e12c6
testresults-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
27.1 KB
sha256:03b0a0f278d14a4c77d34c7463c350753ee6f93d9a01998bb5d3b811e14ee50b
testresults-Hosting.PostgreSQL.Extensions.Tests-windows-latest
25.1 KB
sha256:96d2de39371d4784469d0560ccc382240d604e7a6691d240f9a26ec3e4d66630
testresults-Hosting.PowerShell.Tests-ubuntu-latest
26.4 KB
sha256:2e8a0042c3bafe3f3f114d7bdc3177bb726dda4bb7bd202e7231996987d32eee
testresults-Hosting.PowerShell.Tests-windows-latest
18 KB
sha256:e1e089000597564956ea688bdf4241cdbdaddce5d9182087f1afcaf7bdef8435
testresults-Hosting.Python.Extensions.Tests-ubuntu-latest
21.6 KB
sha256:d1c918ffa0121a115e71b4c93096468431597a10ddefaf5f649d38406a1b1029
testresults-Hosting.Python.Extensions.Tests-windows-latest
23 KB
sha256:f8c4f1bd8302ec4c8611d84e7b01b54c44d46becff269ed92ec462ca159fd58b
testresults-Hosting.RavenDB.Tests-ubuntu-latest
32.5 KB
sha256:1644eda25836960458903c673dcb841617a02bb67f907f67344d6ae330768723
testresults-Hosting.RavenDB.Tests-windows-latest
25.7 KB
sha256:92c7b359f04ba4f6bc8e826017c6f56d6f2ea3f6ddd0c26e037d23d42b7dcf6a
testresults-Hosting.Redis.Extensions.Tests-ubuntu-latest
22.4 KB
sha256:da64d81613657070c1abfe56f075f1539dc7637feb20b8c42f1b3892a4214655
testresults-Hosting.Redis.Extensions.Tests-windows-latest
20.3 KB
sha256:f4efa4c149237cad9c57aa04c26b5b5a7a29ed17ed191de5b65bcb5b796c36f5
testresults-Hosting.Rust.Tests-ubuntu-latest
21.5 KB
sha256:04ff3e985fd58771b8d3651676a2362b99c3500bad7bd7d2881fbe353e5e0a3e
testresults-Hosting.Rust.Tests-windows-latest
21.3 KB
sha256:12a5f35db284461e0fe4befddf224be7efc8e2679ed9f46601488ebb8136ff67
testresults-Hosting.Sftp.Tests-ubuntu-latest
32.6 KB
sha256:4c69e29d976f2cf39d0440a8280eb190cd30b9eb8044fd33ff2dc7e4e9071d41
testresults-Hosting.Sftp.Tests-windows-latest
19.4 KB
sha256:7bc5e7c1e3b720bc24ab425f9ced9d66b208aa24f65efe119b2b574745442ad1
testresults-Hosting.Solr.Tests-ubuntu-latest
23.7 KB
sha256:875023f7a0adaf5c76006799afc4992dcbcfc31b4fce2dcf44663b0a37395ddf
testresults-Hosting.Solr.Tests-windows-latest
21 KB
sha256:fbfb83147bccca8ab8e504f8e2d558a113c455b263c10b86dee86d14c1a70162
testresults-Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
28.5 KB
sha256:49de5619c136af562976f0501a690da2d839ac3115e22991ef05a508aadc7cf2
testresults-Hosting.SqlDatabaseProjects.Tests-windows-latest
26.8 KB
sha256:57bc94d9698cddff4528bdfacbf38edb1d26bbf1c3787ed96041e568ad4145a8
testresults-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
25.8 KB
sha256:5e5e9dfbb6320af21c0043b0003e532f4309391f3dfb8a197a076533e2ccc036
testresults-Hosting.SqlServer.Extensions.Tests-windows-latest
23.3 KB
sha256:45c390adae711c6aff1f861b4cbeefe0e946e94c079c60ce887868cc16ad0f19
testresults-Hosting.Sqlite.Tests-ubuntu-latest
33.2 KB
sha256:69b5ee0993939d2189354bdd7beedca309c3d82b8887a104c56c4c06f27373fb
testresults-Hosting.Sqlite.Tests-windows-latest
32.4 KB
sha256:e52ba69224895dd22a312d0b2f16654c9211d7511c7645ab7aac28bea9cfce74
testresults-Hosting.Stripe.Tests-ubuntu-latest
24.7 KB
sha256:89ed3c0089e8c68c65429825fbaaacfb9db2aebec9e633530a6b318907267b4c
testresults-Hosting.Stripe.Tests-windows-latest
24.7 KB
sha256:e60115b4bf0aa7b310f8368ec01e8bf33d1f4b816a68407b96050d091a6a8e54
testresults-Hosting.SurrealDb.Tests-ubuntu-latest
43.9 KB
sha256:0d9315ca2f8c7be1c79cf0313af994085f44a6358e52ca854de508c8bd26330b
testresults-Hosting.SurrealDb.Tests-windows-latest
31.4 KB
sha256:699687005137bdee8863aeb6e46b557148adcdf2d60e16578f0679acd255e792
testresults-Hosting.Umami.Tests-ubuntu-latest
22.1 KB
sha256:b61ea8b7d2843bda39908ad0f55aa956037c0e94acac725393b1f5dfc4756b3f
testresults-Hosting.Umami.Tests-windows-latest
21.5 KB
sha256:cd71027b5993a1d9fa13b1fd3cbd51cd1a2b55e227d733e18c7f2b67328817ec
testresults-Hosting.Zitadel.Tests-ubuntu-latest
24.7 KB
sha256:f4671aa1ccdd6c81c0db4cfd43d5fc017ad91d69e39860092d7450b6f906bd91
testresults-Hosting.Zitadel.Tests-windows-latest
23.4 KB
sha256:66573fcd814b7bdb62e46cef09227e49e7995d7e530a358ba5d0fda8705fe545
testresults-Hosting.k6.Tests-ubuntu-latest
23 KB
sha256:fb21f1b1adf232da91abbffed20ee8e37335d36e2cd8477fe4828a83e81e6426
testresults-Hosting.k6.Tests-windows-latest
20 KB
sha256:9246a0d5e56adbd649d189bd4463191c9afb7a1bb538a8512ba6f6274af698b3
testresults-KurrentDB.Tests-ubuntu-latest
24.5 KB
sha256:46f31b599c43a45f6e5f03b1a17dc0108f893cba0e7f25f0c5363b5fb8ea04da
testresults-KurrentDB.Tests-windows-latest
24.1 KB
sha256:db64a511610cef155ca39c782e542aa6d075593cf0623ffbe9ece55c17874515
testresults-Logto.Client.Tests-ubuntu-latest
6.74 KB
sha256:a36b632e317d27bfbbe0336a409efb0b4ff23988421a31d4ea1a34e007eeb51e
testresults-Logto.Client.Tests-windows-latest
6.75 KB
sha256:5c52ea44ddb85eb76cbd4bed7345fb378d3026f5c63cb3134d2e6ea213d36cc6
testresults-MassTransit.RabbitMQ.Tests-ubuntu-latest
4.9 KB
sha256:871315dbebd143ece9e46b77a3d2d00ce133a881c1dede80ec153f45a959cba5
testresults-MassTransit.RabbitMQ.Tests-windows-latest
4.92 KB
sha256:3814a3ceda90557b9aaa7c4f90c8ce4b209a034b1ade09ba608d8f5408f68a19
testresults-Meilisearch.Tests-ubuntu-latest
24.8 KB
sha256:e7f41ed0bc01303f4f97b807acdfc652a95669fe7197efedced1b1b2a16b3927
testresults-Meilisearch.Tests-windows-latest
24.5 KB
sha256:98500c45d1c12697ecf4ec853e429d2373d0722bd8da9817f299d4b5367a1553
testresults-Microsoft.Data.Sqlite.Tests-ubuntu-latest
23.5 KB
sha256:ee5e50cfcd1f8923da0c8172df7407a7012c8e9a72f0fb64218fc651bd868641
testresults-Microsoft.Data.Sqlite.Tests-windows-latest
23.4 KB
sha256:6bb2d1bc1263b2003e4dbb12d150c344d29547299f1ba72bdb4c1e2ca33b905e
testresults-Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
25.8 KB
sha256:131a29fb591cd650798817cfcfc300a86ff08ebe06e25300e2078062393e13c5
testresults-Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
25.7 KB
sha256:dbb4b52c319d64f326af9ecb8c46b99cbb086fc3cc09b3b2f646c887f5137f7b
testresults-Minio.Client.Tests-ubuntu-latest
24.9 KB
sha256:d554d7eba876d12671f6ed4ac706ad16672530034656e6fc5d0f2620351ade20
testresults-Minio.Client.Tests-windows-latest
24.9 KB
sha256:ce8b295f2529f740bc176b98865cd80774d5a3dcfafd12a2c37fd6da0ca85f6a
testresults-OllamaSharp.Tests-ubuntu-latest
32.9 KB
sha256:3c3e3f0cd2c87f30919cd6bb145dd2873fec47136863390da4f9ce9dfefd3c40
testresults-OllamaSharp.Tests-windows-latest
32.8 KB
sha256:48b1dfff5471a32ee68be2c155fc45cc4165400c24c480f911fe9ba91fe91bfd
testresults-RavenDB.Client.Tests-ubuntu-latest
8.46 KB
sha256:570a6f87fb36880abeb0f51203d559fb42e4427f5b77cbc0c1afdd8c497b6191
testresults-RavenDB.Client.Tests-windows-latest
8.52 KB
sha256:fc448fc730405ff55dcf2272377d0e04159a97db628683dc794c1830c92df20c
testresults-Sftp.Tests-ubuntu-latest
6.05 KB
sha256:e575698cbd72169e26fbb0ffb85d8c008cb2ae4fc6f2b727ff961e24929a7557
testresults-Sftp.Tests-windows-latest
6.08 KB
sha256:4dddfb69058880f83081ac733258d64d7b67fdde5671245ec92ae1ec16ca4447
testresults-SurrealDb.Tests-ubuntu-latest
24.7 KB
sha256:7f0bec321200eb101cfe8733ce1195a8991762bef1d9cf863d20d605017e44f7
testresults-SurrealDb.Tests-windows-latest
24.4 KB
sha256:d4749773ce45fcd3bede95ae834a0e37f4e2a9c76db4ee2d82f7ade3bcfd7543
ts-app-host-logs-Hosting.Azure.DataApiBuilder.Tests-windows-latest
787 Bytes
sha256:55521c0a74f046bd2d4cf2414f8bd79d1dc5ec47eb8875f9e4ccef74c48479fa
ts-app-host-logs-Hosting.Bun.Tests-windows-latest
2.8 KB
sha256:f3a99993316bfac494e0713eecc763b3dafff9fe063d5226bfa3d991d8be992f
ts-app-host-logs-Hosting.Deno.Tests-windows-latest
2.81 KB
sha256:9cb97032cd28f2136af57ff8791a9e9cc816479ea0b56902efaefddfb6b0a51d
ts-app-host-logs-Hosting.Elasticsearch.Extensions.Tests-windows-latest
2.87 KB
sha256:1ae50caa32dcf5bb1ffebd63014e9bd29a573f07d8ef8af7834ab2c183f2dd12
ts-app-host-logs-Hosting.Java.Tests-windows-latest
2.81 KB
sha256:ea24ead0cb8f8ce7e3566c734615b3adc93fa8e31cd3ce845e0469fb64d3fc35
ts-app-host-logs-Hosting.JavaScript.Extensions.Tests-windows-latest
2.86 KB
sha256:2db337249f72abceada77ad3e439e16d00013a452e288d78d5786ed48861ecf3
ts-app-host-logs-Hosting.Logto.Tests-ubuntu-latest
1.07 KB
sha256:b2ebd680ef364ab7a936235773e9181beae1c2c882afc294485ad42cb2bffc74
ts-app-host-logs-Hosting.McpInspector.Tests-ubuntu-latest
5.34 KB
sha256:3bd9accc2e6e88f475436c1eab6b6992bc13fb6a988cdd856dd59444449b2def
ts-app-host-logs-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
2.05 KB
sha256:52ee82f9851e864631433727c5479e5caae7768f66cc02228fb9dfbe151b8a4e
ts-app-host-logs-Hosting.MySql.Extensions.Tests-ubuntu-latest
2.09 KB
sha256:821497fd4ebf1c5c83eec7dd5108a106c1451be8942e74a0ee6497c009e94289
ts-app-host-logs-Hosting.Ngrok.Tests-ubuntu-latest
5.14 KB
sha256:be94b8e21e8fc6342479557e8ebc5db51ee920ca77963c8d8f16aa3be6b7b420
ts-app-host-logs-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
3.71 KB
sha256:081b7222325992318809108305a89404377a9cb254040e31df1451efe544c263
ts-app-host-logs-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
2.12 KB
sha256:aa1f94737d5e053195573bb2e007d0dd4aafefa6af89f6fd888d93836074a9f7
ts-app-host-logs-Hosting.Python.Extensions.Tests-windows-latest
2.84 KB
sha256:d4c8a7b515953b1a7c2f6301d9cd4275c22688cb3213266a2f5f5d220d90dce1
ts-app-host-logs-Hosting.Redis.Extensions.Tests-ubuntu-latest
2.05 KB
sha256:5384023d97800bb97718adc1f5d044c9e24f4dfeac341f07d0b48271c5ec6828
ts-app-host-logs-Hosting.Rust.Tests-ubuntu-latest
4.84 KB
sha256:25e34650762d6bccbca75377f2b81747f47b557a160b4ee949ac3519c43f2210
ts-app-host-logs-Hosting.Rust.Tests-windows-latest
3.05 KB
sha256:382588a2f76e78bf1e52e720cc64b34d8b71708c6cccd3c6bed4ac8f2709cce4
ts-app-host-logs-Hosting.Solr.Tests-ubuntu-latest
5.49 KB
sha256:baf7fdd38a0aff5f126d3db49605d273ad7299c8034bb980109fbe6306bb31f8
ts-app-host-logs-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
2.09 KB
sha256:13762d42dd67fc2c56e6a191d45f302e6b686a8a99c5149503359f3f79960604