Skip to content

Bump actions/setup-dotnet from 4 to 5 #778

Bump actions/setup-dotnet from 4 to 5

Bump actions/setup-dotnet from 4 to 5 #778

Triggered via pull request March 16, 2026 02:03
Status Failure
Total duration 2m 42s
Artifacts

build-and-test.yml

on: pull_request
Matrix: Build
Publish
Publish
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 20 warnings
Build (ubuntu-22.04-arm, net10.0, 10.0.x, true, -x64, false)
Process completed with exit code 1.
Build (macos-26, net10.0, 10.0.x, true, -x64, false)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (macos-26, net10.0, 10.0.x, true, -x64, false)
The operation was canceled.
Build (macos-26, net8.0, 8.0.x, -x64, false)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (macos-26, net8.0, 8.0.x, -x64, false)
The operation was canceled.
Build (ubuntu-latest, net10.0, 10.0.x, true, -x64, false)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (ubuntu-latest, net10.0, 10.0.x, true, -x64, false)
The operation was canceled.
Build (ubuntu-latest, net10.0, 10.0.x, true, -x64, false): src/ImageSharp.Drawing/Shapes/PathBuilder.cs#L459
Keyword 'this' is not available in the current context
Build (ubuntu-latest, net10.0, 10.0.x, true, -x64, false): src/ImageSharp.Drawing/Shapes/PathBuilder.cs#L459
Keyword 'this' is not available in the current context
Build (windows-latest, net10.0, 10.0.x, true, -x64, false)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (windows-latest, net10.0, 10.0.x, true, -x64, false)
The operation was canceled.
Build (windows-latest, net8.0, 8.0.x, -x64, false)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (windows-latest, net8.0, 8.0.x, -x64, false)
The operation was canceled.
Build (ubuntu-latest, net8.0, 8.0.x, -x64, true)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (ubuntu-latest, net8.0, 8.0.x, -x64, true)
The operation was canceled.
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false)
The strategy configuration was canceled because "Build.ubuntu-22_04-arm_net10_0_" failed
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false)
The operation was canceled.
WarmLFS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04-arm, net10.0, 10.0.x, true, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04-arm, net10.0, 10.0.x, true, -x64, false)
No files were found with the provided path: tests/Images/ActualOutput/. No artifacts will be uploaded.
Build (macos-26, net10.0, 10.0.x, true, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-26, net8.0, 8.0.x, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, net10.0, 10.0.x, true, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, net10.0, 10.0.x, true, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, net8.0, 8.0.x, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, net8.0, 8.0.x, -x64, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04-arm, net8.0, 8.0.x, -x64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, NuGet/setup-nuget@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Benchmarks/Drawing/DrawBeziers.cs#L43
Member 'DrawLinesCore' does not access instance data and can be marked as static (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1822)
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Benchmarks/Drawing/FillPathGradientBrush.cs#L11
Type 'FillPathGradientBrush' owns disposable field(s) 'image' but is not disposable (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1001)
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Benchmarks/Drawing/EllipseStressTest.cs#L14
Type 'EllipseStressTest' owns disposable field(s) 'image' but is not disposable (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1001)
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Benchmarks/Drawing/DrawBeziers.cs#L20
Member 'DrawPathSystemDrawing' does not access instance data and can be marked as static (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1822)
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Tests/TestUtilities/TestEnvironment.cs#L76
Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Tests/TestUtilities/TestEnvironment.cs#L69
Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)
Build (ubuntu-22.04-arm, net8.0, 8.0.x, -x64, false): tests/ImageSharp.Drawing.Tests/TestUtilities/TestEnvironment.cs#L26
The behavior of 'string.StartsWith(string)' could vary based on the current user's locale settings. Replace this call in 'SixLabors.ImageSharp.Drawing.Tests.TestEnvironment.IsFramework.get' with a call to 'string.StartsWith(string, System.StringComparison)'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1310)