Support for custom version with just specifying major and minor version

[PeterStaev]

It would be great if we can specify a custom version by just specifying major and minor versions. Right now all the version numbers seem to be required. In most of the cases where I want to use a specific version would be when I want to use a previous stable version. So it does not matter the revision number that is used as there shouldn't be any breaking changes between revisions.

[hey24sheep]

There is a support for custom version. You can check the readme doc for Install task

[PeterStaev]

Yes, I know of that and I'm actually using it. The problem is that it requires a full match. So for example I need to write "3.29.1" or similar. Instead I just want to write "3.29.x" and it will just pull the latest that is available that has major version set to 3 and minor set to 29.

[hey24sheep]

I see, that is not possible because of the way the version is fetched actually. I mean through hacks and all that will be possible but it won't be that big of a benefit. The reason for custom version flag is so it doesn't auto do anything and always run the same version

[PeterStaev]

Actually I see much benefit for this. Like for example the dotnet ADO tasks - in general I do not care if the build is done by 8.0.0, 8.0.100, or some other version, since the way MS releases versions 8.x.x will be mostly compatible with the codebase and I want to be on the latest possible version in order to have any critical patches/fixes auto-applied.
Similarly, in the flutter environment, most breaking changes / need to update packages come between minor stable versions - so if I change to build with 3.29 instead of the 3.27. The patch versions usually do not introduce any breaking changes so I want to keep my code built with the latest patch version so that it includes any fixes.

Note that the idea here is not to remove the current ability to specify a full specific version. So if the user wants they can still be able to specify 3.29.1 if they want to.