GitTools | A repository with 3 tools for pwn'ing websites with git repositories available

I am trying to install a custom package in Julia using command Pkg.add(PackageSpec(path = "")), which is in my local directory. I created my package using the Julia documentation. But every time when I am trying to install my custom package using PackageSpec from my local path it throws an error. The folowing error is -

I'm running gitversion.exe as part of a GitHub actions workflow on Windows using pwsh:

I raised a request for GitTools task in Azure Devops and now I can see that in my organization extensions setting tab.

But now when I want to add this to my pipeline, I am not seeing any Add button.

I am able to add other tasks such as Yarn or Replace Tokens(See the first image, below GitTools Task).

Below you can see Add button is enabled. But for GitTools, I dont see any Add button. What am I missing?

I have a repo in azure and it has the default branch "main".

Also, I have a task in yml file for semantic versioning.

I have a couple of webapps I am adding gitversion to. Main problem - GitVersion is generating a MajorMinorPatchTag where the Major is in the format yyyymmdd. Aside from this not being a valid major version, I want the usual versioning 0.1.3.alpha.1 in the example below but I am getting 20201021.1.1.

I have removed all the old build tags from the repo so it does not appear to be finding this from tags. Is there anywhere else I can force it to ignore previous build versions and use the semver starting from the gitversion.yml/next-version setting?

Detail below:

The gitversion.yml is simple:

I'm hoping to use fuzzy wuzzy to compare all strings in a list against each other, but it looks not every string is being compared against one another in the list. Here's what I've tried:

I'm trying to install package in julia 1.4.2 but it always returns this:

I can successfully get the full json string with:

Talking about UseGitVersion@5 Azure DevOps task, which is a wrapper around the actual GitVersion tool. I looked at the various GitVersion configuration options, but I could not find anything that will increment per build. Not per commit, per build. I have a build counter value I can pass to GitVersion, if it would be willing to accept it somehow, but I don't see any argument or option to use it.

The only option I found so far is to override the next-version value in GitVersion.yml, but I would prefer to increment the PreReleaseTag rather than the semver.