Commit with version tag not found

[Crossbow78]

In this picture the two topmost commits are in a feature branch, the rest is in master branch.

As you can see I tagged one (latest) commit in master branch, and when the pipeline builds that commit it produces nuget package MyOwnLibrary-0.1.0.nupkg as expected.

Now I'm in my feature branch, and run my pipeline on latest commit. My expectation is that it would arrive at version 0.2.0-alpha.0.2 where the last 2 is the height to the tagged commit. Btw, this would however cause a conflict between two feature branches that are at the same distance...
But it does not find the tagged commit at all as can be seen in below logs, what am I missing here?

[Crossbow78]

Here's a more detailed log... it seems that git log has a smaller reach than expected. Does anyone know why?

(Note that commit 8573d5c7fd130733a6b36b2655342b28fdcad284 is the new latest commit in that feature branch where I changed the MinVer log level)

[Crossbow78]

This seems to be caused by a recent change in default Azure DevOps pipeline behavior where the git checkout has changed to a shallow fetch with maxDepth 1. The issue also affected Nerdbank.Gitversioning.

When adding the following step in my pipeline, Minver is behaving exactly as expected:

- checkout: self
  fetchDepth: 0