You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I recently updated my project to target .NET 9.0 after its release. I modified the csproj file to set the TargetFramework to .NET 9.0 and successfully built the project on my local machine. However, after committing the changes, the GitHub Actions workflow fails during the build step with the following error:
The current .NET SDK does not support targeting .NET 9.0. Either target .NET 8.0 or lower, or use a version of the .NET SDK that supports .NET 9.0. Download the .NET SDK from https://aka.ms/dotnet/download
This suggests that the version of the .NET SDK being used in the GitHub Actions environment does not yet support .NET 9.0.
Questions:
Is .NET 9.0 supported in GitHub Actions?
Do I need to configure my workflow specifically for .NET 9.0?
Actual behavior:
Build step with the following error:
The current .NET SDK does not support targeting .NET 9.0. Either target .NET 8.0 or lower, or use a version of the .NET SDK that supports .NET 9.0. Download the .NET SDK from https://aka.ms/dotnet/download
The text was updated successfully, but these errors were encountered:
Description:
I recently updated my project to target .NET 9.0 after its release. I modified the csproj file to set the TargetFramework to .NET 9.0 and successfully built the project on my local machine. However, after committing the changes, the GitHub Actions workflow fails during the build step with the following error:
This suggests that the version of the .NET SDK being used in the GitHub Actions environment does not yet support .NET 9.0.
Questions:
Task version:
actions/setup-dotnet@v3
Platform:
Runner type:
Repro steps:
https://github.com/ZjzMisaka/PowerThreadPool/blob/main/.github/workflows/test.yml
Expected behavior:
Successfully build
Actual behavior:
Build step with the following error:
The text was updated successfully, but these errors were encountered: