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.

Sign up for GitHub

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

Jump to bottom

Add new SYSLIB warnings for .NET 7 #26328

Closed
1 task
jeffhandley opened this issue Sep 30, 2021 · 1 comment
Closed
1 task

Add new SYSLIB warnings for .NET 7 #26328

jeffhandley opened this issue Sep 30, 2021 · 1 comment
Assignees
@gewarren
Labels
breaking-change Indicates a .NET Core breaking change 🏁 Release: .NET 7 Work items for the .NET 7 release doc-enhancement Improve the current content [org][type][category] Pri3

Comments

@jeffhandley
Copy link
Member

Update this page based on additions to https://github.com/dotnet/runtime/blob/main/docs/project/list-of-diagnostics.md during .NET 7.
@jeffhandley jeffhandley added doc-enhancement Improve the current content [org][type][category] breaking-change Indicates a .NET Core breaking change labels Sep 30, 2021
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Sep 30, 2021
@jeffhandley jeffhandley mentioned this issue Sep 30, 2021
Merged
@gewarren gewarren added the 🏁 Release: .NET 7 Work items for the .NET 7 release label Oct 1, 2021
@jeffhandley
Copy link
Member Author

Per @gewarren, I am closing this aggregate issue in favor of using individual breaking change issues for each new SYSLIB warning in .NET 7. #26352 was filed to capture Regex.CompileToAssembly.

@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gewarren gewarren

Labels
breaking-change Indicates a .NET Core breaking change 🏁 Release: .NET 7 Work items for the .NET 7 release doc-enhancement Improve the current content [org][type][category] Pri3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jeffhandley @dotnet-bot @gewarren @PRMerger16