Skip to content

Allow specifying a custom sidecar resource name via DaprSidecarOptions #2789

Allow specifying a custom sidecar resource name via DaprSidecarOptions

Allow specifying a custom sidecar resource name via DaprSidecarOptions #2789

Re-run triggered April 12, 2026 19:59
Status Failure
Total duration 8m 20s
Artifacts 259

dotnet-ci.yml

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

Annotations

48 errors and 139 warnings
CommunityToolkit.Aspire.SurrealDb.Tests.ConformanceTests.ServiceLifetimeIsAsExpected: tests/CommunityToolkit.Aspire.Testing/ConformanceTests.cs#L176
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.ConformanceTests.MetricsRegistersMeterProvider: tests/CommunityToolkit.Aspire.Testing/ConformanceTests.cs#L162
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.ConformanceTests.TracingRegistersTraceProvider: tests/CommunityToolkit.Aspire.Testing/ConformanceTests.cs#L147
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.ConformanceTests.EachKeyedComponentRegistersItsOwnHealthCheck: tests/CommunityToolkit.Aspire.Testing/ConformanceTests.cs#L122
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.ConformanceTests.HealthChecksRegistersHealthCheckService: tests/CommunityToolkit.Aspire.Testing/ConformanceTests.cs#L108
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.ConformanceTests.OptionsTypeIsSealed: tests/CommunityToolkit.Aspire.Testing/ConformanceTests.cs#L92
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.AspireSurrealClientExtensionsTest.CanAddClientFromEncodedConnectionString: tests/CommunityToolkit.Aspire.SurrealDb.Tests/AspireSurrealClientExtensionsTest.cs#L111
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.AspireSurrealClientExtensionsTest.CanAddMultipleKeyedServices: tests/CommunityToolkit.Aspire.SurrealDb.Tests/AspireSurrealClientExtensionsTest.cs#L85
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.AspireSurrealClientExtensionsTest.AddSurrealClient_HealthCheckShouldNotBeRegisteredWhenDisabled: tests/CommunityToolkit.Aspire.SurrealDb.Tests/AspireSurrealClientExtensionsTest.cs#L56
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
CommunityToolkit.Aspire.SurrealDb.Tests.AspireSurrealClientExtensionsTest.AddSurrealClient_HealthCheckShouldBeRegisteredWhenEnabled: tests/CommunityToolkit.Aspire.SurrealDb.Tests/AspireSurrealClientExtensionsTest.cs#L20
Class fixture type 'CommunityToolkit.Aspire.SurrealDb.Tests.SurrealDbContainerFixture' threw in InitializeAsync ---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit"}
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 376 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-a9c1e99750e6479cbf8f6feef52bd190/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": 4812, "cliPid": 4757, "dashboardUrl": "https://localhost:29750/login?t=b38d0018836ee635d473813dafa4d645", "logFile": "/home/runner/.aspire/logs/cli_20260412T200043067_detach-child_02e1d7140aa84c54b5a6bd97c85bf824.log" } Waiting for resource 'upstream' to be up (running)... ✔ Resource 'upstream' is up (running). (6.1s) 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 697 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 696 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.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.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/net9.0/CommunityToolkit.Aspire.Hosting.Redis.Extensions.dll Successfully created package '/tmp/ct-polyglot-7b42da84a8a14ffab6c5dc5cbc6f6ca2/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.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 479 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-5e6a8b4155ff48ebb62e0bb3b5ec1a31/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": 6453, "cliPid": 6399, "dashboardUrl": "https://localhost:29750/login?t=4478560c5cc9a522ec4f6f94f42a5f75", "logFile": "/home/runner/.aspire/logs/cli_20260412T200053359_detach-child_5c997820cd684ed4892fc00a3b55a737.log" } Waiting for resource 'solr' to be healthy... ✔ Resource 'solr' is healthy. (10.5s) 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.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 661 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/CommunityToolkit.Aspire.Hosting.Flyway.csproj (in 664 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 664 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions/CommunityToolkit.Aspire.Hosting.PostgreSQL.Extensions.csproj (in 664 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.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net9.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.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.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.Flyway -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Flyway/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Flyway.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 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 Successfully created package '/tmp/ct-polyglot-6b0fb700624944908a26342524256434/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.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.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 557 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 558 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MySql.Extensions/CommunityToolkit.Aspire.Hosting.MySql.Extensions.csproj (in 558 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/net10.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.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.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.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/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-39cc501d02e04a889217d1bb3e48aa18/CommunityToolkit.Aspire.Hosting.MySql.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 2s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.Adminer with version (>= 13.2.1-polyglot.local) - Found 160 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-eng - Found 0 version(s) in https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.DbGate with version (>= 13.2.1-polyglot.local) - Found 231 version(s) in https://api.nuget.org/v3/index.json [ Nearest version: 13.2.1-beta.532 ] - Found 0 version(s) in local-polyglot - Found 0 version(s) in dotnet9-transport - Found 0 version(s) in dotnet-
run-tests / Hosting.MongoDB.Extensions.Tests-ubuntu-latest
Process completed with exit code 2.
CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.Tests.TypeScriptAppHostTests.TypeScriptAppHostCompilesAndStarts: tests/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.Tests/TypeScriptAppHostTests.cs#L8
Command 'pwsh -NoLogo -NoProfile -File /home/runner/work/Aspire/Aspire/eng/testing/validate-typescript-apphost.ps1 -AppHostPath /home/runner/work/Aspire/Aspire/examples/mongodb-ext/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.AppHost.TypeScript/apphost.ts -PackageProjectPath /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.csproj -PackageName CommunityToolkit.Aspire.Hosting.MongoDB.Extensions -WaitForResources mongo,dbgate,mongo-named' failed with exit code 1. Standard output: Determining projects to restore... Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.csproj (in 599 ms). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 599 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.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.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/net9.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/net10.0/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.dll Successfully created package '/tmp/ct-polyglot-2682804145b746eaa158c9ebcd1f1364/CommunityToolkit.Aspire.Hosting.MongoDB.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 2s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ❌ Failed to prepare: Package restore failed: ERROR: Unable to find package CommunityToolkit.Aspire.Hosting.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 424 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-9f557e2d1d314cb0a80d425cee9d4b3e/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": 5060, "cliPid": 5007, "dashboardUrl": "https://localhost:29750/login?t=f9c16bb3d9b1075ec1c7e5c211fbbba0", "logFile": "/home/runner/.aspire/logs/cli_20260412T200118219_detach-child_72516db678f34118a5124942c8ad359f.log" } Waiting for resource 'inspector-default' to be healthy... ✔ Resource 'inspector-default' is healthy. (5.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.Stripe.Tests-windows-latest
Process completed with exit code 1.
run-tests / Hosting.Stripe.Tests-windows-latest
Process completed with exit code 1.
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 479 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-9d705852f185404e9a2bdc30b9654b36/CommunityToolkit.Aspire.Hosting.OpenTelemetryCollector.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. 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_20260412T200053703_detach-child_901ba9507cb34f9fb85194cf24a72ec6.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.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.DbGate/CommunityToolkit.Aspire.Hosting.DbGate.csproj (in 1.26 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/CommunityToolkit.Aspire.Hosting.Adminer.csproj (in 1.26 sec). Restored /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.csproj (in 1.36 sec). CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Adminer.dll CommunityToolkit.Aspire.Hosting.Adminer -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Adminer/bin/Debug/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/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/net10.0/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.dll CommunityToolkit.Aspire.Hosting.DbGate -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.DbGate/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.DbGate.dll CommunityToolkit.Aspire.Hosting.SqlServer.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.dll CommunityToolkit.Aspire.Hosting.SqlServer.Extensions -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.SqlServer.Extensions.dll Successfully created package '/tmp/ct-polyglot-e7d6ee08f40a45d28a467fc70aa567cf/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
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 363 ms). CommunityToolkit.Aspire.Hosting.Rust -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/bin/Debug/net10.0/CommunityToolkit.Aspire.Hosting.Rust.dll CommunityToolkit.Aspire.Hosting.Rust -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/bin/Debug/net8.0/CommunityToolkit.Aspire.Hosting.Rust.dll CommunityToolkit.Aspire.Hosting.Rust -> /home/runner/work/Aspire/Aspire/src/CommunityToolkit.Aspire.Hosting.Rust/bin/Debug/net9.0/CommunityToolkit.Aspire.Hosting.Rust.dll Successfully created package '/tmp/ct-polyglot-c0fb8ac3a10a4f6f96398a2999bf7f3f/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. { "appHostPath": "/home/runner/work/Aspire/Aspire/examples/rust/CommunityToolkit.Aspire.Hosting.Rust.AppHost.TypeScript/apphost.ts", "appHostPid": 7053, "cliPid": 6965, "dashboardUrl": "https://localhost:29750/login?t=e60ba0213e25b20cbd63d95b4d505496", "logFile": "/home/runner/.aspire/logs/cli_20260412T200122373_detach-child_1f3b202a97a54f27bc0d240cb9886763.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.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 529 ms). 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 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\net9.0\CommunityToolkit.Aspire.Hosting.Python.Extensions.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-0fc790ffc1d246eea79d727ab3d1690c\CommunityToolkit.Aspire.Hosting.Python.Extensions.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 5s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260412T200223167_detach-child_5c8092b78595437482060f95d4938bc4.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.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 633 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-9059758eb38b48e6b35777f299cf8f6b\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_20260412T200226467_detach-child_11ce62995de549778ce3fb36d825e2b7.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 524 ms). CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.dll CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions\bin\Debug\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\net8.0\CommunityToolkit.Aspire.Hosting.Elasticsearch.Extensions.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-83658fa4c7c64cc78ff6ec946071487e\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_20260412T200257614_detach-child_eb64a98c955e490284d90799d9f7c70e.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.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 772 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\net8.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 Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-49b021f90d6a44a3ad6f39877ed1e889\CommunityToolkit.Aspire.Hosting.Deno.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 8s 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_20260412T200257232_detach-child_a3571f3a6459441d8700ddcdc8f8de70.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 479 ms). CommunityToolkit.Aspire.Hosting.Java -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Java.dll CommunityToolkit.Aspire.Hosting.Java -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Java\bin\Debug\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 Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-24d4e31c4892498e9e2852925194920f\CommunityToolkit.Aspire.Hosting.Java.13.2.1-polyglot.local.nupkg'. added 114 packages, and audited 115 packages in 3s 35 packages are looking for funding run `npm fund` for details found 0 vulnerabilities ⚙ Restoring SDK code... ✔ SDK code restored successfully for apphost.ts. Standard error: Starting Aspire apphost in the background... ❌ Timeout waiting for apphost to start. 🔎 Check logs for details: C:\Users\runneradmin\.aspire\logs\cli_20260412T200302084_detach-child_39d3c87270a7411385dffdb226b6227c.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 577 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-713fd1765e5049bebbc80326eb7e8ca0\CommunityToolkit.Aspire.Hosting.Rust.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_20260412T200320471_detach-child_07592a43f7f54961a9daa05a42326db1.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.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 528 ms). 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 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\net9.0\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.dll Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-ea9fbaee2ea447b1bc68f856a264eebc\CommunityToolkit.Aspire.Hosting.JavaScript.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... ✔ 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_20260412T200431662_detach-child_aa736e11f01647b8a47a4af2b2e88fcd.log Exception: D:\a\Aspire\Aspire\eng\testing\validate-typescript-apphost.ps1:39 Line | 39 | throw "Command failed with exit code ${LASTEXITCODE}: $FilePa … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Command failed with exit code 2: aspire start --apphost | D:\a\Aspire\Aspire\examples\javascript-ext\CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.AppHost.TypeScript\apphost.ts --isolated --format Json --non-interactive
run-tests / Hosting.Golang.Tests-windows-latest
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 556 ms). CommunityToolkit.Aspire.Hosting.Golang -> D:\a\Aspire\Aspire\src\CommunityToolkit.Aspire.Hosting.Golang\bin\Debug\net10.0\CommunityToolkit.Aspire.Hosting.Golang.dll 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 Successfully created package 'C:\Users\runneradmin\AppData\Local\Temp\ct-polyglot-8eaac532bf5a4e21a1dcaad5ce803f23\CommunityToolkit.Aspire.Hosting.Golang.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_20260412T200400943_detach-child_c5d7f7e8b57f42fa9d1d6907dd2d89a2.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 / Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Sftp.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Perl.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / MassTransit.RabbitMQ.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / KurrentDB.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Stripe.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Dapr.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.Dapr.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Microsoft.Data.Sqlite.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Minio.Client.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Meilisearch.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Flagd.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Python.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / SurrealDb.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / SurrealDb.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Bun.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / RavenDB.Client.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.LavinMQ.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / GoFeatureFlag.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Ngrok.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Ngrok.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Deno.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Redis.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Redis.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.RavenDB.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PowerShell.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Solr.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Solr.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.MailPit.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.ActiveMQ.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Flyway.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.MySql.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.MySql.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Umami.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.k6.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.MongoDB.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.MongoDB.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.GoFeatureFlag.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Sqlite.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PapercutSmtp.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Adminer.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / OllamaSharp.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.KurrentDB.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Solr.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.McpInspector.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.McpInspector.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Sftp.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Stripe.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Stripe.Tests-windows-latest
No files were found with the provided path: testresults/**. No artifacts will be uploaded.
run-tests / Hosting.Stripe.Tests-windows-latest
No files were found with the provided path: **/*.binlog. No artifacts will be uploaded.
run-tests / Hosting.MongoDB.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Meilisearch.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.MailPit.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Zitadel.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.k6.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Golang.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Azure.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Redis.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / OllamaSharp.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Minio.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.MySql.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlServer.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlServer.Extensions.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.KurrentDB.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Ollama.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Umami.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.LavinMQ.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.GoFeatureFlag.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Minio.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Dapr.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Zitadel.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.DataApiBuilder.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Java.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Rust.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Rust.Tests-ubuntu-latest
No files were found with the provided path: ~/.npm/cache/_logs/**. No artifacts will be uploaded.
run-tests / Hosting.Adminer.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.DbGate.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PostgreSQL.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.Dapr.Redis.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (ubuntu-latest)
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
build (ubuntu-latest)
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Minio.Client.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Keycloak.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Ngrok.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PowerShell.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
'../SdkProject/SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / SurrealDb.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Meilisearch.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.JavaScript.Extensions.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.OpenTelemetryCollector.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.ActiveMQ.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Sftp.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Meilisearch.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SurrealDb.Tests-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / RavenDB.Client.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / GoFeatureFlag.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Ollama.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Flyway.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SurrealDb.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / MassTransit.RabbitMQ.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Perl.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Flagd.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.RavenDB.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.PapercutSmtp.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.DbGate.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Microsoft.Data.Sqlite.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / KurrentDB.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlServer.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.McpInspector.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Azure.Dapr.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, dapr/setup-dapr@v2, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlDatabaseProjects.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.SqlDatabaseProjects.Tests-windows-latest
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.SqlDatabaseProjects.Tests-windows-latest
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.Sftp.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Python.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Bun.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Elasticsearch.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Deno.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Java.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Sqlite.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Rust.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.Keycloak.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-tests / Hosting.JavaScript.Extensions.Tests-windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-dotnet@v4, actions/setup-java@v4, actions/setup-node@v4, actions/setup-python@v5, ai-action/setup-ollama@v1, astral-sh/setup-uv@v5, timheuer/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (windows-latest)
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
build (windows-latest)
'..\SdkProject\SdkProject.csproj' is referenced by an Aspire Host project, but it is not an executable. Did you mean to set IsAspireProjectResource="false"?
run-tests / Hosting.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/setup-aspire@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
binlog-GoFeatureFlag.Tests-ubuntu-latest
951 KB
sha256:cbe6b2c010b9cab3b0d26f84548549967adb25a35a5dbe1fab4fa84bc5b0813e
binlog-GoFeatureFlag.Tests-windows-latest
960 KB
sha256:b80ba08981ab086403ea01e8763be6efd1af0c6533ca1124327e3c7a1bd03a51
binlog-Hosting.ActiveMQ.Tests-ubuntu-latest
1.4 MB
sha256:8a37f64e992995f4a1d8bc5d6ab8cdf596e57b7f5fc9e598d1b3b0c02d90ae66
binlog-Hosting.ActiveMQ.Tests-windows-latest
1.42 MB
sha256:55a105e612e1f2f362e75015dbc1a76b21bc406849118e1b15cc550fb7603018
binlog-Hosting.Adminer.Tests-ubuntu-latest
2.06 MB
sha256:338af15c365ce6d9a6b3ae5f94330ac3a488486f8b117251648ae4ae8744d693
binlog-Hosting.Adminer.Tests-windows-latest
2.11 MB
sha256:d6074d0b0f67904883e23bf7bc7e9f5b3a9a4d8bee5960ba6f2fca2f2f488415
binlog-Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
1.35 MB
sha256:f59ea7d2136f0a02f5e7011dc96dcafc4c2f616375bd4eb4cad9d9f434b0d525
binlog-Hosting.Azure.Dapr.Redis.Tests-windows-latest
1.37 MB
sha256:ba8355b39899abfbf9559f21acd04fae9ca25bbb4bb88edce6fadef6690281bd
binlog-Hosting.Azure.Dapr.Tests-ubuntu-latest
1.16 MB
sha256:6103392d0f8beef1bcf279a83728ecd32b87be701ec3d500a096c67b9acbc3ef
binlog-Hosting.Azure.Dapr.Tests-windows-latest
1.16 MB
sha256:a0b48c847e952c3c585292fed29ba017e59fa0c86aacfceb61109f9830a59d4c
binlog-Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
1.45 MB
sha256:ac738eaa6ebeb3f32a5c2add263d39d8f0348172b28dc67ac5c903bdc01a27da
binlog-Hosting.Azure.DataApiBuilder.Tests-windows-latest
1.46 MB
sha256:59961cd01ff072818750da24c2b8334baf21bdd4a14c7caec8a9c984b66eed7e
binlog-Hosting.Azure.Extensions.Tests-ubuntu-latest
1.11 MB
sha256:7ad32b486cf841c1c4e0394d7b16048d430563f6e95e0c608b9ed5f41b96c786
binlog-Hosting.Azure.Extensions.Tests-windows-latest
1.11 MB
sha256:2710b6eb6bf203135e09b979af23f10608eaa5ce767e9ee5c1a2d26ead666b87
binlog-Hosting.Bun.Tests-ubuntu-latest
1.07 MB
sha256:06f74986692b1c1f24fac9973e85791800db31d587828eda3f38d3af89358969
binlog-Hosting.Bun.Tests-windows-latest
1.07 MB
sha256:80272a4a14dcd0910323db0d61eafb572368fb0c0083642317b8b224c92e3220
binlog-Hosting.Dapr.Tests-ubuntu-latest
1.65 MB
sha256:286f4a84e17ca2641e89abfe535859cafc2995ccf87f6713916e365030127ff0
binlog-Hosting.Dapr.Tests-windows-latest
1.67 MB
sha256:4db48527f686a61ced650a9ee153c8a492ad34b2168bd37b94aeab6c6da4eebf
binlog-Hosting.DbGate.Tests-ubuntu-latest
2.55 MB
sha256:0907d6484fa187faca4400eeef691c612e4fc3572b2106eb3847651c0409bf2e
binlog-Hosting.DbGate.Tests-windows-latest
2.5 MB
sha256:bc369b7e4c090adc90842361791ef0c2a238389d62e0b9dc69006245ab18a60b
binlog-Hosting.Deno.Tests-ubuntu-latest
1.06 MB
sha256:865301c0139c03a8c059b8bb1f06c58db5aaa4d726dd727b318e66a044f3c599
binlog-Hosting.Deno.Tests-windows-latest
1.07 MB
sha256:53efa52e3fd90ee3540645e8638c3e25228d147b08b795f7014581d8bedb60e9
binlog-Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:89e6840ad750cdce90c8168cb9028079be43796233b1177bb68427844d12bfbf
binlog-Hosting.Elasticsearch.Extensions.Tests-windows-latest
1.08 MB
sha256:310e2d4f0a9197aa16f59a8e4e98db160af0a4520548508f6df8824981349cfb
binlog-Hosting.Flagd.Tests-ubuntu-latest
1.06 MB
sha256:ddd249d74b720bf3e389d8aabfce4c02478ccbafa49c5126e7e5b92ed837b177
binlog-Hosting.Flagd.Tests-windows-latest
1.07 MB
sha256:861ecf63fe7837a2678e1c636b118de1bcbf9e35c2132bd014f38a8d10b08c27
binlog-Hosting.Flyway.Tests-ubuntu-latest
962 KB
sha256:712d352c6c8f77a79048786d1f152de450cf19014b1585d887d296c6b2e3506e
binlog-Hosting.Flyway.Tests-windows-latest
977 KB
sha256:7755c22b86c0fe624115b827eb093e22927c6c0ee9fc7974041e2678feffe6c9
binlog-Hosting.GoFeatureFlag.Tests-ubuntu-latest
1.57 MB
sha256:c325681d3e5e798e979c2b3086411b16ea0a161367bde95a5f7054b3e87c4afd
binlog-Hosting.GoFeatureFlag.Tests-windows-latest
1.59 MB
sha256:9444fc1f77c230dd03ca6011ebf7bf6c0061e77d815d758d65dbefc51ccf0d34
binlog-Hosting.Golang.Tests-ubuntu-latest
1.07 MB
sha256:d60d401b8481dc04aa5d2b94445858265a262681bcb10cc5ec9de654c6bd71f1
binlog-Hosting.Golang.Tests-windows-latest
1.07 MB
sha256:2fb2271d6f52245648916670db07ee7a70b5a936f3d5185877513ef7d82a89a3
binlog-Hosting.Java.Tests-ubuntu-latest
1.55 MB
sha256:665b820cdc74e20276047d7f50c0778a7104aea1a9b80f02f41a82cfe0c2c24e
binlog-Hosting.Java.Tests-windows-latest
1.58 MB
sha256:696e503dc148297a5678c75ebf2cb5e113d181fc3af219613217c7dc016b3b56
binlog-Hosting.JavaScript.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:01b36b54864f1480e68c0785b09b4c4c0695f6a07cd518e873f05a54746714c2
binlog-Hosting.JavaScript.Extensions.Tests-windows-latest
1.07 MB
sha256:51b371dabc706a215a90ebc8a5dde71abfc7e3ce32dab9d53b55263ad7314966
binlog-Hosting.Keycloak.Extensions.Tests-ubuntu-latest
969 KB
sha256:1399ea67af7a27cc68d1356825e100ea07b3fe6b7093449442ae05cf63bb4c59
binlog-Hosting.Keycloak.Extensions.Tests-windows-latest
986 KB
sha256:a41890eb1eb2bcc93775c295c91cdd3e83e82f9b53706311a022317ea0e0e476
binlog-Hosting.KurrentDB.Tests-ubuntu-latest
1.1 MB
sha256:d777c47c4b90900f86827e9c4eb92abdc2a6cb5bbf896d36878cee02c0a4af0a
binlog-Hosting.KurrentDB.Tests-windows-latest
1.12 MB
sha256:a74ce34b023af994588f5be9cea27db1c0ce4a24b1a2182fec62b3c7f55fd198
binlog-Hosting.LavinMQ.Tests-ubuntu-latest
1.39 MB
sha256:18927df20708193fda102db540bcbfc6aa566ff9c71d5a8b3bac758291d68bf5
binlog-Hosting.LavinMQ.Tests-windows-latest
1.41 MB
sha256:b014e7a73d842ed682fe336b4569be775a332fb96f890d16bdbd84c68da45fd6
binlog-Hosting.MailPit.Tests-ubuntu-latest
1.4 MB
sha256:24bb2ec909acbac48214f709b937f098d90657da7e3668a4d5a2fe4ef918e44d
binlog-Hosting.MailPit.Tests-windows-latest
1.41 MB
sha256:6be1730e0958c0a2287b3fa3c769202764026773c9ff946346e5e61f6f609427
binlog-Hosting.McpInspector.Tests-ubuntu-latest
1.28 MB
sha256:a748e0a1da2f5b11c8a48b68d34f9e42fdbd5662cb1fd9502348f81e8b87d8fc
binlog-Hosting.McpInspector.Tests-windows-latest
1.29 MB
sha256:b0bd1df221bdf7bd4dee8143ae219d7ffc87f2048dd121bb4095af402ee7cfaf
binlog-Hosting.Meilisearch.Tests-ubuntu-latest
1.58 MB
sha256:78479b2423878e7f424e874800b75f69d68bbb97a270d33683d69f3f7074a832
binlog-Hosting.Meilisearch.Tests-windows-latest
1.6 MB
sha256:17e1ffae1464c7943d498a12c003c8359c80f3ccf33d6c2883f9d0e8479008f9
binlog-Hosting.Minio.Tests-ubuntu-latest
1.58 MB
sha256:cd257510b04cd8ddbaad9e19445da30f6c51c5af3fee05061772fc070e3c17da
binlog-Hosting.Minio.Tests-windows-latest
1.6 MB
sha256:4cc82f955512883e7b8c6ff8d93ba74cbba258db775d704f51c4e9f989d2b709
binlog-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
1.25 MB
sha256:5b8b1551fd8a3ac1250a57f55f60f84644773c413ba3287191dc4837e1e474d8
binlog-Hosting.MongoDB.Extensions.Tests-windows-latest
1.27 MB
sha256:1f95a13004a9790848dd3b7757baafa1534b5aa6848c3f0893721b98a209e73f
binlog-Hosting.MySql.Extensions.Tests-ubuntu-latest
1.41 MB
sha256:b9496775b7487b70aa2289577d7a32fd9fcea6a2efc608966e9d0a11fb5159fa
binlog-Hosting.MySql.Extensions.Tests-windows-latest
1.44 MB
sha256:a8a50e2b6e085ef51148690c4e5bc0ccf6eb232ce28d3a40a1d0c4106aed6dcd
binlog-Hosting.Ngrok.Tests-ubuntu-latest
1.38 MB
sha256:b715123297123858a8cb481589394341599952dca311b3a56effdea74e3f376e
binlog-Hosting.Ngrok.Tests-windows-latest
1.41 MB
sha256:95d4988910048835df6253494e6378519d154acf7c819cb716bc9dbd48fcd5c5
binlog-Hosting.Ollama.Tests-ubuntu-latest
1.23 MB
sha256:a694bb5384be55e8cdba4cae55b14de9605c024a408c460aa1f5b195078ff90d
binlog-Hosting.Ollama.Tests-windows-latest
1.23 MB
sha256:a88b1cc83891585be02cebadc188b5193d3c61ec2034a19e37ced60a26ac4a24
binlog-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
962 KB
sha256:7beab7837987dfad3ce6d23eb6eee3094de7168e92adbcb959dbfb8d3f8a3c2a
binlog-Hosting.OpenTelemetryCollector.Tests-windows-latest
973 KB
sha256:527bfce24d456eb9d53472441f27b95471681bae44eaf864567084c1b2831f99
binlog-Hosting.PapercutSmtp.Tests-ubuntu-latest
1.39 MB
sha256:81767147c6c5718fde38047570e7f86d4eeaeabc85a1dcea054a4009317e82fe
binlog-Hosting.PapercutSmtp.Tests-windows-latest
1.41 MB
sha256:fcf89016608399405abe33d73a21cbeaad8cef08c5201d62a443d569286ad0d4
binlog-Hosting.Perl.Tests-ubuntu-latest
1.07 MB
sha256:bcaf3e791c1c790941798df3e5956637f0c4872b62e14328890df2f62be6f996
binlog-Hosting.Perl.Tests-windows-latest
1.07 MB
sha256:b62508d6785a14d6860f62223e25aef8115d316754f79e2885d1bea9416d9aeb
binlog-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
1.58 MB
sha256:39ebc792174e914ca094bfa33b829b4573fa6155853067ef6336158407f337da
binlog-Hosting.PostgreSQL.Extensions.Tests-windows-latest
1.59 MB
sha256:ed8ff30db16bbb1d7e701c7a2f2642ed9c74dc48f2a0b8102445eaab6a6dccc7
binlog-Hosting.PowerShell.Tests-ubuntu-latest
1.3 MB
sha256:46e52218d1543eab304ef3033eb04f3d4d7d1f5d4bf963d34e02cf41c633f8bc
binlog-Hosting.PowerShell.Tests-windows-latest
1.31 MB
sha256:0dba605c192e3a73800c923661705068436ff18b20a861be66b7e71e65df0329
binlog-Hosting.Python.Extensions.Tests-ubuntu-latest
1.07 MB
sha256:49e8dda6df4141aa61e2d67df6d102ec1490a4583993c7c82b21407bdca9b095
binlog-Hosting.Python.Extensions.Tests-windows-latest
1.08 MB
sha256:bbb904db0b138877778beaac0543f48d951238c54200d548b72755f31290784f
binlog-Hosting.RavenDB.Tests-ubuntu-latest
1.59 MB
sha256:190bfeb269e1065d84601bd06f93d266568346d2d4a54dc8960305900d8bd0c3
binlog-Hosting.RavenDB.Tests-windows-latest
1.61 MB
sha256:0092eabf461291e911335ca582d0128595aaa6753b9a0070ca30b6be5c62e58d
binlog-Hosting.Redis.Extensions.Tests-ubuntu-latest
1.24 MB
sha256:a79720ef8f8172b052be91fea2d601b11a12a369638f2c7e488a1014f252fd36
binlog-Hosting.Redis.Extensions.Tests-windows-latest
1.26 MB
sha256:df505304b0fd400a73380ac6d638297e1bd28410daba5485e6278742e2618cd0
binlog-Hosting.Rust.Tests-ubuntu-latest
1.06 MB
sha256:33dbffd65e9a366003eb238c2c5ad5fa25d62e06ac5ef04e9b0e5c4e1c434696
binlog-Hosting.Rust.Tests-windows-latest
1.08 MB
sha256:5f912834046543c5417ccd360a1d7768997c7f9341ece16b267e312450c505b1
binlog-Hosting.Sftp.Tests-ubuntu-latest
1.59 MB
sha256:ad91a8e86c445c225c2d7b6912c6f45311917f2059f7333897547defa3200e75
binlog-Hosting.Sftp.Tests-windows-latest
1.59 MB
sha256:4a3121c45a4f4d5204f14d79a089609028d9892ee08482cec76fbddbaf9793a8
binlog-Hosting.Solr.Tests-ubuntu-latest
1.05 MB
sha256:58755f488b8f760e43970bf8ca76a9d3ef0a1d0f162d6bf877970a949e24ae92
binlog-Hosting.Solr.Tests-windows-latest
1.07 MB
sha256:67215a0c7312e94321a5a20b330ae9d11198a2cc69dd9c9e8fbe4bf06094eea4
binlog-Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
1.26 MB
sha256:b1b6d8fac3731d48f893c04af3e8bc75ef1c0da36d2e59984130fd6543c23f28
binlog-Hosting.SqlDatabaseProjects.Tests-windows-latest
1.28 MB
sha256:8681fa4b242d6e0d9dabbac4b4eac890a5cea9c89bd6b4ea811683091b156a45
binlog-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
1.46 MB
sha256:40a57af9a59e74b2d8ab0a82a054cab3b0459a82311e01f1e9bbb0795370aeb9
binlog-Hosting.SqlServer.Extensions.Tests-windows-latest
1.47 MB
sha256:ec9dc473fecf97bed5f0b20ecf67a8b6c133dd1c0ba1af03f11c34da8367c6f3
binlog-Hosting.Sqlite.Tests-ubuntu-latest
1.78 MB
sha256:edb08da65f4bf1d187f0f554b02ca988d8369fa0b31c4017a9ec84b79e4ca4b6
binlog-Hosting.Sqlite.Tests-windows-latest
1.81 MB
sha256:6b6cec3c078f36b5808b1418ac99977321b3a2f847288b42f5b215f691a9f8a3
binlog-Hosting.Stripe.Tests-ubuntu-latest
1.29 MB
sha256:d012f5f70abff98c3369eae16a73e3607e6cafc1ba49804ed373cd1d0cb5fa0a
binlog-Hosting.SurrealDb.Tests-ubuntu-latest
1.6 MB
sha256:e4c9598159fb1c703c0307a4440bdf95a91c7c71d6856af0cdf86180702a696b
binlog-Hosting.SurrealDb.Tests-windows-latest
1.62 MB
sha256:ee64742c5b528bdd8bbae23ffffe8dd6ef644dd5441d4417ae0debd93c0b9676
binlog-Hosting.Umami.Tests-ubuntu-latest
1.06 MB
sha256:766a86e12835b3e94deaad8476940e45127a40681fc634a281b3ba7f287af51b
binlog-Hosting.Umami.Tests-windows-latest
1.07 MB
sha256:c830c20dd95dc6b5ce99cc35a097807a903aacf4a36601a0080ae07f6bd7c986
binlog-Hosting.Zitadel.Tests-ubuntu-latest
1.05 MB
sha256:3cf71a4046ac28bcc2664894027bb4a4a9f2b0481b7fb07a4ea8539a09b20fc9
binlog-Hosting.Zitadel.Tests-windows-latest
1.07 MB
sha256:4d8940c6b8fee266abb6c16a771679cc8fce55e482650074465edf4d48d1f080
binlog-Hosting.k6.Tests-ubuntu-latest
1.39 MB
sha256:c2248bcad838a3fdb936f36ad8c814130e2174a56f8011d0cc2b9e2b57d58b5e
binlog-Hosting.k6.Tests-windows-latest
1.4 MB
sha256:a72b63e49c951c7891b7c0c6b531825abb422c787ff351226361f6b780225ff6
binlog-KurrentDB.Tests-ubuntu-latest
952 KB
sha256:8e94b938d5744383d080a19dff67a1c6074da5a7df84e4d289b00ecd1aa94c05
binlog-KurrentDB.Tests-windows-latest
960 KB
sha256:55ade6be626a10019be52b99e595265202affad4b144eb434599c6e75bb17961
binlog-MassTransit.RabbitMQ.Tests-ubuntu-latest
935 KB
sha256:fa030b75c22bd1b9d6e14f19d26d3d5076f67d978744527d0855c3aff0afbe29
binlog-MassTransit.RabbitMQ.Tests-windows-latest
953 KB
sha256:b82b5b6aabfa9dd00c177f9deb800b17b5745aebe152b6d9f6f69d288eb2e32c
binlog-Meilisearch.Tests-ubuntu-latest
946 KB
sha256:21fdf1d8fad2d3370c561a9d3b55a76cc25086ae276090753f08c0a8b4364c2a
binlog-Meilisearch.Tests-windows-latest
959 KB
sha256:e9b02f3705a1b339fb7fddb349568ef331fbfe2d82754ea7ebe63a3c858829ac
binlog-Microsoft.Data.Sqlite.Tests-ubuntu-latest
942 KB
sha256:3eed571cc390a4c24caa5f890065133c83cf3767859cc577b5d22ea614d50bab
binlog-Microsoft.Data.Sqlite.Tests-windows-latest
955 KB
sha256:c126d484c9f483a54c9fb234ff5417b7fdc30731975016c9d63f75790064bb7a
binlog-Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
958 KB
sha256:a00396f1d98cddf6838e43b3a2415f44a518aab76dae8f16782fd181b848597c
binlog-Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
985 KB
sha256:e0562c83e21edb6e048f42056c2a6d718ea6b4e41a91cc8e7ec4bace93f83a68
binlog-Minio.Client.Tests-ubuntu-latest
1.1 MB
sha256:15e67cab7d8fe8d4caf3fda92a63fe6db0f65f777db4eddd6aa0137becc7d6c9
binlog-Minio.Client.Tests-windows-latest
1.11 MB
sha256:c3768d6903dee1ddf5a794bb0dd564e0e8a7ff1836374695d99f4ff4ab71b560
binlog-OllamaSharp.Tests-ubuntu-latest
948 KB
sha256:bc92e1166e3243770b593f24a7750eb4dc43910cb821d33b0eb8a056a91818dd
binlog-OllamaSharp.Tests-windows-latest
956 KB
sha256:d9e3e6bab9c33abb4dee3296bf47cc05b90879157b186dda580f52e8a5570b00
binlog-RavenDB.Client.Tests-ubuntu-latest
837 KB
sha256:9fcac6c2531fe7606bcf7be0afeaced3c74fbba11331dcfda7dacfd8a136e463
binlog-RavenDB.Client.Tests-windows-latest
853 KB
sha256:eb68ee05278aa476252006cbfd5c09df12e192c7a72f5098236e260b5cb79ca5
binlog-Sftp.Tests-ubuntu-latest
936 KB
sha256:08523a4d7d6976fb751b962afc90612d328b38142148ac409c75b3aa99512e5a
binlog-Sftp.Tests-windows-latest
952 KB
sha256:10526b84935a813ccc0264d278f426303c6be6fc9581514f6a874c7d555fe1ea
binlog-SurrealDb.Tests-ubuntu-latest
959 KB
sha256:d254f57e14c8c1574862ce8df5d330c9c85340b418c2cae054b9ef20d711abcb
binlog-SurrealDb.Tests-windows-latest
966 KB
sha256:1e25ad23d35d5b704b2cc6c354ed49c4ceedf041568a191bb415e3e4de78d96c
npm-logs-Hosting.Bun.Tests-windows-latest
114 KB
sha256:ac9ec0814d21ce21803f4955e66a952176be051a48f4896d90f761c2ddf6ae4f
npm-logs-Hosting.Deno.Tests-windows-latest
114 KB
sha256:f0c9f7ab2accacd51bb76620bb31ff3d9b308ed82f833a3170ae23a236ccdc8d
npm-logs-Hosting.Elasticsearch.Extensions.Tests-windows-latest
115 KB
sha256:972474fb968d6f5ca801e02d7d365074b4a37ab4bde3f1d353942d38918bfa41
npm-logs-Hosting.Golang.Tests-windows-latest
115 KB
sha256:165b3acd43d1502e2f3187316d3745485c817a999d9964666d367436910d8b43
npm-logs-Hosting.Java.Tests-windows-latest
114 KB
sha256:45ff6e5d8479947af661380c055f3fa9e7904223570803796703d1572feebc07
npm-logs-Hosting.JavaScript.Extensions.Tests-windows-latest
212 KB
sha256:d3d5a3e5d72cda2ec88c7dbc08a9ac16d510c4e92f3a27f7ec44bab3bef67091
npm-logs-Hosting.Python.Extensions.Tests-windows-latest
114 KB
sha256:2abca97888ec0181658b9cfcc2bd559d62045cfffb50b342925cae5845c36658
npm-logs-Hosting.Rust.Tests-windows-latest
114 KB
sha256:6d6ba647e0392188a89ec24154ff407cf8a1ea3cd19814e092962c8a575ba4cd
npm-logs-Hosting.Stripe.Tests-windows-latest
94.8 KB
sha256:0d752cfbcf79eb1c0b1aadddda17a32c6c3231eda7a2fca3934ad024404f4acc
testresults-GoFeatureFlag.Tests-ubuntu-latest
24.6 KB
sha256:4a668c6c1950c09d909a830493e69534f15c96acb307315183e9e289001a0d52
testresults-GoFeatureFlag.Tests-windows-latest
24.4 KB
sha256:6d2a8049cadf5fa08430a8a94a1965bccc97a76dfe65980523af758837b6989d
testresults-Hosting.ActiveMQ.Tests-ubuntu-latest
25.9 KB
sha256:937a8d04833772cf49ccf28568e7f22f18c08e2a3a96e17597948dd9e75a3742
testresults-Hosting.ActiveMQ.Tests-windows-latest
22.4 KB
sha256:975a441a2ddf7126e32afed2b000211a6b3b2583e27570225ec209b6fa6fe44a
testresults-Hosting.Adminer.Tests-ubuntu-latest
27.2 KB
sha256:10d153807dc15dfe5f763fa401df2b3821abacf5704ecdde022d0b239c48ab52
testresults-Hosting.Adminer.Tests-windows-latest
25.7 KB
sha256:7b279807aeedfee95a8aa5e7f0e724180d9a285b9d57f9831f9cec05161592cd
testresults-Hosting.Azure.Dapr.Redis.Tests-ubuntu-latest
49.7 KB
sha256:687c53ea721244df2b99189385f05f072158aa71b1aae5e5e141a9027699c944
testresults-Hosting.Azure.Dapr.Redis.Tests-windows-latest
49.8 KB
sha256:32940f93ee16018515203a575bd03fd9579e7140a44ad9011673635147ed206f
testresults-Hosting.Azure.Dapr.Tests-ubuntu-latest
47.9 KB
sha256:b0574e972e7a63bca4afb50d514ac0d8b85b4d4f8038c1596e720f1d97a36cd6
testresults-Hosting.Azure.Dapr.Tests-windows-latest
47.8 KB
sha256:f2e8453e6971a87d2049c59fd506e7d8815a45fc7f61fb5a2c7c5c516d441e47
testresults-Hosting.Azure.DataApiBuilder.Tests-ubuntu-latest
23.9 KB
sha256:7f22c8f9acb7d6ec38cd6a59f521aa35204cc84ee8e305e785c26a49b07544b4
testresults-Hosting.Azure.DataApiBuilder.Tests-windows-latest
20.1 KB
sha256:6f290dc3634731b3e50aa5a4f6bd108d430d652efefc23bb1679cc4e5ce7b5f2
testresults-Hosting.Azure.Extensions.Tests-ubuntu-latest
20.5 KB
sha256:95237875b77cdffde4dba7432f86b4395bc76ffdc8acefb5be6ed5201c25398f
testresults-Hosting.Azure.Extensions.Tests-windows-latest
20.1 KB
sha256:ef02ae5ddb1ada1bf7fe1ad372d912d91105a6585f18517ecb1c427d59ff4010
testresults-Hosting.Bun.Tests-ubuntu-latest
20.9 KB
sha256:b4edb4b43a34b120df2be09e8960e311b48e1e21b722f3af8b6ca8054de5ac67
testresults-Hosting.Bun.Tests-windows-latest
22.4 KB
sha256:979d49fbc46e1022a56cf438ac8608d7b0d11b3e965e76c56b6a3f2f0b8f397d
testresults-Hosting.Dapr.Tests-ubuntu-latest
48.1 KB
sha256:f4fe6ebd74e3871bcfca994f504e6dc300f7800d08c230bbbb3ec15255a0a99f
testresults-Hosting.Dapr.Tests-windows-latest
47.8 KB
sha256:fcc0aa8ded40834e3e976ffcc2e2848c03335869f42b82e3539a679854d63270
testresults-Hosting.DbGate.Tests-ubuntu-latest
29.5 KB
sha256:f4d63e05465a20a3e9e653e9509a29e9b1d47fa67aefe1a17b773114853408fb
testresults-Hosting.DbGate.Tests-windows-latest
27.8 KB
sha256:b26c8563cd9169f40564d4e38a242c0c0c8c262be54158c1fd7c3e036da57466
testresults-Hosting.Deno.Tests-ubuntu-latest
20.4 KB
sha256:9673591499e1965243e0c0f4604b0f8f3b338b70060b964a0a0435c81618520d
testresults-Hosting.Deno.Tests-windows-latest
21.8 KB
sha256:8d63d77e6157e31d3faeeffe2f2b79fb7ad484937d6d69440a039a51f17a3476
testresults-Hosting.Elasticsearch.Extensions.Tests-ubuntu-latest
21.3 KB
sha256:4c575c7ec9c2ec01d16eb5766704c2925c625082db52e8a3522af8203e10a40c
testresults-Hosting.Elasticsearch.Extensions.Tests-windows-latest
22.3 KB
sha256:131c473ad90e5a03525169bbd6d35eba23098b033913de54004b3c991aa815c0
testresults-Hosting.Flagd.Tests-ubuntu-latest
22.7 KB
sha256:4c18a651bb141c36bcfe142905a1bc90c5040568a0011a39e51fa9955f3fc353
testresults-Hosting.Flagd.Tests-windows-latest
21.7 KB
sha256:3c05d859f2eb8ed49a6a09db1c7c16dac3dac3423bb89f6314b9a75e4ce0fc38
testresults-Hosting.Flyway.Tests-ubuntu-latest
19.1 KB
sha256:b7ce1ac312eeca66b9b4021acef66c65358c15b2dc7af19637fe8dd382385da3
testresults-Hosting.Flyway.Tests-windows-latest
18.7 KB
sha256:7fe8fcde497739fe4fad29255022478f860391c6f66e6f1c151732d058ea892e
testresults-Hosting.GoFeatureFlag.Tests-ubuntu-latest
26.3 KB
sha256:0c1cf03e1e220c2a101e19f5a4c997034e74a3eb3a79867d1502f9c333e0dcae
testresults-Hosting.GoFeatureFlag.Tests-windows-latest
21.2 KB
sha256:eba3259f02b6399e5cba5cbfb900d37149631e0bc3fa00981f1ad49b98fe1183
testresults-Hosting.Golang.Tests-ubuntu-latest
24.3 KB
sha256:0b3b0c97147028b4095f7ede382a6fdf54ac136c9ea7993b82f4888e2a3aa0e4
testresults-Hosting.Golang.Tests-windows-latest
25.7 KB
sha256:a853de757aa091f96c106302735b943fe2c99c460442eccc842e9a7f5cfc85af
testresults-Hosting.Java.Tests-ubuntu-latest
33.4 KB
sha256:d25a9004a625130cd0fd33fb9516ba813f26becc7f3a1e9c52d3e3ce8150f606
testresults-Hosting.Java.Tests-windows-latest
29.7 KB
sha256:e37b795402cd4c0024dcd81b8bb870f614bd81bfe82685a39dfee2e59402441d
testresults-Hosting.JavaScript.Extensions.Tests-ubuntu-latest
29 KB
sha256:360712f1362b0a850f07c1557f565a814320200608df11f28a477893747921ae
testresults-Hosting.JavaScript.Extensions.Tests-windows-latest
31.2 KB
sha256:53fb65f75f449c20effcb4e651f1d2d548fe84bee83cf6e14b3ab9633d377581
testresults-Hosting.Keycloak.Extensions.Tests-ubuntu-latest
20 KB
sha256:178a78e883e55874237423c2157d0966dc63cee61aa794697f6f05621ab38740
testresults-Hosting.Keycloak.Extensions.Tests-windows-latest
19.2 KB
sha256:9c873c96d0230b70f4f48af7f125a12f1b1afd83fae5fb731b10d3b03ecd3f15
testresults-Hosting.KurrentDB.Tests-ubuntu-latest
23.8 KB
sha256:1ebb8593c3bd3b1beb781391912cc48abd69e68baeaa8ee42a2491af3e10d661
testresults-Hosting.KurrentDB.Tests-windows-latest
20.7 KB
sha256:55e64342912a8d1aaef02754d06e9a4c7c0999636978dd01245391574e899a96
testresults-Hosting.LavinMQ.Tests-ubuntu-latest
23.4 KB
sha256:7a5cfedbe598dcb21ebde2d1eb850bb3f76d1db43759b714902011eb06104c96
testresults-Hosting.LavinMQ.Tests-windows-latest
19.8 KB
sha256:0806c9fb716d0a535bc3664c31f4d0acd35b678311605278267e392a007aeaaa
testresults-Hosting.MailPit.Tests-ubuntu-latest
20.6 KB
sha256:24a6ea6087978c60e0103935cae049d4f30a9ffab00f820e47a93170de80bb84
testresults-Hosting.MailPit.Tests-windows-latest
19.7 KB
sha256:61380bc7e41b5475761f7ee39883467e4b6571c3b6d25ad938542b2d30e94db6
testresults-Hosting.McpInspector.Tests-ubuntu-latest
31.5 KB
sha256:96d913f6def13bed073b0125b34654a2af46d7e6d96cd736c84d4d50b8f43224
testresults-Hosting.McpInspector.Tests-windows-latest
29.4 KB
sha256:0543871959a1a28baccedf36ba52350e4a64585b9fd7b1f7e27cc85e2bfdca3a
testresults-Hosting.Meilisearch.Tests-ubuntu-latest
26.8 KB
sha256:4d23101fa7019bcea25a91fc3d8ac7d04a69ec5ac470715a1ff3778a94dbe817
testresults-Hosting.Meilisearch.Tests-windows-latest
21.2 KB
sha256:bd32e47b8ce4acf8f51abfada13fcaaedfe1b7e770c8db02c0bfdb9f8449d827
testresults-Hosting.Minio.Tests-ubuntu-latest
27.8 KB
sha256:7322abd6b1f02d724b7fc799d28d3d9d11b08abf12fcec3c6e9df15de8fb1943
testresults-Hosting.Minio.Tests-windows-latest
21.4 KB
sha256:a793fdd44b2104b36ca86a777e8d667889f01666c8951a06241bbc4f3b9f3e44
testresults-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
22.7 KB
sha256:2044078dee32a3972a27a97d4f95f4dc6476997d4250fc18d3e269bbbf7e8e47
testresults-Hosting.MongoDB.Extensions.Tests-windows-latest
20.4 KB
sha256:815be9971a89397dca33bb122fee501808b62caf3bc84ad106797de47833228c
testresults-Hosting.MySql.Extensions.Tests-ubuntu-latest
25.6 KB
sha256:07b85c90e1d54bab3391b1ef65654af60ed0813d5ed61048b11a94d6c026b231
testresults-Hosting.MySql.Extensions.Tests-windows-latest
23.1 KB
sha256:d73b0226edffdafaa30a4f7844ee292783b40175c01447c43d02d3158baa34a7
testresults-Hosting.Ngrok.Tests-ubuntu-latest
25.7 KB
sha256:548d9f18bc038906474bae689c1314e97eff4f8fca8158b9b227f9b3a053a0af
testresults-Hosting.Ngrok.Tests-windows-latest
23.7 KB
sha256:244153f8b6c206bfabff365c44dd49b5f821c58f04e4836209fc9f094f5d6c7e
testresults-Hosting.Ollama.Tests-ubuntu-latest
39.2 KB
sha256:8cb92fca7cdd1bc61e882f046c5c2b3c968e9018a8d76fc2d69d0ca84a818adb
testresults-Hosting.Ollama.Tests-windows-latest
38.3 KB
sha256:93bf00da641a470ffcf8d0e9089b1a40d4d16aa5f9b355dac729590c1762c690
testresults-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
25.3 KB
sha256:e62a9143c12a0c45652f9c6b2f6d8f2550536d00426f3fc6264eda34c6e5c271
testresults-Hosting.OpenTelemetryCollector.Tests-windows-latest
23.3 KB
sha256:974cc6f5cef2d43a75e24266468955de2db5f3adaeeb7eb061355d8b77580f9e
testresults-Hosting.PapercutSmtp.Tests-ubuntu-latest
19.9 KB
sha256:6f1b251eb2555fc0c5edbc412e1e2cd122e51ced6d38fb074c195b7d8e8ef535
testresults-Hosting.PapercutSmtp.Tests-windows-latest
19.1 KB
sha256:e6926d75f32a8f492553c16047ad4dd7752db70f9d8d878863fc18d18d8ee96b
testresults-Hosting.Perl.Tests-ubuntu-latest
66.1 KB
sha256:6e059a79211c97d8ae8c23bc244613668dd403498d9404689f25e849c2b96604
testresults-Hosting.Perl.Tests-windows-latest
60.2 KB
sha256:4d0e4693e0d536d461654e4405d54f6b42bc82bc8e97e5efb3f165b866429dcb
testresults-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
27.1 KB
sha256:a26c87d1fb297527b17dae6fafe5b61eeec5b8ddbe1840989a539fb73e3cb00b
testresults-Hosting.PostgreSQL.Extensions.Tests-windows-latest
25.1 KB
sha256:b2f4511280ef2bf19dce0381c4173bddcaff793e7d40385df80f68d9b4d07e2b
testresults-Hosting.PowerShell.Tests-ubuntu-latest
26.4 KB
sha256:98f53df8c2d5f556c6ecce9b90949a31887da7729d5d187ac3d8ea5ce76e8f4b
testresults-Hosting.PowerShell.Tests-windows-latest
18 KB
sha256:4854bd36ff9e56a66fbf55e9fbd7b74eeaa2d15b3f32c6c5b1a374a55ed94c9b
testresults-Hosting.Python.Extensions.Tests-ubuntu-latest
21.6 KB
sha256:7c8575892ae41570cdfdd0f1cccac147916f10e1c77a3c26bf3a1725b7381eaf
testresults-Hosting.Python.Extensions.Tests-windows-latest
23 KB
sha256:4f5fc2b5bb712d20748ed747e6ff94df6c68bd812a96b0e0832f2df59fc7e8d4
testresults-Hosting.RavenDB.Tests-ubuntu-latest
32.5 KB
sha256:ffb735ae0d6107e23c50859eaa729a21f8d502b62b087831aafb3b59bd08edc4
testresults-Hosting.RavenDB.Tests-windows-latest
25.7 KB
sha256:a858a083311956e28b20298014fe152d13956e848098277a519f83b1b3edcd60
testresults-Hosting.Redis.Extensions.Tests-ubuntu-latest
22.4 KB
sha256:48e0520db7f431a10f65a1e423b358bb39f9b65ee22c043999a08d61de75fc20
testresults-Hosting.Redis.Extensions.Tests-windows-latest
20.3 KB
sha256:b5d38dbe03222d12c91a4cf480ea75b441ec26b28ca52b7dbce08ca56a94a963
testresults-Hosting.Rust.Tests-ubuntu-latest
98.6 MB
sha256:1f01827c73687cfc356735f0578777b0d4365152a143aec326afd2ce053f7312
testresults-Hosting.Rust.Tests-windows-latest
21.3 KB
sha256:7f9f3db97320dffe18606230e3018dabc02c23d3e0045348838c65bb2463f542
testresults-Hosting.Sftp.Tests-ubuntu-latest
32.3 KB
sha256:613cd6ac8420e05d0937da11d326ac09781d5b47aacdc3041fa0d1e7f470cc37
testresults-Hosting.Sftp.Tests-windows-latest
19.4 KB
sha256:19b21a1c211d77afdd7d92eaa1a8f73fdd5ca774e56b9f7a89af924eaa0023ee
testresults-Hosting.Solr.Tests-ubuntu-latest
23.7 KB
sha256:0ab96b1acc6cc8cce032bd4db33927fa8be1cd78fb153ceba52fc13876fc3b7c
testresults-Hosting.Solr.Tests-windows-latest
21 KB
sha256:0404b4f894a784a0484d4e53203f103dfb33f3f2aa6bdc5c834e105061f07978
testresults-Hosting.SqlDatabaseProjects.Tests-ubuntu-latest
28.5 KB
sha256:7f4400a24ec963c8cb13ee3cfd0e4fcf732778283388fb588abd58ba4a4c7ada
testresults-Hosting.SqlDatabaseProjects.Tests-windows-latest
26.8 KB
sha256:abbd02e0f02f6e0f0973f81bd38c61c034bfb43ee640f00beadfa7027c783c61
testresults-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
25.8 KB
sha256:4f48015ede5eea2fbf10465e9b72083e69ee8993e5efb32c86e3680bc91a7e85
testresults-Hosting.SqlServer.Extensions.Tests-windows-latest
23.3 KB
sha256:7446d9904a96ca7b8522c49f755f5704d11d4d54fb3ce688c7b2f142f6ea5542
testresults-Hosting.Sqlite.Tests-ubuntu-latest
33.2 KB
sha256:6655aabac87e1b88f4e17fca7759f1f3942ec3fbae5c89a04ebeb07e349dd61a
testresults-Hosting.Sqlite.Tests-windows-latest
32.4 KB
sha256:1cb79c3462698e0afa95aee43a1c82ae06d29256e2150dae4a641c246cc3dcb7
testresults-Hosting.Stripe.Tests-ubuntu-latest
24.6 KB
sha256:3b0a6fbc10dec0dba014f85f2c28912bf6d5846efec17ab5f6e81ab96dbf1dcf
testresults-Hosting.SurrealDb.Tests-ubuntu-latest
43.8 KB
sha256:0331efe9a4d77826d4a1d8de059e3fca21d856b0b1f3ef133c7bec7660b56c38
testresults-Hosting.SurrealDb.Tests-windows-latest
31.3 KB
sha256:1bd0684139923c13b470ec725ce41bcd89cd40067db1226e98570e8c4aa8188f
testresults-Hosting.Umami.Tests-ubuntu-latest
22.1 KB
sha256:af5e4ea367665099dbaa480f2598e7c257e78ccef25c61f8e6e2f6a4d76e1f42
testresults-Hosting.Umami.Tests-windows-latest
21.5 KB
sha256:2bb1d2b6f8800049c487b6191292aaca5d449a9774c4126416a99825e3183079
testresults-Hosting.Zitadel.Tests-ubuntu-latest
24.7 KB
sha256:902f6b213f3ea0b2b0030633c644a1ad969965618c9bcb36854321f6e2b163ec
testresults-Hosting.Zitadel.Tests-windows-latest
23.4 KB
sha256:08a5875cc22b463653c3888ac7c49443b47f5c89968490e8e5d897b08528a61b
testresults-Hosting.k6.Tests-ubuntu-latest
23 KB
sha256:5e7091f57c40ef800100c6db25783c89d36af5c17a257b740fb5d5fea6dc221a
testresults-Hosting.k6.Tests-windows-latest
20 KB
sha256:ebce4f2c1e873e33758578ebb5ca99068ea8fa59022c3f3e5aa7c8f60d3f2343
testresults-KurrentDB.Tests-ubuntu-latest
24.6 KB
sha256:e1a6e3794c32112131a700c942286601feb641eaaca91752f6d9188fa383a723
testresults-KurrentDB.Tests-windows-latest
24.1 KB
sha256:7e7bbc9b783b1c5dfee5ec4aedd20dfcdac24dcd6408bde65e5e2e59bfe1b1a8
testresults-MassTransit.RabbitMQ.Tests-ubuntu-latest
4.9 KB
sha256:0a29067f936a3c2d7a33323c23c78a20f9f7afe923b494c521cf858e8f394462
testresults-MassTransit.RabbitMQ.Tests-windows-latest
4.93 KB
sha256:d2d1dc6299845f2bbc893fadd5b225f2653fc772163cf07e9bac4123399e0539
testresults-Meilisearch.Tests-ubuntu-latest
24.8 KB
sha256:0d76e00b6ce0cefc5d64425ded9ef2feac42d18a5a10c0add28b966a0315bb8a
testresults-Meilisearch.Tests-windows-latest
24.5 KB
sha256:9e0497df6a474e310a596ce952bc9c948e11ff95929a7258cb8cbcfa5c8b7f62
testresults-Microsoft.Data.Sqlite.Tests-ubuntu-latest
23.5 KB
sha256:b444c98625d1052482d9872c10156bace98e9b958055a1b36daeb195e9aee734
testresults-Microsoft.Data.Sqlite.Tests-windows-latest
23.4 KB
sha256:8db5d744101e4b1ecf5e705c701eee65abf10bde2b4f7dcb6c66086a72375705
testresults-Microsoft.EntityFrameworkCore.Sqlite.Tests-ubuntu-latest
25.8 KB
sha256:8a56d00bc552c958c953c738825a1bb7a868e0ba832e12e6301028c9199baaa4
testresults-Microsoft.EntityFrameworkCore.Sqlite.Tests-windows-latest
25.7 KB
sha256:bfb793fd2f41c1b8c211c483a8d70207d86d7356d270a706ac6d377d71dfe5a1
testresults-Minio.Client.Tests-ubuntu-latest
24.9 KB
sha256:397ccb0807056048c4bb18642adc515ab79710a755f3a85c6d9577db92e7a443
testresults-Minio.Client.Tests-windows-latest
24.9 KB
sha256:0676917de185a22a26cfb9fbdb6b6d24337500ac43e2d91f832a97518b158eea
testresults-OllamaSharp.Tests-ubuntu-latest
32.9 KB
sha256:07a00b4e9e7aa6d9b4a3cc42eb5632e2b59676949e240cb336bdd781c962d55d
testresults-OllamaSharp.Tests-windows-latest
32.8 KB
sha256:79f8734f141b04b7ea102f59515e5bba8abbd834db736ae1a46f18b179332a8b
testresults-RavenDB.Client.Tests-ubuntu-latest
8.47 KB
sha256:3176dc101e95df8879b828cc18544db2d444ce8031313756bb5cc0d79febc292
testresults-RavenDB.Client.Tests-windows-latest
8.52 KB
sha256:30e9127d8a8c2cf6147a71cf3fc1d2d2d806281c8fa6f7df9c52016259032598
testresults-Sftp.Tests-ubuntu-latest
6.05 KB
sha256:4a2266783adf4a0244eece39531e987c49244c0e27ef1efa47ae09e5d3760f31
testresults-Sftp.Tests-windows-latest
6.08 KB
sha256:32529e74a741a180dce09344bfd79b559ff5c9c095f73f6fb5b67b0a3d0b9964
testresults-SurrealDb.Tests-ubuntu-latest
25.1 KB
sha256:23cb3f1cbe9ace5b9532b60c600d5882cf0b2160006be32ed1a1a365e2a477b1
testresults-SurrealDb.Tests-windows-latest
24.4 KB
sha256:02b55940ad71b395191d4408ec0604c9a230e62ffa280a4ddf521e41be46c3f2
ts-app-host-logs-Hosting.Bun.Tests-windows-latest
2.81 KB
sha256:b6b1270283b4faecd5bac64a73d9b4763f2072a2e406cb60038da863cc2508dc
ts-app-host-logs-Hosting.Deno.Tests-windows-latest
2.82 KB
sha256:e71fd98ba58a77d93099dd5e303a1b787b225d0a2d36229e5434a32138f57947
ts-app-host-logs-Hosting.Elasticsearch.Extensions.Tests-windows-latest
2.86 KB
sha256:3b600fc51ad8180269aa646217ec2ae338b46af883c7bf879047b2e91c77d3c0
ts-app-host-logs-Hosting.Golang.Tests-windows-latest
2.82 KB
sha256:2d62a835072f130d3acb6a6d68afe8d31173d359b6ce6f44c79a9cfca687db00
ts-app-host-logs-Hosting.Java.Tests-windows-latest
2.81 KB
sha256:44de6de65f0a71c4895b077d26fad31174685a458a3ac3ede832ee530f290356
ts-app-host-logs-Hosting.JavaScript.Extensions.Tests-windows-latest
2.86 KB
sha256:44e1fa2d3922b502859f05c642bf39b6ddc3f8b86b8caa752f81f3aab7d1141b
ts-app-host-logs-Hosting.McpInspector.Tests-ubuntu-latest
5.22 KB
sha256:c4b7a65991024142a4051af962fe9b9675d15e36143ed1124afdf4383d36b6f7
ts-app-host-logs-Hosting.MongoDB.Extensions.Tests-ubuntu-latest
2.18 KB
sha256:9533dffff7d3207826ac07d76847ff46d6a2beb2abc510b1aa69773c7d0f4bae
ts-app-host-logs-Hosting.MySql.Extensions.Tests-ubuntu-latest
2.09 KB
sha256:90414f52da08093765d77082501ec8f84b8662430158a555c8fbcc1302a68b13
ts-app-host-logs-Hosting.Ngrok.Tests-ubuntu-latest
5.08 KB
sha256:a6b3bf67f24692f4db522f8185dba1146dac3df01e91530fc84523ecf48b3be2
ts-app-host-logs-Hosting.OpenTelemetryCollector.Tests-ubuntu-latest
3.64 KB
sha256:50359817e937142a6c9f05d2497788272f5122b818d50b8a9d5dd80dab70cf1a
ts-app-host-logs-Hosting.PostgreSQL.Extensions.Tests-ubuntu-latest
2.12 KB
sha256:87e20712bda98cfd41c98a06c3032da21b92a11f7da1f360f1101e579d898885
ts-app-host-logs-Hosting.Python.Extensions.Tests-windows-latest
2.84 KB
sha256:18bf165a1ce354b7074b89f9f1e29f9d78b519d0efc9f860d7de191075b7d2f6
ts-app-host-logs-Hosting.Redis.Extensions.Tests-ubuntu-latest
2.05 KB
sha256:c4a066ba470e4ec403e308e58799f9f703992d54c27b1b09bd5a389420e16715
ts-app-host-logs-Hosting.Rust.Tests-ubuntu-latest
4.84 KB
sha256:71f0ebca1f748c2c2b234cd79da75412daf28193bcd9fcf989b1c7d07dd777af
ts-app-host-logs-Hosting.Rust.Tests-windows-latest
3.06 KB
sha256:9c153ebdda66f0f998f2a8aa9b3eae5dc8e585e143b728b4a71cfa8c0953ba8a
ts-app-host-logs-Hosting.Solr.Tests-ubuntu-latest
5.47 KB
sha256:8a5f5e91feb8cded75160b43c5f1a901514ac663f673dcc8b8502ab05c3d27af
ts-app-host-logs-Hosting.SqlServer.Extensions.Tests-ubuntu-latest
2.09 KB
sha256:7961719ef2f7efd67e3632d2e4d1d85c0bcb57cb1d78b2ddf77d61ca87578dfa
ts-app-host-logs-Hosting.Stripe.Tests-windows-latest
1 KB
sha256:6454d037fee1b5ece0fb1b1f36d653134ccc6d67d97387399a7c6db0432d26c1
ts-app-host-logs-SurrealDb.Tests-ubuntu-latest
1.07 KB
sha256:b8446933a0ea4908fef07e7e3064b26f4b101d9198976a147652105cb06fcaf4