Closed KetanReddy closed 3 months ago
Previously during a non-canary/next release, the version file plugin would always prepend a v to the tag that was created for the new version regardless of if the noVersionPrefix option was set.
v
noVersionPrefix
The noVersionPrefix option should be respected
Todo:
Indicate the type of change your pull request is:
documentation
patch
minor
major
:rocket: PR was released in v11.2.1 :rocket:
v11.2.1
What Changed
Previously during a non-canary/next release, the version file plugin would always prepend a
v
to the tag that was created for the new version regardless of if thenoVersionPrefix
option was set.Why
The
noVersionPrefix
option should be respectedTodo:
Change Type
Indicate the type of change your pull request is:
documentation
patch
minor
major