Open iris-garcia opened 1 month ago
I'm afraid, I do not see a simple workaround. We have previously considered a similar case and realized that in some situations (prereleases from feature branches) we need a different way of storage for meta: 1) release info files in a separate branch https://github.com/qiwi/pijma/tree/meta 2) as part of GH assets https://github.com/antongolub/misc/blob/master/.releaserc.cjs https://github.com/antongolub/misc/releases/tag/0.1.0-esbuild-plugin-transform-ext (see meta.json)
But we were unable to adapt this architecture to the semantic-release and created a separate tool from scratch.
Issue type
Expected behavior
The
next
branch can be used for next major releases.Actual behavior
There is a git tag collision. Having release the first version from
main
and then starting a new feature and pushing tonext
collisions with the git tag/release ofmain
.How is it supposed to work with that workflow? if it is possible at all.
Thank you.