Yes indeed. However can we agree that change of the runtime, i.e. change from runtime .net core 2.x → 3.x is breaking? Can this be handled from your side better in the future? i.e. increasing the major version / version for the task as usual and expected by the other extensions? We are using tens of extensions for our Azure DevOps projects. Now the sonarcloud pipeline is integrated to tens of projects and hundreds of people depends on successful run of these pipelines. It is indeed really a big issue for us when such pipelines starts failing unexpectedly (i.e. because the new version of the extension installs automatically).
Can this be handled from your side better in the future = increasing major/extension version when doing breaking changes?