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

[egoist]

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.

[Haroenv]

I think this is related to #414

[eunjae-lee]

Yeah it's related, but if there is only one commit, that will happen because there is no commit to release since the commit you chose. Unfortunately the behavior we have is like that. We'll try to find a way to fix this, but in the meantime you can still release it if there is one more commit.

[egoist]

@eunjae-lee OK, thanks for the info.