Drop .NET Standard 2.1 (netstandard2.1) target #1193
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
paulirwin
added
the
notes:breaking-change
|
Update: The run succeeded on Azure DevOps Pipelines. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Drops the .NET Standard 2.1 (netstandard2.1) target and .NET 6 tests for it.
Fixes #1040
Description
In draft until agreement is reached that we should drop this target, and to ensure tests/workflows pass. See rationale in discussion of #1040. Only Unity and Mono are currently supported runtimes that can use it, and both can use the .NET Standard 2.0 target. (Mono should even be able to use the .NET Framework target.)
Note that the GitHub workflow files previously had a UTF-8 BOM. When running the script to generate the workflows, it removed the BOM.