Skip to content

Logto

Logto #2802

Triggered via pull request April 15, 2026 10:04
Status Failure
Total duration 12m 50s
Artifacts 268

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
0s
publish-azure-artifacts
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 142 warnings
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#L10
Microsoft.Extensions.Options.OptionsValidationException : Property CliPath: The path to the DCP executable used for Aspire orchestration is required.; Property DashboardPath: The path to the Aspire Dashboard binaries is missing.
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-e3ce62e81ddb4dc9894f5ce93cca9553/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": 5432, "cliPid": 5379, "dashboardUrl": "https://localhost:29750/login?t=ffee74a00fdc81a9283175f6dbf31905", "logFile": "/home/runner/.aspire/logs/cli_20260415T100608668_detach-child_fe276fa133844fec951372c5c0e9792d.log" } Waiting for resource 'upstream' to be up (running)... ✔ Resource 'upstream' is up (running). (4.2s) 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.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.Redis.Extensions/CommunityToolkit.Aspire.Hosting.Redis.Extensions.csproj (in 522 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 522 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.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/net8.0/CommunityToolkit.Aspire.Hosting.Redis.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.Redis.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Redis.Extensions/bin/Debug/net10.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/net9.0/CommunityToolkit.Aspire.Hosting.Redis.Extensions.dll Successfully created package '/tmp/ct-polyglot-1c54011241054fffa11f19e7480dd053/CommunityToolkit.Aspire.Hosting.Redis.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.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 / 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.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 656 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.csproj (in 656 ms). 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 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 Successfully created package '/tmp/ct-polyglot-31fc3943549147c1848cc0458c59f11f/CommunityToolkit.Aspire.Hosting.MongoDB.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.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.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 587 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-0656b1f32ae74d5ab173726b5cc692dc/CommunityToolkit.Aspire.Hosting.McpInspector.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/mcp-inspector/CommunityToolkit.Aspire.Hosting.McpInspector.AppHost.TypeScript/apphost.ts", "appHostPid": 5788, "cliPid": 5735, "dashboardUrl": "https://localhost:29750/login?t=5bd799fc4729f183ef3a6556e8a34c4e", "logFile": "/home/runner/.aspire/logs/cli_20260415T100624989_detach-child_e997e093dfb549c098fb7ce0ea5ab89a.log" } Waiting for resource 'inspector-default' to be healthy... ✔ Resource 'inspector-default' is healthy. (9.7s) 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 1.02 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 1.02 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/CommunityToolkit.Aspire.Hosting.MySql.Extensions.csproj (in 1.02 sec). 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.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.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.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/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/net8.0/CommunityToolkit.Aspire.Hosting.MySql.Extensions.dll Successfully created package '/tmp/ct-polyglot-ade31c1c9c6045fe9fc94db66953b1a3/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 d
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 463 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-29a3eebffe52454ab7df8ecaa86972a6/CommunityToolkit.Aspire.Hosting.Solr.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/solr/CommunityToolkit.Aspire.Hosting.Solr.AppHost.TypeScript/apphost.ts", "appHostPid": 7193, "cliPid": 7138, "dashboardUrl": "https://localhost:29750/login?t=e44ce4291514209524199aec5bb02602", "logFile": "/home/runner/.aspire/logs/cli_20260415T100637300_detach-child_163c6b5a974b49399096f16a604ef62d.log" } Waiting for resource 'solr' to be healthy... ✔ Resource 'solr' is healthy. (10.4s) 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.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.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 888 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 889 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.csproj (in 888 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.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net8.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/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.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 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 Successfully created package '/tmp/ct-polyglot-a3713ff619194826b008f531f825be87/CommunityToolkit.Aspire.Hosting.SqlServer.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 dotnet
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 506 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/net9.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 Successfully created package '/tmp/ct-polyglot-27ca0db742934d9a8a431d77176d517c/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": 7602, "cliPid": 7537, "dashboardUrl": "https://localhost:29750/login?t=bc40e1aa7407b4654d230de3bb33fa37", "logFile": "/home/runner/.aspire/logs/cli_20260415T100626362_detach-child_117e7eb29e8a4dc9841d596c119388b0.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.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 357 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/net8.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 Successfully created package '/tmp/ct-polyglot-030da40cd48e4cbd95d05b966a9deb1b/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_20260415T100627738_detach-child_844caab368f54e5ba3abaf929b1e5047.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.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.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 573 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/CommunityToolkit.Aspire.Hosting.Flyway.csproj (in 575 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.csproj (in 575 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 571 ms). 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.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Flyway.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.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/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/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.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.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Flyway.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-76e7b04bbd1e4ab8ae54d29a49853389/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)
run-tests / Hosting.Sftp.Tests-ubuntu-latest
Process completed with exit code 2.
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 676 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-aadd76de6f7e4ef39543e2fd7c884cbb\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_20260415T100849422_detach-child_ade87063bcf245a18747c65e9fca452d.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.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 511 ms). 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 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 Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-d60776a76cea45589e14cfdc57475df7\CommunityToolkit.Aspire.Hosting.Elasticsearch.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_20260415T100853081_detach-child_3068f703ea41426abeec98b638150abb.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 509 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-26dd4d65e9a74012bf25a947935748fe\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_20260415T100900733_detach-child_dd5210169c624607a028f011b574d211.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.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 571 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-b78e59beeee7404babf4b2845aebcd4e\CommunityToolkit.Aspire.Hosting.Deno.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. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260415T101115104_detach-child_8ae476ec93b14f7e9896261e35774de3.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.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 389 ms). CommunityToolkit.Aspire.Hosting.Java -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\bin\Debug\net8.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\net10.0\CommunityToolkit.Aspire.Hosting.Java.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-83627d1504ba46a2a0b8ed869f4e6060\CommunityToolkit.Aspire.Hosting.Java.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_20260415T101216427_detach-child_05607aedc5544c1aaedd8a801155becf.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.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 541 ms). CommunityToolkit.Aspire.Hosting.Rust -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Rust\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Rust.dll 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 Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-886bfba0adc942cc9f5717e5728f8c66\CommunityToolkit.Aspire.Hosting.Rust.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_20260415T101216725_detach-child_58d02f3f1403456593c9b6c4032164d4.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.Golang.Tests-windows-latest
Process completed with exit code 1.
CommunityToolkit.Aspire.Hosting.Golang.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.Golang.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\golang\CommunityToolkit.Aspire.Hosting.Golang.AppHost.TypeScript\apphost.ts -PackageProjectPath D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Golang\CommunityToolkit.Aspire.Hosting.Golang.csproj -PackageName CommunityToolkit.Aspire.Hosting.Golang -WaitForResources golang-root,golang-cmd -WaitStatus up -RequiredCommands go' failed with exit code 1. Standard output: Determining projects to restore... Restored D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Golang\CommunityToolkit.Aspire.Hosting.Golang.csproj (in 552 ms). CommunityToolkit.Aspire.Hosting.Golang -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Golang\bin\Debug\net8.0\CommunityToolkit.Aspire.Hosting.Golang.dll CommunityToolkit.Aspire.Hosting.Golang -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Golang\bin\Debug\net9.0\CommunityToolkit.Aspire.Hosting.Golang.dll CommunityToolkit.Aspire.Hosting.Golang -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Golang\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Golang.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-d5eca248b8b4417e96724aa8acaa3b84\CommunityToolkit.Aspire.Hosting.Golang.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_20260415T101251845_detach-child_bb39986126c643f6a8255d2c541bf174.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\golang\CommunityToolkit.Aspire.Hosting.Golang.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 520 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-4f68d81360844ab18947372eab501b59\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_20260415T101300276_detach-child_62be337e25994f94bfa48dc1309db59a.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 / 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/[email protected]. 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
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/[email protected]. 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 / 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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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/[email protected]. 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
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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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 / 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/[email protected]. 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-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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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/[email protected]. 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 / 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/[email protected]. 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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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 / 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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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 / 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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
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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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/[email protected]. 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 / 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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-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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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.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/[email protected]. 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 / 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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/[email protected]. 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-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/[email protected]. 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-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/[email protected]. 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
950 KB
sha256:6bf05a470b27a62c703142fbf439b8340c9c27a86452b5353c014ed40493b6b8
binlog-GoFeatureFlag.Tests-windows-latest
961 KB
sha256:372f35efb682e011daaddb3d23f2a2405b6c1743e1ccb64396349c6933c2b7a4
binlog-Hosting.ActiveMQ.Tests-ubuntu-latest
1.41 MB
sha256:7a46a889346b4de231bff12e163edde0f19fb374b0cfe4937f12f8fa8c6b2a02
binlog-Hosting.ActiveMQ.Tests-windows-latest
1.42 MB
sha256:fd12955cf7dce059f6390d950e97ca9dcb7319caad5a1b4fffb1d68d3866c148
binlog-Hosting.Adminer.Tests-ubuntu-latest
2.08 MB
sha256:171b057e6b55e8209fa3f27c4140ef925a3489ca34e5fd3a02189461c81b9c07
binlog-Hosting.Adminer.Tests-windows-latest
2.11 MB
sha256:22dbe11650a5657abe72fa5a6cc19411cb370ec9696ca82f24c2ac55f866cac6
binlog-Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
1.36 MB
sha256:bc74b5fb4c8f59fe6a182f4f5a5c771f13be09f412fd6f9930be9d1cbb50123d
binlog-Hosting.Azure.Dapr.Redis.Tests-windows-latest
1.37 MB
sha256:624c139782b906d56b8307e86cd357ec6bdf9817e47705d84370553c7e411a0f
binlog-Hosting.Azure.Dapr.Tests-ubuntu-latest
1.16 MB
sha256:5d1530cc6645c896621ebb6d73e0da73b7707d133550adad8e39870daceb7053
binlog-Hosting.Azure.Dapr.Tests-windows-latest
1.17 MB
sha256:2052a6889f0f86f2806c157c9b84d7708c6730d1a9952cb9074d95c1288efb09
binlog-Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
1.45 MB
sha256:2749a5134e03348bc9a1a4d828dc66f92e6d41425d69b66fe5335a332e71da5f
binlog-Hosting.Azure.DataApiBuilder.Tests-windows-latest
1.46 MB
sha256:fe05e84afb5949477ce1275736ca89626fa4ba83023825d36dcb6afc3f59d641
binlog-Hosting.Azure.Extensions.Tests-ubuntu-latest
1.11 MB
sha256:f8199f69a1dcc23a64ba805055e1b315f869182bd0fd7073501e1729538baf61
binlog-Hosting.Azure.Extensions.Tests-windows-latest
1.12 MB
sha256:42577d82750ca456e963d8500944b85d2782424cfe1adbbc72b33cdc74b44ce8
binlog-Hosting.Bun.Tests-ubuntu-latest
1.07 MB
sha256:dc1ef90a948335f7757d24f4e27444304c1ce02023bd9e20cc0cb978c539e449
binlog-Hosting.Bun.Tests-windows-latest
1.08 MB
sha256:5ba7ec1be16c85e1c37c64c01465a4d8a16cf822f7abc8476f1af4e098fd322d
binlog-Hosting.Dapr.Tests-ubuntu-latest
1.65 MB
sha256:fb9bea812f1dcc02135b7cfdc0c9925941b21f81788536b3d2d6595d7fb0730f
binlog-Hosting.Dapr.Tests-windows-latest
1.66 MB
sha256:8fc4ab9c73d469c5c41748e3a384908eb8487a019a16a2af1abe3a13f7d7eeea
binlog-Hosting.DbGate.Tests-ubuntu-latest
2.57 MB
sha256:510336313835bd0383786181e577400cbf166cfd3331b6668baa29569ffbc710
binlog-Hosting.DbGate.Tests-windows-latest
2.5 MB
sha256:ee788ddc0557fe751990c0ef3468c1d64e19acb3dc89c13715f7cfc9c8623afc
binlog-Hosting.Deno.Tests-ubuntu-latest
1.07 MB
sha256:4bcd2fa3650a07323b01319d4f87b8c71c6609a67e16e840572eec298ca553fe
binlog-Hosting.Deno.Tests-windows-latest
1.07 MB
sha256:97661d8992d1ff5f1bcb1edc4eda28d9713a4a3c84cfd7e6d5ad766170f2cc42
binlog-Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:d2e0a09853e4b50ae6136cf79a5efcfd4c946b34c8e7a2a2228b58dac4a06ec6
binlog-Hosting.Elasticsearch.Extensions.Tests-windows-latest
1.09 MB
sha256:c7cf451f5b312778f10e2eda51f42d932880480b8ff73c59a4c9cc90fd3f6f6c
binlog-Hosting.Flagd.Tests-ubuntu-latest
1.07 MB
sha256:07eeb6d2f807dc0b6f274f09aee066bfd13f5ac195d6b3f592d208449b7c61a1
binlog-Hosting.Flagd.Tests-windows-latest
1.08 MB
sha256:55a0250f28e2602068c72b8a8233d38f1c2ec6582de67db49504ba091a5ed34f
binlog-Hosting.Flyway.Tests-ubuntu-latest
964 KB
sha256:808837d15afe104e4c3782a57c61325ab60b7da700c4c2e957d234555568644e
binlog-Hosting.Flyway.Tests-windows-latest
977 KB
sha256:16257c0ffeacdff0703534cac1a3fceb39fd12f513f33e5feecd44931dae059b
binlog-Hosting.GoFeatureFlag.Tests-ubuntu-latest
1.58 MB
sha256:e5257da5f2d2c8e9a9a643d4e31592490248954529621c48915a3f6d539a68f1
binlog-Hosting.GoFeatureFlag.Tests-windows-latest
1.6 MB
sha256:f312619480124cb25223607660b31cfa38d85edcaa8db1fa7778d389875a1b6d
binlog-Hosting.Golang.Tests-ubuntu-latest
1.07 MB
sha256:db6a75de7ab9dd76d70e831d552754adc0ed621877f3431de3a2431a3948a74d
binlog-Hosting.Golang.Tests-windows-latest
1.09 MB
sha256:b907b5afd9bc6a69bb5671e3f0f461e77fa6b6343062a07de682251ed4dbd1b0
binlog-Hosting.Java.Tests-ubuntu-latest
1.56 MB
sha256:176f28680e4273f9830f806429aa78ff9e60ab57ecc155dfc00140469bfca2c9
binlog-Hosting.Java.Tests-windows-latest
1.56 MB
sha256:2886c6e7fe7633b9e1d3a7442ffc94bc7b18f707b09717ef589df9bbcec3781f
binlog-Hosting.JavaScript.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:ab9822b8df755453d37fc66a7b635a24e2e476932500cc9b82a63ea985b64450
binlog-Hosting.JavaScript.Extensions.Tests-windows-latest
1.09 MB
sha256:9cec6d4723f9d7c8dd7e6693423857476847fe215f18887a07d0143abd6ede5f
binlog-Hosting.Keycloak.Extensions.Tests-ubuntu-latest
974 KB
sha256:47b8f0e10dfee8a7ffab3b9633c3538472c7d1e485b4bfda1d93dedad4522729
binlog-Hosting.Keycloak.Extensions.Tests-windows-latest
984 KB
sha256:3531262a9eed9254145343db4a784a143af190ac1b758f517c561d1dd03199b5
binlog-Hosting.KurrentDB.Tests-ubuntu-latest
1.11 MB
sha256:c63afa9f432c4ce03a0471c70b8fe90f6fa3fd684fc29b6bb13c7eea523bcab6
binlog-Hosting.KurrentDB.Tests-windows-latest
1.12 MB
sha256:ef16711a7cfb8945f46fd4cee26adebfece272374f1a00b3c9597d65052e8f62
binlog-Hosting.LavinMQ.Tests-ubuntu-latest
1.41 MB
sha256:ce4777d5ce1a2287d81edd6b6f2133669dfd335ca063901e913a76648218e381
binlog-Hosting.LavinMQ.Tests-windows-latest
1.41 MB
sha256:83584924e89653ee916b5613231ee157b62706979dd56aa4eb4853486d78eaaf
binlog-Hosting.Logto.Tests-ubuntu-latest
971 KB
sha256:9bbf323539943f72ae3e02dbe8447680218bccb6a9966577a48bc7aa27e3a42b
binlog-Hosting.Logto.Tests-windows-latest
983 KB
sha256:316cefdd1d5073f697eff7f256ece01a0323c8b8ca082d397b9011daf95c9033
binlog-Hosting.MailPit.Tests-ubuntu-latest
1.4 MB
sha256:95aa2a37001fe975f3bf6e0c89c20296734183932a1248f608ed37b5edfd2286
binlog-Hosting.MailPit.Tests-windows-latest
1.41 MB
sha256:0c9bf82d1274f3937f7ffd10cdfa97168a94b50b6285c53444f2c363b0c1b288
binlog-Hosting.McpInspector.Tests-ubuntu-latest
1.28 MB
sha256:6a3c0d03123cbd0b2f087ec44c6d0bb27af2912bf2d4e78a5585f1b3ad1c110d
binlog-Hosting.McpInspector.Tests-windows-latest
1.3 MB
sha256:203d5b2a8332af3e1852295301b69999ee20e215070903769ad2cf22e93155f5
binlog-Hosting.Meilisearch.Tests-ubuntu-latest
1.58 MB
sha256:051d5e378375c97efa608cf083b31a2fc21c9a0138824b0972993d24608d7d23
binlog-Hosting.Meilisearch.Tests-windows-latest
1.58 MB
sha256:91b1a7a0decab4ad9604847e445307f60d636f5d91c7b7286b292f7e5cc59669
binlog-Hosting.Minio.Tests-ubuntu-latest
1.57 MB
sha256:49611c222a26e8fccf686ad32800ced13c734eca5b0bb2c0a06bffd196b18fa3
binlog-Hosting.Minio.Tests-windows-latest
1.58 MB
sha256:4fda4db3a2a1779414e78617f551b7cb94bbe71b353138b4f61d44f061be5ba8
binlog-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
1.27 MB
sha256:af3887ae74d0217487e38b609744df3587a4451d2f236106bf2408ba59303477
binlog-Hosting.MongoDB.Extensions.Tests-windows-latest
1.28 MB
sha256:38bc9e0b163b3df5b42a68a83d5a46e95761bfc29a89ae824b69722b922aa142
binlog-Hosting.MySql.Extensions.Tests-ubuntu-latest
1.44 MB
sha256:8768ec1143010062353725d6cc3e735fc40ec57b42053b98880f210abad6052f
binlog-Hosting.MySql.Extensions.Tests-windows-latest
1.44 MB
sha256:8924f0c8882c68282861b2a6d5d2678ce55973a07365316cbdec93caa26f057d
binlog-Hosting.Ngrok.Tests-ubuntu-latest
1.39 MB
sha256:ae3f74425865993b2db8935e0d9c9a45d4882f83a1bb730073ba9439210ff652
binlog-Hosting.Ngrok.Tests-windows-latest
1.41 MB
sha256:564f6b71aa7a8af33a364ef81deea75454b06859345c6f02559ccb9e44c6d525
binlog-Hosting.Ollama.Tests-ubuntu-latest
1.22 MB
sha256:dcd485ca1500f512c48bbe413e9673c6185b3a1e88a829fa8adbac2dab09c817
binlog-Hosting.Ollama.Tests-windows-latest
1.23 MB
sha256:fa91c164725c6d7165aee0ba988409d73045d5ddea9074196656dc2eeada86b0
binlog-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
963 KB
sha256:008e1e186ec3b5b861bd0c21fe670d4e26a1ae934a81bc4757d125888500a05d
binlog-Hosting.OpenTelemetryCollector.Tests-windows-latest
978 KB
sha256:0c7e10648c66c0e8d9bd67056e835e63b5b7424983301e2e40fd5ad07fb43a89
binlog-Hosting.PapercutSmtp.Tests-ubuntu-latest
1.4 MB
sha256:2779130ff034d4209f46e333a20a1dd4ed203138b56c5285e0b104f53c26d370
binlog-Hosting.PapercutSmtp.Tests-windows-latest
1.41 MB
sha256:09c8e004c53fc4fd5777b8e6a699bdd89e5475a14053bfaed7722b0411fc28f0
binlog-Hosting.Perl.Tests-ubuntu-latest
1.06 MB
sha256:49e25b13287f26338b2d756b85b974b983b702e93703994dabb97386a2f4b126
binlog-Hosting.Perl.Tests-windows-latest
1.08 MB
sha256:cba5966d0370362ab7bff8c39d38e727cc9dccca430aed9e7c03a8ff2876cb12
binlog-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
1.57 MB
sha256:bb17b8782f83a83dc9886dc36fc6b440b5ebdb1fc8de8b12ba52b777f7ceca0f
binlog-Hosting.PostgreSQL.Extensions.Tests-windows-latest
1.6 MB
sha256:c3083cac7c9d2c2b4556ec033c231fe4c10ebcdbe2d16cf43f32d2d947f11292
binlog-Hosting.PowerShell.Tests-ubuntu-latest
1.31 MB
sha256:b8894126e8b388a4606ff2e1c754c0c9c2cbeae582a2d25f80b4dbc4fad3123f
binlog-Hosting.PowerShell.Tests-windows-latest
1.31 MB
sha256:ea5838915ffaed4e769e5b75488cf36dffc77ec63fde143c4c78a693626c30af
binlog-Hosting.Python.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:9defde65446274748bf40f4cb9f3b668e6c64746496bd998eb0c72ba582e9117
binlog-Hosting.Python.Extensions.Tests-windows-latest
1.08 MB
sha256:5e21a9894cd0a03ffd966f1d668349cd6a87e51921bf212bd0c4007cc22317ba
binlog-Hosting.RavenDB.Tests-ubuntu-latest
1.6 MB
sha256:a0ed05c046d75767f7ef177faa816cdc7e605e867a7d29b21542f1fc573fc810
binlog-Hosting.RavenDB.Tests-windows-latest
1.61 MB
sha256:054a9cbd2ef49c91aa3b07b35f169ca1c39da0eb0423c94e203b01599f8722c5
binlog-Hosting.Redis.Extensions.Tests-ubuntu-latest
1.26 MB
sha256:49d0fb0f97266f100de879b5ea968755eda09458b0a0c05fb462a54d43865540
binlog-Hosting.Redis.Extensions.Tests-windows-latest
1.26 MB
sha256:f5b5a0226ed375af35fa087104b02b237f025f74f93b71cd8b8daaf50b7b0fed
binlog-Hosting.Rust.Tests-ubuntu-latest
1.06 MB
sha256:803158105aeb690bcfd38549917eadd1e9e2192a2b1735943aee2cf5cd6acdfd
binlog-Hosting.Rust.Tests-windows-latest
1.08 MB
sha256:70f6189a7bcd814c32f65565e7e515011efbbeb6be8e3df5627209e5ecc3222a
binlog-Hosting.Sftp.Tests-ubuntu-latest
1.59 MB
sha256:3fec3d9286a824967a7d6b0094508a1e2a351d7ebd15b67b299f8a3949f58005
binlog-Hosting.Sftp.Tests-windows-latest
1.59 MB
sha256:2e9bc74378773939e944c744fd16ce4d45eda84e580ba7602ea1eb936c20b1d0
binlog-Hosting.Solr.Tests-ubuntu-latest
1.05 MB
sha256:f3aa24af8eb99865c053abfbf5e4252e50705ac56af61a9f73a0775345a7ed26
binlog-Hosting.Solr.Tests-windows-latest
1.07 MB
sha256:e5603b19b27f6d93c36285fda05021256e81fd661c25373424c10561d15f68b5
binlog-Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
1.26 MB
sha256:50537283668cb82e358512282a5823ce871fe311ac6fce86b627376c7fac9c09
binlog-Hosting.SqlDatabaseProjects.Tests-windows-latest
1.28 MB
sha256:eefcf57155d99aca734e6dd07236304f5f534500e77c82ea006fe7e837ca08bc
binlog-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
1.49 MB
sha256:613eda6aa89034afee03251fef5d398e51bcd25ee5b4fd3293b14618c181fe80
binlog-Hosting.SqlServer.Extensions.Tests-windows-latest
1.49 MB
sha256:2cd6ce2891abae2c32cc82fb013c70f3d52eead55796dc0e461d96f2ce6257f8
binlog-Hosting.Sqlite.Tests-ubuntu-latest
1.78 MB
sha256:791a07198bac49bffc3b2d0e1b6de5ad542570ac120bbcdb460ee9102e57eb90
binlog-Hosting.Sqlite.Tests-windows-latest
1.81 MB
sha256:c4153000d62c29bb771d0c9553e68587b0cf786cf49ae84f56e9e39a044538d4
binlog-Hosting.Stripe.Tests-ubuntu-latest
1.27 MB
sha256:b0e7f935ee8746e475fca7a8f62fedf5a7fcee981c0cb02855558ee512b43c7b
binlog-Hosting.Stripe.Tests-windows-latest
1.29 MB
sha256:ad5e6a208cfaa71bbd6f529853d9e3214908ecb0fe60a87db3b21ad76fe10b0e
binlog-Hosting.SurrealDb.Tests-ubuntu-latest
1.61 MB
sha256:e46eca46ad23dc7f3732782c8ee7e42b5dc90c74ed994aad2cb3169436916eb7
binlog-Hosting.SurrealDb.Tests-windows-latest
1.61 MB
sha256:160253a2e5442b01ad3acbf914f88978ee156b4b6e4fd925f2f1cbd97390a3cb
binlog-Hosting.Umami.Tests-ubuntu-latest
1.06 MB
sha256:916b6b2af9a4dd9885b9a4c56a2028cb9bcef03a354659a23a9302000f9f0b4c
binlog-Hosting.Umami.Tests-windows-latest
1.07 MB
sha256:da07c02c85b7fc7318020381162ea389ca45bab08bfb0289a3b3a7e3b9680617
binlog-Hosting.Zitadel.Tests-ubuntu-latest
1.06 MB
sha256:28377c69baa849b1c8c650852c5e0d464d8563139450d8cc499adc2b0207e325
binlog-Hosting.Zitadel.Tests-windows-latest
1.08 MB
sha256:c71f5fd887fd15a8e600cb68acf70e0cd799a3bb529e4058878dba57a61f71da
binlog-Hosting.k6.Tests-ubuntu-latest
1.39 MB
sha256:82136cfa17ebbc8dc7e7b8a6b6dc058aa97a3c4a133fe7054b8ad700c82af378
binlog-Hosting.k6.Tests-windows-latest
1.4 MB
sha256:fc5a07d8a460d1e9a277aac6e3bb3ae29a89d2d6731b202b387417016c966d7e
binlog-KurrentDB.Tests-ubuntu-latest
954 KB
sha256:c26c4155d55f90d654048e066a58d93ea319d130803b99b820f0c9f18fcb3c5d
binlog-KurrentDB.Tests-windows-latest
964 KB
sha256:0f55b628e8af880578958fdd60365def6c42eb41aaceddf86c7b48157bd62d5d
binlog-Logto.Client.Tests-ubuntu-latest
773 KB
sha256:8541683636a116c6e3c3c41991baf9588614e76c8d8d7d39652e52c6a604c918
binlog-Logto.Client.Tests-windows-latest
784 KB
sha256:607fbb49e211926de2e60a5f6eb00514891d548b063a3f3440b4b8997f2d229c
binlog-MassTransit.RabbitMQ.Tests-ubuntu-latest
938 KB
sha256:220f6136e97a02a6e71441bfc74d39dd43450845befa4cd12a4b4be1012ae1a4
binlog-MassTransit.RabbitMQ.Tests-windows-latest
955 KB
sha256:c47cf8252a7f69345e49453f9fbe8617c48c7381e4d57c70e4b5804ecc548b13
binlog-Meilisearch.Tests-ubuntu-latest
946 KB
sha256:3db681acab8e75326c96357bdd24da63cf307d6529cb2d407ac5118b6aa733f3
binlog-Meilisearch.Tests-windows-latest
962 KB
sha256:f54ff12c827c410d9f761e6319d446c867681e36860180d7d922954c1221a738
binlog-Microsoft.Data.Sqlite.Tests-ubuntu-latest
944 KB
sha256:9fdf53bfb3349b5e8e51524eab610b653a8ddd8060e3a21e1ef9556a69d18640
binlog-Microsoft.Data.Sqlite.Tests-windows-latest
961 KB
sha256:2e1015fb79e3b1143e6d0ac38d13d048700e3adb4a6d46afd0dded62e3578b0c
binlog-Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
959 KB
sha256:d61b5e4eb9068c62125d94811ba722e29acfd9a32b94c425c8825485f6519917
binlog-Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
987 KB
sha256:c20550789293e423df204cffe1a40e4ab09537e006b60aeaf655f78f2a0d6ee5
binlog-Minio.Client.Tests-ubuntu-latest
1.1 MB
sha256:7930c9e1c9eae3bbb88e60546e7ae3018ea5f3e6e2c49d5f35ea1f045aedd4a5
binlog-Minio.Client.Tests-windows-latest
1.11 MB
sha256:b0e6713c5b7d7b1e37bf72d3c7788fbd6ee23da18c0824c0403eee142afd9ea3
binlog-OllamaSharp.Tests-ubuntu-latest
949 KB
sha256:932bdde240b71c9c9da2626d775258b70fa118fac450f146bfd12e20d5dfed72
binlog-OllamaSharp.Tests-windows-latest
962 KB
sha256:63302a85495d8528ff46e940899ef88676c6d0d2bfc732df3b5e8a4c85fd96bf
binlog-RavenDB.Client.Tests-ubuntu-latest
837 KB
sha256:22192897952534226904bfdb4c48e5d5053eaf13c81cd95f34b2a9143b07767e
binlog-RavenDB.Client.Tests-windows-latest
845 KB
sha256:31b8c3214b8f3db9beb4f87f06c190817e19d7642473d587f3a5afff66e36bc7
binlog-Sftp.Tests-ubuntu-latest
938 KB
sha256:d03600533815a16ccf14dc72b5e6226d63688c9dfd1056be96203378d7c8427e
binlog-Sftp.Tests-windows-latest
949 KB
sha256:def4a587e3c37ea5edae44f148bb9d392b4c7a00e5dfe894b086fbeb8fcd80fb
binlog-SurrealDb.Tests-ubuntu-latest
957 KB
sha256:bba006ea19dc3a1ab40ba41b98f8e72f9d4cbf5e55e2ec666c16d090ab4d6687
binlog-SurrealDb.Tests-windows-latest
969 KB
sha256:47ac6ad5d7d3ca59d4fe1a4c25963a980293ffead8f8002a8595a6d07d55b32d
npm-logs-Hosting.Bun.Tests-windows-latest
115 KB
sha256:0a4868d1914e3b5753bc121e97770eb4c8f3d2b2a260154ef87c7608ef55d719
npm-logs-Hosting.Deno.Tests-windows-latest
114 KB
sha256:2ab084cd3a1897173417c2794d89747b4c4eff43349395e28a1df00c6ff916d9
npm-logs-Hosting.Elasticsearch.Extensions.Tests-windows-latest
115 KB
sha256:ee0b384c8b93568be4aa5bb4ca17a651a5dc13ac8161db858a0d780160d67e1d
npm-logs-Hosting.Golang.Tests-windows-latest
115 KB
sha256:6331b37ed193638b4f03bc71ff9cc02890b6bd19cba64f9c1660e9f5c75baa8a
npm-logs-Hosting.Java.Tests-windows-latest
114 KB
sha256:48b4521295963e0b0b44dca602564828a5cc20d9d661c701060d4ed1257c0064
npm-logs-Hosting.JavaScript.Extensions.Tests-windows-latest
215 KB
sha256:88dc08ef56872582403cd513e7d64798d2db6116b058680a71a7058910a3bb4a
npm-logs-Hosting.Python.Extensions.Tests-windows-latest
114 KB
sha256:cbb3992de9ca97eee3c35227f6cbc146cef8660a875e3502384a286a1816bb7d
npm-logs-Hosting.Rust.Tests-windows-latest
114 KB
sha256:088c4eea6e00090f81ab270250140eb86b31e39c2a56291defce1c0c41f7a975
testresults-GoFeatureFlag.Tests-ubuntu-latest
24.6 KB
sha256:19ee61ad32362689833c943ae9ee6ebe8dfd47a26037d67f5943cb7e6cf0ab26
testresults-GoFeatureFlag.Tests-windows-latest
24.4 KB
sha256:d1f142946a0cfe5c1d6332ca1d4e02b45f6ec639b2e67ef9f1b0cb1577e2e67f
testresults-Hosting.ActiveMQ.Tests-ubuntu-latest
26 KB
sha256:2e7d60e5104b97d4a8574375c0b8615c3aea3f9234f4fe35676597f2835227fc
testresults-Hosting.ActiveMQ.Tests-windows-latest
22.4 KB
sha256:a3a5d09cf5690d77b7ba752e47bf5b7d8b4d3d97c93f12beee7222431498c51e
testresults-Hosting.Adminer.Tests-ubuntu-latest
27.2 KB
sha256:32de9ddc5bf47f075362cd3bfca18971242be33d162e166f993811bc86d7ac0a
testresults-Hosting.Adminer.Tests-windows-latest
25.7 KB
sha256:bd203808c3a583089b731514c8db70e24e547f6a6e9e5a10212b29f75a9dd1dc
testresults-Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
49.4 KB
sha256:f35ec523d9562cf5f07a8538e65929cc56a769880c9404febed3eafb90f14408
testresults-Hosting.Azure.Dapr.Redis.Tests-windows-latest
49.5 KB
sha256:048e66e2e8fd9d5d379c1e885aa728835601539daf2f584d05650a252987b3e1
testresults-Hosting.Azure.Dapr.Tests-ubuntu-latest
47.4 KB
sha256:f630ab9059f19f78cc589dc17beb9daf0c2af6d90bdd5d97cfecb3a0eaa951f4
testresults-Hosting.Azure.Dapr.Tests-windows-latest
47.4 KB
sha256:c09c78933aa790ac30b5f75e7241ee2a5b9c7d06cb678ff0ec9f0c153ba52a69
testresults-Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
23.9 KB
sha256:6a20d528e30beefd3e6767258cace770bea96dbc043223447150db6d2285d6cd
testresults-Hosting.Azure.DataApiBuilder.Tests-windows-latest
20.1 KB
sha256:d2b2a7150ecb94fed6c782bc18ef56f94f29970fbc1e391d52a8b97b64ae625e
testresults-Hosting.Azure.Extensions.Tests-ubuntu-latest
20.5 KB
sha256:2ab89283fb23b6cd15935086147ef8f6b62acf82e38277d236749fe5a8e9a0f1
testresults-Hosting.Azure.Extensions.Tests-windows-latest
20.1 KB
sha256:d8f49208fc8103c4761b6b33c59b271275a14e440c9005d2de47b8bad7c104d5
testresults-Hosting.Bun.Tests-ubuntu-latest
20.9 KB
sha256:d2171e8f28333e4ac4e0b3dd83179cb9174077f12a305e82350611cd22b2929b
testresults-Hosting.Bun.Tests-windows-latest
22.4 KB
sha256:06bda66cfaf33121fb78093a1c6cbc8ad79c211739cdb13272204b8c56dea535
testresults-Hosting.Dapr.Tests-ubuntu-latest
47.2 KB
sha256:b2d11064d7feca80669e497b3209042eafcc6d34056eaced19297e9973e4bba2
testresults-Hosting.Dapr.Tests-windows-latest
47 KB
sha256:5324b9c5dbd1429d3f8130da2a30cfca21c3c24b5206645bab13b042ccb381dd
testresults-Hosting.DbGate.Tests-ubuntu-latest
29.4 KB
sha256:7d4a30e7b1f314c1c4f571adeedda8918405e19d3d10a684fa9a668fe48eb33a
testresults-Hosting.DbGate.Tests-windows-latest
27.8 KB
sha256:899bdc6d0de3040147023b1b73214b598a9dc4bdaa2bfc668e687aade84087df
testresults-Hosting.Deno.Tests-ubuntu-latest
20.4 KB
sha256:f105944053779f4f3fb9522ab1c6c46103d5b79ad785cd7f908207277ccde1ac
testresults-Hosting.Deno.Tests-windows-latest
21.8 KB
sha256:6edb92d6efb3a908f2d59e27024b9ee33602092be66aaa2d4fb82764efb673d6
testresults-Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
21.3 KB
sha256:babf8e93d019f4ac05f2f39a55f524d482b90412aa1c405cf1421607223cb075
testresults-Hosting.Elasticsearch.Extensions.Tests-windows-latest
22.3 KB
sha256:8bdd9fb0056e19c81091dbdc3018aceae0c3b94e058c82df9bea083a30a603f3
testresults-Hosting.Flagd.Tests-ubuntu-latest
22.7 KB
sha256:89d49d7ed185079217c78a37f905f44ffe54b6ad4edea0f431a4ee1d05aac8ba
testresults-Hosting.Flagd.Tests-windows-latest
21.7 KB
sha256:cd5abf154686195d261aeac71d2ea3f4dc422a36311a6cff83bc43d0390cb542
testresults-Hosting.Flyway.Tests-ubuntu-latest
19.1 KB
sha256:e6e028800c4ade78c491521d5da759e2f091e0d28d1b78a77ac6fdf3576a9eca
testresults-Hosting.Flyway.Tests-windows-latest
18.7 KB
sha256:880acce09331265c3fc87d6cbd360f2d888eda759f2d2c55de94b636285c281f
testresults-Hosting.GoFeatureFlag.Tests-ubuntu-latest
26.3 KB
sha256:81f6afcc6536010c6ae5ba156818d61e8360f1bd9c5ed0bfed7853ca93c73eed
testresults-Hosting.GoFeatureFlag.Tests-windows-latest
21.2 KB
sha256:6b9d9e9c2099aedd07f4b71d4b535dda7ca9f1d47ce46e81c315549efc13d966
testresults-Hosting.Golang.Tests-ubuntu-latest
24.3 KB
sha256:8d7dd0f7ddc75eac324c5115fd52eb97603ab5e182f9dd1e8e239b0b745fbab6
testresults-Hosting.Golang.Tests-windows-latest
25.7 KB
sha256:4864cb684f4428cf203da63ed8e90498e738f5834fe1e5a92fa1ba237b5a1b2f
testresults-Hosting.Java.Tests-ubuntu-latest
33.5 KB
sha256:ae38d76eb465947f55cdf499f7fc17ddc9d19fb8f840681f2a787fe67227bb73
testresults-Hosting.Java.Tests-windows-latest
30 KB
sha256:a8f5c2fb1d94a753d9082858400d80517a1d592a375824abba887c8ac7c579a7
testresults-Hosting.JavaScript.Extensions.Tests-ubuntu-latest
29.1 KB
sha256:10c344c62e30f9c589ce49a70f2821320c49f509668898f4b0d70866b2d2a698
testresults-Hosting.JavaScript.Extensions.Tests-windows-latest
31.2 KB
sha256:dd13250bf83e1816a79417cba4657f0f6cec1ed860d5558cf8d35bc2fb3c1167
testresults-Hosting.Keycloak.Extensions.Tests-ubuntu-latest
20 KB
sha256:4770b73294ce4b7fae8d5e75f372c13b8f1122cbb17eb91500937501734c0e92
testresults-Hosting.Keycloak.Extensions.Tests-windows-latest
19.2 KB
sha256:43b692444238218c7ade75ccfa78f79abfd86f17e1ce9d1603cfa2bff070b11b
testresults-Hosting.KurrentDB.Tests-ubuntu-latest
23.8 KB
sha256:c5272877bc4d1ecf7142ad0a57dde8210779263ef4ebca09070f166346a1f4e3
testresults-Hosting.KurrentDB.Tests-windows-latest
20.7 KB
sha256:b6cceafb9efb96bf0abc3ac8d97ce132f1398ea2a9945659e9676241e3535f70
testresults-Hosting.LavinMQ.Tests-ubuntu-latest
23.4 KB
sha256:fd4bc4395a3540673b4d612cb70ca0155a0d17de73fb0b8120e01ff3c03cd5d8
testresults-Hosting.LavinMQ.Tests-windows-latest
19.8 KB
sha256:4913be808eb64228d8d003cffbcd0d21fa2a2a88f28d6d42f867bdf3b9080e92
testresults-Hosting.Logto.Tests-ubuntu-latest
20.3 KB
sha256:4d7a2e1948c745b3adb7ce02268394c332f6be7aa26e36b041d760d0f0f0e359
testresults-Hosting.Logto.Tests-windows-latest
19.6 KB
sha256:f5163a93faaae394ea4cf00d9aa03f519ec9710d74b59945cb43b2b47f2f10ac
testresults-Hosting.MailPit.Tests-ubuntu-latest
20.6 KB
sha256:296f90c032f47e7c18d25d57037343416b44f2f946c2d7b3155ac355082b07d5
testresults-Hosting.MailPit.Tests-windows-latest
19.7 KB
sha256:de277ecbaa91324a895ceeabbab610a62a123785e99d7f75660a333522d88d8d
testresults-Hosting.McpInspector.Tests-ubuntu-latest
31.5 KB
sha256:9237ad9a87dfc0cb5a1f78b7790d6dfcafc672a500572694735f8136e98c717e
testresults-Hosting.McpInspector.Tests-windows-latest
29.4 KB
sha256:09e33a563e96fa99263ae5ab6f5045531327fa654dc1f1bbf201bcaffb5d0659
testresults-Hosting.Meilisearch.Tests-ubuntu-latest
26.8 KB
sha256:a48a09e248e9fc0b0c352b932c4beb8d36cd9585e6d688f3da2641efccce9bca
testresults-Hosting.Meilisearch.Tests-windows-latest
21.2 KB
sha256:02c450ed895ab24e0adf85f90631171461666d9410c48ccfb979afdde68ee82a
testresults-Hosting.Minio.Tests-ubuntu-latest
27.8 KB
sha256:d38837a6420e637a56d9322d6a5567faf40e1a857ef26d58c516730611d1ce2a
testresults-Hosting.Minio.Tests-windows-latest
21.4 KB
sha256:26b5c1b573e789b14cea711419c3315b7c9d798fb62229f7d73fa9620b00512f
testresults-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
22.7 KB
sha256:b0412ba0e619db60a6b9697be77a1f088e04cbbad81c8e7ca2d7e754d216847e
testresults-Hosting.MongoDB.Extensions.Tests-windows-latest
20.4 KB
sha256:ae8afb69eb7ad578a1302fa4701f5d4452ba7b71b426b551e7126cbe9857e0d5
testresults-Hosting.MySql.Extensions.Tests-ubuntu-latest
25.6 KB
sha256:ccab5fe87952a4e0850bce56de0c640ab96eb6d0ee4442b87c26e24d0cdb851c
testresults-Hosting.MySql.Extensions.Tests-windows-latest
23.1 KB
sha256:0b73221e636ae994e955dc47c9ff67c27c9c91ded2807a57d345fcb36627f3ef
testresults-Hosting.Ngrok.Tests-ubuntu-latest
25.7 KB
sha256:217ebc135c63e8c646c137e9a6c8c818a1c56d785bc37c542fa86ffc4fdb15a8
testresults-Hosting.Ngrok.Tests-windows-latest
23.7 KB
sha256:aa629fdc1cffd1b7f21ef36b20edd63de762598822e416d4e9425f52100af937
testresults-Hosting.Ollama.Tests-ubuntu-latest
39.3 KB
sha256:2899c128b879c4aa3f1702c3151ab56126066ea98d029fcbed172564d1923860
testresults-Hosting.Ollama.Tests-windows-latest
38.3 KB
sha256:0fc447cd7635aba7ba9423a05809201d1e74781663d6d62003fa446a79342887
testresults-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
25.3 KB
sha256:9c0cb514ec9c2c6f22f2f0d9b8c35de1b6460eb0384eff117edb2a29a81f254e
testresults-Hosting.OpenTelemetryCollector.Tests-windows-latest
23.3 KB
sha256:a322e191745e068ec77c66fce433d14a12fe93ddad880ca53f0f3d2982d27861
testresults-Hosting.PapercutSmtp.Tests-ubuntu-latest
19.9 KB
sha256:4f532ad370c3b1e1edd6e876d924d6a64d0230c2ace148967003fc3249393099
testresults-Hosting.PapercutSmtp.Tests-windows-latest
19.1 KB
sha256:0ad83e8f74e1fd840b806b337f30d813f392552aaa94cccb00c76d4c724b9ae7
testresults-Hosting.Perl.Tests-ubuntu-latest
66 KB
sha256:9596048ac23ea5c9668c2bd58f32aad06e60525a9ddb635b829d29398b88f365
testresults-Hosting.Perl.Tests-windows-latest
60.2 KB
sha256:391d3ee873ad673fb393e6ca8f98d5f63af738a5e1e8465df42610c9a734999b
testresults-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
27.1 KB
sha256:e3e2c1f17579e4a37b826b0db73a5011329c3a933e77637fe07ff9fafed926bb
testresults-Hosting.PostgreSQL.Extensions.Tests-windows-latest
25.1 KB
sha256:ffda831a89fa715def5131ab07585fa42eed2bb098db63f3070c2a895a7c0ea4
testresults-Hosting.PowerShell.Tests-ubuntu-latest
26.4 KB
sha256:c32d11f27a88748628a44471affb9f9ebe7771e69194d8bf6a69aff9eaf1ec15
testresults-Hosting.PowerShell.Tests-windows-latest
18 KB
sha256:db0a40315c4eb647aaff0de2ddca0f3832e851018a2e13f44c20e5dd4fccea46
testresults-Hosting.Python.Extensions.Tests-ubuntu-latest
21.6 KB
sha256:b0423bbd7ba00899ff3f58a6dbeed873fb151e646bad0948fc83fe71c7b98e28
testresults-Hosting.Python.Extensions.Tests-windows-latest
23 KB
sha256:955bdc5d59be1cf3c3e73de920a58189cc6eee2aae6e43d34ae1435157b193d4
testresults-Hosting.RavenDB.Tests-ubuntu-latest
32.5 KB
sha256:7984155613b2fbe15058daf000e82f28787285dddffe6758537c2d1a7dbed623
testresults-Hosting.RavenDB.Tests-windows-latest
25.7 KB
sha256:5c070508e4916c1e7e1dc0325488853382fded566a01e7d25d36d4be574da88b
testresults-Hosting.Redis.Extensions.Tests-ubuntu-latest
22.4 KB
sha256:356a1a66057829b5669f62afc0024f35a9a7f8f03667b5dd8bc1ecb09ce35c7f
testresults-Hosting.Redis.Extensions.Tests-windows-latest
20.3 KB
sha256:ee114f50de4ee96e664bee837fba8eaf1e9c4a9ab181442ee9104198d503bcc5
testresults-Hosting.Rust.Tests-ubuntu-latest
98.5 MB
sha256:1aaa3fa7a7855ca4630f1b5146de77c632376935d66af1430811295af2d781e0
testresults-Hosting.Rust.Tests-windows-latest
21.3 KB
sha256:8bf5167c1dd3ef8b511b671e67d713342a34b6fc76e1d9a20386374f7b71cbb0
testresults-Hosting.Sftp.Tests-ubuntu-latest
32.8 KB
sha256:1272c7b8687b3b32223aee61f84b57ab94cc78978508543577e3c29fd235d086
testresults-Hosting.Sftp.Tests-windows-latest
19.4 KB
sha256:4652ad31eb57829a9dfcf0eb18f535cd54e6b56696af78021c0b3f76ed228b05
testresults-Hosting.Solr.Tests-ubuntu-latest
23.7 KB
sha256:f305a73245e9818fffa7a6522b6b055adc3a883c03538c181d6cacaffcabfaa4
testresults-Hosting.Solr.Tests-windows-latest
21 KB
sha256:478d3b08bdf42087672c441d767986cb0542c48015e2355ad461ccd8f682e8af
testresults-Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
28.5 KB
sha256:dfe3ce4584e2ba12bc507bc4a986e26bdeac4263c501b27f89818c3bb72aff2b
testresults-Hosting.SqlDatabaseProjects.Tests-windows-latest
26.8 KB
sha256:3c379023893361a73bce31c13fa096abf4800d57108eda3b9b9f5ffe2ce59303
testresults-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
25.8 KB
sha256:8fa5661ec944cb7efd9d22f11b957c802bbc834777be3eed5d947e43a1cd59be
testresults-Hosting.SqlServer.Extensions.Tests-windows-latest
23.3 KB
sha256:3440b5743a4ce48425a348e2f6e9155c5846dd8d2b842c4106ce70a76f532c8e
testresults-Hosting.Sqlite.Tests-ubuntu-latest
33.2 KB
sha256:5b2d0062995ad04f06cb54b7aea32baa370eb0f498015b8a6bad05c22b451e65
testresults-Hosting.Sqlite.Tests-windows-latest
32.4 KB
sha256:ee1e4d14338b95d55ebe868bfe04bbb262c33c057ff38575b0497841c31f3e8f
testresults-Hosting.Stripe.Tests-ubuntu-latest
24.6 KB
sha256:5703a9dbd491a52e59939e2f3fe92c3f09c92a5307960a4ba7399664f9c5a50a
testresults-Hosting.Stripe.Tests-windows-latest
24.7 KB
sha256:1e9adf9602bbcd69c4732b7e004c0e4052dfb1a4afab0662720543172edbc1b9
testresults-Hosting.SurrealDb.Tests-ubuntu-latest
44 KB
sha256:012c44a44fc8b324683c65428b1f45e64932d0ed98948fb6f559f4f742ef6f92
testresults-Hosting.SurrealDb.Tests-windows-latest
31.4 KB
sha256:d674015e5ee29c5444d9c9b6b33efe6513140ead35075f363fa203df87aa48f4
testresults-Hosting.Umami.Tests-ubuntu-latest
22.1 KB
sha256:07f4ef8b44a622ccaa5d83061b86e34710c272a0a9a1df3e1c516371436fa7bd
testresults-Hosting.Umami.Tests-windows-latest
21.5 KB
sha256:6a7e6d6b79e86f04b725f42ffb25df04f11b543e7b55ddbc4cc40a104319aac0
testresults-Hosting.Zitadel.Tests-ubuntu-latest
24.7 KB
sha256:b43695e566b1f18d7a111a456692b8661044c0e9a2638237fa2760649d3663e6
testresults-Hosting.Zitadel.Tests-windows-latest
23.4 KB
sha256:61b7e9bde2dc18f2752a8977bdcaa92d1f616631695e68bd1ab32076c3c75ad6
testresults-Hosting.k6.Tests-ubuntu-latest
23.1 KB
sha256:10d18b365320ac0dfce45b964d2bd66fc3d4c62e4fe5eea8511a715ad78f1153
testresults-Hosting.k6.Tests-windows-latest
20 KB
sha256:9821515c2218bad969d706381d795ce74ebb7da40746fca5c9585f35b2c931b5
testresults-KurrentDB.Tests-ubuntu-latest
24.5 KB
sha256:b4a7c55ab476d0017f3175559916c603dbbe3007cf8819732ad70a5e85a6675d
testresults-KurrentDB.Tests-windows-latest
24.1 KB
sha256:81b64eab1912e2cf24c045e79125d9b5dd98244a05d1fb1012c8f0e5fec14b41
testresults-Logto.Client.Tests-ubuntu-latest
6.72 KB
sha256:48354859d7a7ce182ee2b7ecd09042a55af3cf538fed2b9420208589c35dba03
testresults-Logto.Client.Tests-windows-latest
6.77 KB
sha256:743ccb18ec79937b0a7ccf75a5ccc3588648869c6bd511f9234df0f1b25cbfd4
testresults-MassTransit.RabbitMQ.Tests-ubuntu-latest
4.91 KB
sha256:cad9dd5bc2698d7d23cf5b8968c398624f78719d1c2f517c18cb2fb31d0d0038
testresults-MassTransit.RabbitMQ.Tests-windows-latest
4.92 KB
sha256:be5126895580c99a041c01955b3debc1145d1d3f761c7f3c55d984dcb6cb625d
testresults-Meilisearch.Tests-ubuntu-latest
24.8 KB
sha256:755ff07d20b522ef85b5d277cd0fe66c56f96c1a5cba17b9d8359cb040aced56
testresults-Meilisearch.Tests-windows-latest
24.5 KB
sha256:8ebf884373bbee8ec4a0ef8ea6016a6c6d2e3ec1bc3ad7348a8640046e920fb2
testresults-Microsoft.Data.Sqlite.Tests-ubuntu-latest
23.5 KB
sha256:74c1e61b4c6b4e38efb50e734cdb07fb5f0a9b4a7319c4e4afb832f3a828558f
testresults-Microsoft.Data.Sqlite.Tests-windows-latest
23.4 KB
sha256:40bc72483cd22348a05a57889bdf87566f00c4a183dac6cd68da919a166bbce6
testresults-Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
25.8 KB
sha256:8ae3b89ff7922f0b5fc86e953c1e6dbd0c6da34b58b972695fc78b919681dba9
testresults-Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
25.6 KB
sha256:02f2317e2a62972f20de5848f9a66481e9a83ada6d81dc0ecd8bccdc9e87f98d
testresults-Minio.Client.Tests-ubuntu-latest
24.9 KB
sha256:02093743d52551678b537786195ebc996595f12ac4a6fb563eb877e21c1ab0b3
testresults-Minio.Client.Tests-windows-latest
24.9 KB
sha256:2e5c7830516743d1b4a973595515f829011203401e0cbcf99d781ef29610722b
testresults-OllamaSharp.Tests-ubuntu-latest
32.9 KB
sha256:4434fb8551119f7844366a7e0caa465b75cd1652e93769a94124854243f11ccf
testresults-OllamaSharp.Tests-windows-latest
32.8 KB
sha256:568fb95440b15982b4d21e140da6809f1e4715c8d155802ff70c9b80afcd9824
testresults-RavenDB.Client.Tests-ubuntu-latest
8.48 KB
sha256:6f5d44ae2b6b70dc89246f699f24a7ce509da28193869943af77987e74627bfe
testresults-RavenDB.Client.Tests-windows-latest
8.51 KB
sha256:4172fd03c66d0ad3cb8d97f1ebdb32fc69244ddc738d2b0a3996ab2a63fb983a
testresults-Sftp.Tests-ubuntu-latest
6.04 KB
sha256:a0790acce900d0905580839a7b772591d4d65e89f8453f2d97d6e3ce8d613d5f
testresults-Sftp.Tests-windows-latest
6.08 KB
sha256:23a3510dfdf903f642961238e3a38f349cce54d41f4c06b884d1fd2171667000
testresults-SurrealDb.Tests-ubuntu-latest
24.6 KB
sha256:417661be292c5907b41a9eb56e187392525ad63069a7d66b0e8eb6a7481a3b06
testresults-SurrealDb.Tests-windows-latest
24.4 KB
sha256:cece3e8e03a67be72e56b8825baf51f80d3bc148fe4f7880469bdca9ee94178b
ts-app-host-logs-Hosting.Bun.Tests-windows-latest
2.81 KB
sha256:245a1f6fc081326c4f03ad8ed0dcb48bca8d60d9d68000e6bc0db2984d4923b9
ts-app-host-logs-Hosting.Deno.Tests-windows-latest
2.81 KB
sha256:b71a091a3785faaf34e7c41f2e1ecc7629cada2a2634f7bad9f50fac61cf882a
ts-app-host-logs-Hosting.Elasticsearch.Extensions.Tests-windows-latest
2.86 KB
sha256:e2cdd0a1a2e3be5e455b9a8264c8d5cc157b1a699a42a56ddf16678fc3f91078
ts-app-host-logs-Hosting.Golang.Tests-windows-latest
2.82 KB
sha256:9f5c5147a770fce1ca8f2542481836ec224cbd3accf6605a4db831e884f9f057
ts-app-host-logs-Hosting.Java.Tests-windows-latest
2.81 KB
sha256:160eeec6bb7869a10d2109bf37b2bb0033ec1e1f3f5eadc052aed0f5edfa828d
ts-app-host-logs-Hosting.JavaScript.Extensions.Tests-windows-latest
2.86 KB
sha256:40f9c67992f33a9fd14856e98c372ea0b815bdce77663a11a25bd870147b3db3
ts-app-host-logs-Hosting.Logto.Tests-ubuntu-latest
1020 Bytes
sha256:a883c69ea001d347b797a6c0644ba4ad1edc9cdee454855178910c57fc3b4e5b
ts-app-host-logs-Hosting.McpInspector.Tests-ubuntu-latest
5.3 KB
sha256:f461d67492f27682a18cc815ceb8d2b2deed16b5a55598cba3b6174c3114021f
ts-app-host-logs-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
2.06 KB
sha256:e2cd75782619b4fc88625e8f12d3f8f341718360bec120888dbadcc7dc385723
ts-app-host-logs-Hosting.MySql.Extensions.Tests-ubuntu-latest
2.09 KB
sha256:8de49aec6a541e0565518a57f072b22143824480ee980d07ffcf0fb62bec4b58
ts-app-host-logs-Hosting.Ngrok.Tests-ubuntu-latest
5.13 KB
sha256:517be882851cc66abe292b24ab6354cf42c89a423e2ef57a6bea853c751762fd
ts-app-host-logs-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
3.57 KB
sha256:db89efd8f44efd9672af5f73ac4309d7d24c7dd8ea3f27f74733bc5c9d6416c0
ts-app-host-logs-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
2.12 KB
sha256:c891d2238cb1ed6921654791c5278de380aca18061fe9c418c2e711f694ba399
ts-app-host-logs-Hosting.Python.Extensions.Tests-windows-latest
2.84 KB
sha256:99babc78e977807739ac0bfee9b5bbca38b9c5604afe5a7e2bd96d0722687493
ts-app-host-logs-Hosting.Redis.Extensions.Tests-ubuntu-latest
2.05 KB
sha256:4c70ab5706cdc53ad6c92ab069ae65ffc4ea5b9975a3e04abba3f026049a8583
ts-app-host-logs-Hosting.Rust.Tests-ubuntu-latest
4.83 KB
sha256:3efb2bbd88bb18266c0cd16685b7d27716b3b87d451f39efc7e94f07acfa2d61
ts-app-host-logs-Hosting.Rust.Tests-windows-latest
3.03 KB
sha256:54ee153dc44fca7a21b5a6e76af09b9ebdb5c2caa8b9cfaa2145421abcb8ef9b
ts-app-host-logs-Hosting.Sftp.Tests-ubuntu-latest
5.64 KB
sha256:5991bb2e74f0ff7a860ec7dd415aa1940e4c60e7ab53442a6e38d2067ce159b9
ts-app-host-logs-Hosting.Solr.Tests-ubuntu-latest
5.44 KB
sha256:b31b42c3f4c9a1354d7c85acd0f73f4421a8bd36ea427b623c9ca036fdc045f0
ts-app-host-logs-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
2.07 KB
sha256:d16c87813f1c8a823ca776dd748db6c426f2d657f70644078b0ed94bd0c0ea94