-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET May 2022 Update - .NET 6.0.5, .NET 5.0.17, and .NET Core 3.1.25 #7447
Comments
Hello, in our CI/CD pipelines we´re using the following YML step to get the latest .Net SDK Version:
Until yesterday we recieved version 6.0.202 via this task. From today it´s 6.0.300. Now all our Builds have a massive amount of warnings regarding the Microsoft Code Analysis. It looks like a missing assembly ('Microsoft.CodeAnalysis.CodeStyle.dll').
|
Our builds are returning extra code analysis violations since upgrading to .NET Core 6.0.5 (i.e. SDK 6.0.300). These warnings are not present in SDK 6.0.203. e.g. The line e.g. The line |
Hello, We have some CI/CD builds which have started failing after the release of dotnet 6.0.300 which seems to be related to central package management. The error we are getting is: Yesterday this was not a problem (with version 6.0.202), and after investigation we found that our builds started working again when specifying verison 6.0.202 to be installed. We are using the actions/setup-dotnet@v2 action to achieve this. Previously we installed the latest dotnet in our workflow yml files like so:
but we have reverted it like this for now:
These are running on the ubuntu-latest GitHub runners. |
@rbhanda |
I'm seeing some new failures as well. I have a project with the following PropertyGroup in the .csproj file. <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
</PropertyGroup> When I run The specific warning/error is |
Seems like |
Closing in favor of #7536 |
Release Notes
6.0.5
5.0.17
3.1.25
Please report any issues you find either by responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Note: This list refers to the Microsoft-provisioned feeds (packages.microsoft.com) and does not in any way represent direct availability in distros (eg RHEL, Fedora).
Known Issues
If there are any more issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.
The text was updated successfully, but these errors were encountered: