We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Although there shouldn't be any changes in .NET 6 that break YARP, we should add .NET 6 as a target for build validation
The text was updated successfully, but these errors were encountered:
We'll start with tests and samples. We don't want to add a .NET 6 target to the shipping packages until after 1.0.
Sorry, something went wrong.
We'll also need to review #if's in the tests and product code to make sure we're using the new NET5_0_OR_GREATER symbols so we don't have to add 6.0 specific symbols. https://github.com/dotnet/designs/blob/be793b557255c9ed1276ecdd23119b64f45453bf/accepted/2020/or-greater-defines/or-greater-defines.md
MihaZupan
Successfully merging a pull request may close this issue.
Although there shouldn't be any changes in .NET 6 that break YARP, we should add .NET 6 as a target for build validation
The text was updated successfully, but these errors were encountered: