Pinned latest version

[jarlef]

Output of brew config

N/A

Output of brew doctor

N/A

Description of issue

Microsoft released version .net 11 this week and this resulted in the dotnet-sdk cask to move from version 10 to 11. The old dotnet version gets it own pinned cask version dotnet-sdk@10. Upgrading major version when doing brew upgrade can break the local development environment because some codebases might have a strong dependency on a given sdk. Should the latest version also get its own pinned version dotnet-sdk@11 so that when .net 12 gets released next year it won't affect machines installed with dotnet-sdk@11

Relevant casks

dotnet-sdk

[HaraldNordgren]

Do you have your version pinnned?

brew pin dotnet-sdk

It would be interesting if when user is on latest dotnet-sdk (and it's pinned) that when new major version is released, the user can migrate to dotnet-sdk@10.

[jarlef]

No. We currently run on .net 10. We installed .net 10 using brew install --cask dotnet-sdk last year. When we run brew upgrade now we get a new major suddenly. So now all the developers on our team have to run brew uninstall ---cask dotnet-sdk and brew install --cask dotnet-sdk@10 to continue using .net 10. We are not planning to upgrade major until next month until all our infrastructure is ready for the latest dotnet sdk. So it would be useful to have a caskdotnet-sdk@11 already now that receives the latest patches but wont't switch to .net 12 when Microsoft pushes a new major next year.