Allow the creation of releases based on an already existing version number

[GroovinChip]

Use case

I have a branch dedicated to releases, and any PR's to this branch require that the version number of the project already be updated. As such, I do not need to make a bump when generating a release. I only need to create a release based on this number. As such the corresponding tag does not need a version bump. So it would be great if I could specify to this action that no version bump is required, but to still create a release and corresponding tag anyway.

Example:

1. A PR is created to the dev branch, which contains a version bump from 1.6.0 to 1.7.0
2. The PR gets merged to dev and a new PR gets opened from dev to stable
3. The PR to stable gets merged
4. This action gets run on the stable branch, creating a release with a tag of 1.7.0. (There is a prior step in this job that gets the version number from the file that contains it)

In the above example, setting bump_version_scheme to any of the existing options doesn't result in the desired behavior. norelease would cause no release to be published at all, and minor would result in a tag of 1.8.0, which isn't correct.

I hope I've described this issue clearly, please let me know if further explanation is required.