Skip to content
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

Packages that depended on the latest version of System.Runtime.CompilerServices.Unsafe regressed and use a very old version of Unsafe now #67380

Closed
ViktorHofer opened this issue Mar 31, 2022 · 1 comment · Fixed by #67385

Comments

@ViktorHofer
Copy link
Member

One example of such a package is DiagnosticSource and that was fixed with 6ba20ab.

Overall this regressed with ddb22ef. See #67196 (comment) for a more detailed explanation why this regressed.

@ghost
Copy link

ghost commented Mar 31, 2022

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

One example of such a package is DiagnosticSource and that was fixed with 6ba20ab.

Overall this regressed with ddb22ef. See #67196 (comment) for a more detailed explanation why this regressed.

Author: ViktorHofer
Assignees: -
Labels:

area-Meta, regression-from-last-release

Milestone: 7.0.0

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Mar 31, 2022
@ViktorHofer ViktorHofer self-assigned this Mar 31, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Mar 31, 2022
@ghost ghost removed untriaged New issue has not been triaged by the area owner in-pr There is an active PR which will close this issue when it is merged labels Apr 1, 2022
@ghost ghost locked as resolved and limited conversation to collaborators May 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.