attempt at fixing versions in user-facing docs

[bjaglin]

Since versions used in docs (and in metadata available for clients) come from https://github.com/sbt/sbt-dynver, I don't understand how this ever worked with a shallow clone, so this might help with #1538

[bjaglin]

https://github.com/actions/checkout

# Number of commits to fetch. 0 indicates all history for all branches and tags.
# Default: 1

[mlachkar]

I don't understand why this number is wrong ...but let's try!

[bjaglin]

https://github.com/sbt/sbt-dynver#setup

In CI, you may need to run git fetch --unshallow (or, sometimes, git fetch --depth=10000), to avoid situations where a shallow clone will result in the last tag not being fetched. Additionally git fetch --tags if the repo is cloned with --no-tags.

[bjaglin]

For the record the release job gets proper versions because it does an explicit unshallow

scalafix/.github/workflows/release.yml

Line 13 in 6d991eb

- run: git fetch --unshallow

I guess either approach is correct. The unshallow is maybe a bit more efficient but I like that fetch-depth is a flag on the checkout as it's more apparent.

[bjaglin]

It looks like it worked: c151ae6! I have no idea why it worked without this before though... Maybe to be continued.