https://github.com/dotnet/arcade/pull/13991#discussion_r1389571783
By default dotnet tools allow only the minor version rollforward. Major version rollforwad need to be opt-in at the execution time (and for the dotnet tools this can only be done via env var - https://github.com/dotnet/sdk/issues/10375) or it can be opted in via the tool itself.
If we want the tool to be used in the internal engineering builds, the default major rollforward should be seriously considered
Downsides
This means appearing to support newer runtime that is not available for testing together with the tool at the time of publishing the tool - so an issue can occure in the future that would not be discoverable at the time of publishing.
However this is just a theoretical option, while not being able to run on newer runtime version is existing complication
Context
https://github.com/dotnet/arcade/pull/13991#discussion_r1389571783 By default dotnet tools allow only the minor version rollforward. Major version rollforwad need to be opt-in at the execution time (and for the dotnet tools this can only be done via env var - https://github.com/dotnet/sdk/issues/10375) or it can be opted in via the tool itself. If we want the tool to be used in the internal engineering builds, the default major rollforward should be seriously considered
Downsides
This means appearing to support newer runtime that is not available for testing together with the tool at the time of publishing the tool - so an issue can occure in the future that would not be discoverable at the time of publishing. However this is just a theoretical option, while not being able to run on newer runtime version is existing complication