Not releasing correct version if previous tag is not cloned down beforehand

[GeorgeCadwallader]

(NOTE: This issue has been replicated from the old repository)

Description

If the latest version is v1.0.0. If the commit from v1.0.0 is not cloned down, then conventional tools will try to release v0.0.1.

Expected Behaviour

The correct tag should be released, it should be at least more than the most recent tag.

Actual Behaviour

It is releasing version 0.0.1

Notice an error is thrown

›   Error: Command failed with exit code 128: git tag v0.0.1
›   fatal: tag 'v0.0.1' already exist

A workaround it to do a full clone when releasing. For github actions that will be the below

steps:
  - name: Checkout
    uses: actions/checkout@v3
      with:
        fetch-depth: 0

Steps to Reproduce the Problem

1. git clone --depth 1 https://github.com/Practically/webpack-config
2. cd webpack-config
3. git fetch --tags
4. export CT_TOKEN=xxx
5. conventional-tools release-semver