Publish complete API documentation - #9
Merged
Conversation
Stephanvs
marked this pull request as ready for review
August 9, 2026 10:54
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
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.
What changed
CS1591CompatibilitySuppressions.xml, while keeping baseline package validation active for any additional breaksValidation
netstandard2.0,net8.0, andnet10.0: 0 warnings, 0 errors.nupkgand.snupkgcreation and content inspection: passedStack and merge order
Merge independent PR #6 first or at any point. Then merge #4; after that, #5 and #7 can be retargeted to
mainand merged in either order. Merge #8 next and retarget this PR tomainlast. Release the resulting API as 2.0.0 because the compatibility suppressions document intentional major-version changes.