-
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 August 2022 Updates - .NET 6.0.8, .NET Core 3.1.28 #7682
Comments
Just an FYI, the README.md link for the 6.0.8 and 3.1.28 release notes has an invalid path (still has the old version in the parent directory):
|
@mockjv - I think it's fixed (unless I'm looking in the wrong place) |
@dcwhittaker Unfortunately I think I still see it @ https://github.com/dotnet/core/blob/main/README.md on both |
@mockjv ahh I see now. Fixed! Thank you :) |
I am running into a type load exception that bubbles up through PowerShell's |
I ran into a problem with .NET SDK 6.0.303 that doesn't exist in 6.0.300. I think this is the right place to report this problem. We use a batch file to build our project for various targets. Here's the relevant excerpt:
This stopped working with .NET SDK 6.0.303 and produces the following error:
Something is either swallowing the "FileVersion=" part of the build parameters, or maybe something else changed. I tried 6.0.400 with the same result. Again, no such problem occurs in 6.0.300. |
Closed in favor of #7791 |
Can anyone provide any guidance on CVE-2022-34716 and System.Security.Cryptography.Xml.dll? My understanding was that updating our SDK to 3.1.28 or higher should resolve this. But it's still showing up on our scans and as far as I can tell our build SDK and runtime should all meeting the fix criteria. The file version of the dll on our build artifacts still reads 11/15/2019, v4.700.19.56404, so I'm not sure how the "fixed" version is supposed to be generated. |
Release Notes
6.0.8
3.1.28
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 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: