@benwulfe: No, because it's not actually a requirement. As documented, it's something you should do in some situations, but it's not only allowing you to be more efficient. Any code that doesn't dispose of the client will work just as well as it did before.

AdvancedTranslationClient done

If you have singletons that implement IDisposable, not disposing it is a pretty common (if maybe not entirely correct) usage pattern. I'd argue this caveat doesn't really make it special or unique.

I guess all I was saying is that the very existence of having an object that implements IDisposable that is not disposed is likely to create a lint error where it was ok before.
linters will not be able to read your comments.

Well, I'd argue that the expected behaviour at that point is for the developer to read the linter error, read the doc comment then, and configure the linter appropriately. If the linter can't be configured, I think that's a bigger problem. (And how does it cope with HttpClient and Task for example?)

I really believe that bumping the major version number would be a mistake here, giving an unrealistic impression of breaking.