Due to the changes in #433 pre-release tags are ignored when getting the target release version.
Problem
If a prelease is started using the --releaseAs=prerelease parameter then it is fine as it takes the previous commits into account to identify the correct version.
If a prerelease is started using premajor, preminor or prepatch then it might lead to (in my opinion) wrong release versions when performing the actual release.
Example
Let's assume an app named myapp having the version target and the current version 1.2.0 with the latest tag myapp-v.1.2.0
In the next step we want to create a new premajor release candidate:
nx run myapp:version --releaseAs=premajor --preid=rc
This leads to a new prerelease tag myapp-v.2.0.0-rc.0
Next, we add a few changes/commits and perform another prerelease:
nx run myapp:version --releaseAs=prerelease
This leads to a new prerelease tag myapp-v.2.0.0-rc.1.
Finally, we create a new release: nx run myapp:version
This leads to a new release tag myapp-v.1.3.0 because it identifies the release to be a minor one due to the previous commits. It ignores the manually set premajor. The only way to "fix" this for me would be to add releaseAs=major to my command.
Expected Behavior
It should be a configurable option whether prerelease tags should be considered for getting the release version to support my scenario so that I do not have to specify the release version via releaseAs anymore as the release version should always match the pre-release version.
Or is there another way (currently) to achieve my goal?
Due to the changes in #433 pre-release tags are ignored when getting the target release version.
Problem
If a prelease is started using the
--releaseAs=prereleaseparameter then it is fine as it takes the previous commits into account to identify the correct version. If a prerelease is started usingpremajor,preminororprepatchthen it might lead to (in my opinion) wrong release versions when performing the actual release.Example
Let's assume an app named
myapphaving the version target and the current version1.2.0with the latest tagmyapp-v.1.2.0In the next step we want to create a new
premajorrelease candidate:nx run myapp:version --releaseAs=premajor--preid=rcThis leads to a new prerelease tagmyapp-v.2.0.0-rc.0Next, we add a few changes/commits and perform another
prerelease:nx run myapp:version --releaseAs=prereleaseThis leads to a new prerelease tagmyapp-v.2.0.0-rc.1.Finally, we create a new release:
nx run myapp:versionThis leads to a new release tag
myapp-v.1.3.0because it identifies the release to be aminorone due to the previous commits. It ignores the manually setpremajor. The only way to "fix" this for me would be to addreleaseAs=majorto my command.Expected Behavior
It should be a configurable option whether
prereleasetags should be considered for getting the release version to support my scenario so that I do not have to specify thereleaseversion viareleaseAsanymore as the release version should always match the pre-release version.Or is there another way (currently) to achieve my goal?