You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe my use-case is weird but I often need to re-apply standard-version changelog generation when crafting my release, for many reasons: last minute bug fixes, forgotten pull requests, etc.
My workflow is:
using standard-version to bump version, generate changelog, commit the file, add tag
hell ! I forgot
merge PR / commit any content
"fix" the release with standard-version
The problem appears on the last step, as I'd like to use standard-version --skip.bump to just update the Changelog without creating a new version, but it fails on the tagging step because tag already exists. I may not use --skip.tag because I do want the tag to be updated to the latest commit.
That's why I'd like to have an option that allows me to move the existing version tag to the latest commit.
PR incoming !
The text was updated successfully, but these errors were encountered:
pluce
linked a pull request
Nov 3, 2021
that will
close
this issue
Maybe my use-case is weird but I often need to re-apply
standard-version
changelog generation when crafting my release, for many reasons: last minute bug fixes, forgotten pull requests, etc.My workflow is:
standard-version
to bump version, generate changelog, commit the file, add tagThe problem appears on the last step, as I'd like to use
standard-version --skip.bump
to just update the Changelog without creating a new version, but it fails on the tagging step because tag already exists. I may not use--skip.tag
because I do want the tag to be updated to the latest commit.That's why I'd like to have an option that allows me to move the existing version tag to the latest commit.
PR incoming !
The text was updated successfully, but these errors were encountered: