Can't trigger release if there's only one commit

**Describe the bug**
A clear and concise description of what the bug is.
with only one commit, e.g. `feat: init`, it says:

```
› Getting a revision range for this release.
Git tag 'v0.0.0' doesn't exist.
? From which commit do you want to release? 1) 31b86aa (HEAD -> main, origin/main) feat: init
31b86aa..HEAD
› Calculating the next version.
Nothing to release!
```

**To Reproduce**
Steps to reproduce the behavior:
1. create a repo
2. create a commit
3. run `shipjs prepare`

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Environment (please complete the following information):**
- environment: (your local machine, CircleCI, Travis CI, etc.)
- `node -v`:
- `npm -v` or `yarn -v`:
- Ship.js version: 0.23.0

**Additional context**
Add any other context about the problem here.

Start with the `shipjs prepare` entry point and reproduce the behavior in a repository containing only the `feat: init` commit. Inspect how the release revision range and next version are calculated for this case. Done means the single-commit repository can trigger a release instead of reporting "Nothing to release!".

Written by the indexing model from the issue text.