Skip to content

pages: add Jekyll front matter to API ref so just-the-docs renders pages #209

pages: add Jekyll front matter to API ref so just-the-docs renders pages

pages: add Jekyll front matter to API ref so just-the-docs renders pages #209

Triggered via push May 11, 2026 13:16
Status Failure
Total duration 4m 38s
Artifacts 1

ci.yml

on: push
CodeQL Security Analysis
4m 34s
CodeQL Security Analysis
Matrix: build
Matrix: integration-tests
Fit to window
Zoom out
Zoom in

Annotations

1 error, 45 warnings, and 1 notice
build (ubuntu-latest)
Process completed with exit code 1.
build (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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 (macos-latest): FluentDocker/Testing/Core/ContainerResource.cs#L145
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/PodmanKubernetesResource.cs#L136
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/ResourceBase.cs#L236
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/ResourceBase.cs#L192
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L111
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L108
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L105
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L74
Method 'FluentDocker.Testing.Core.ResourceLifecycle.CreateAndInitializeAsync<TResource>(System.Func<FluentDocker.Kernel.FluentDockerKernel, TResource>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Threading.CancellationToken, Microsoft.Extensions.Logging.ILoggerFactory)' should take CancellationToken as the last parameter (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1068)
build (macos-latest): FluentDocker/Testing/Core/SwarmStackResource.cs#L139
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (macos-latest): FluentDocker/Testing/Core/TopologyResource.cs#L159
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
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/checkout@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (ubuntu-latest): FluentDocker/Testing/Core/PodmanKubernetesResource.cs#L136
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L111
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L108
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L105
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L74
Method 'FluentDocker.Testing.Core.ResourceLifecycle.CreateAndInitializeAsync<TResource>(System.Func<FluentDocker.Kernel.FluentDockerKernel, TResource>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Threading.CancellationToken, Microsoft.Extensions.Logging.ILoggerFactory)' should take CancellationToken as the last parameter (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1068)
build (ubuntu-latest): FluentDocker/Testing/Core/ResourceBase.cs#L236
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Testing/Core/ResourceBase.cs#L192
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Testing/Core/SwarmStackResource.cs#L139
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Builders/ContainerBuilder.cs#L469
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (ubuntu-latest): FluentDocker/Builders/Builder.cs#L252
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
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/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (windows-latest): FluentDocker/Testing/Core/ResourceBase.cs#L236
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Testing/Core/ResourceBase.cs#L192
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Drivers/Podman/Cli/PodmanCliDriverPack.cs#L150
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Builders/Builder.cs#L252
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L111
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L108
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L105
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Testing/Core/ResourceLifecycle.cs#L74
Method 'FluentDocker.Testing.Core.ResourceLifecycle.CreateAndInitializeAsync<TResource>(System.Func<FluentDocker.Kernel.FluentDockerKernel, TResource>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Threading.CancellationToken, Microsoft.Extensions.Logging.ILoggerFactory)' should take CancellationToken as the last parameter (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1068)
build (windows-latest): FluentDocker/Testing/Core/SwarmStackResource.cs#L139
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
build (windows-latest): FluentDocker/Testing/Core/TopologyResource.cs#L159
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, github/codeql-action/analyze@v3, github/codeql-action/init@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
CodeQL Security Analysis: FluentDocker/Builders/ContainerBuilder.cs#L469
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/PodmanKubernetesResource.cs#L136
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/ResourceBase.cs#L236
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/ResourceBase.cs#L192
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/ResourceLifecycle.cs#L111
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/ResourceLifecycle.cs#L108
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/ResourceLifecycle.cs#L105
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogError(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/ResourceLifecycle.cs#L74
Method 'FluentDocker.Testing.Core.ResourceLifecycle.CreateAndInitializeAsync<TResource>(System.Func<FluentDocker.Kernel.FluentDockerKernel, TResource>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Func<System.Threading.Tasks.Task<FluentDocker.Kernel.FluentDockerKernel>>, System.Threading.CancellationToken, Microsoft.Extensions.Logging.ILoggerFactory)' should take CancellationToken as the last parameter (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1068)
CodeQL Security Analysis: FluentDocker/Testing/Core/SwarmStackResource.cs#L139
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis: FluentDocker/Testing/Core/TopologyResource.cs#L159
For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, Exception?, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)
CodeQL Security Analysis
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
build (windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
nuget-packages
2.86 MB
sha256:7b4fb580444561a1ef60cc029dce50195b02bef6e5f45b8356fab02353cdbfff