can't trigger release if a commit has happened since the "release" commit

[Haroenv]

Describe the bug

When you prepare a release, but after merging you see something small is missing, I don't want to prepare the release again.

To Reproduce
Steps to reproduce the behavior:

1. shipjs prepare
2. git commit -m "something else"
3. shipjs trigger

Expected behavior

The last prepare which was not yet released will now be released, but only if the changes since the last release chore, docs, maybe fix?

Screenshots

Skipping a release due to the following reason:
  > The commit message should have started with the following:
chore: release v1.4.0

Environment (please complete the following information):

• environment: your local machine
• Ship.js version: 0.13.1

Additional context

For now what I do is enable force pushing on the repo, making the fix in a separate commit, but reordering so the release commit is latest again, then disabling force push again