If the cratis CLI instance running is running as a dotnet tool, it should just do the appropriate dotnet tool update. But if it is running as a native command, we need to know it is from brew or not. If brew issue the correct brew upgrade command. For others, we don't know how they installed it - so we basically have to tell them to do it themselves in however way they installed it - but if its a Linux installation, just print the approach we have on our getting started / readme for installing.
We could know which mode it is through compiler directives.
Either way, whenever we run cratis we should always start a background task to check if there is a newer version. And if there is a newer version, have a colored text after whatever command has run that says there is a newer version with what version the user has and then what version they will get when running cratis update - point out that they need to run cratis update - unless its a manual install, then print the manual approach as above.
If the
cratisCLI instance running is running as a dotnet tool, it should just do the appropriate dotnet tool update. But if it is running as a native command, we need to know it is from brew or not. If brew issue the correct brew upgrade command. For others, we don't know how they installed it - so we basically have to tell them to do it themselves in however way they installed it - but if its a Linux installation, just print the approach we have on our getting started / readme for installing.We could know which mode it is through compiler directives.
Either way, whenever we run
cratiswe should always start a background task to check if there is a newer version. And if there is a newer version, have a colored text after whatever command has run that says there is a newer version with what version the user has and then what version they will get when runningcratis update- point out that they need to runcratis update- unless its a manual install, then print the manual approach as above.