Async release version control

[yyynnn]

Is there a way to control major versions across multiple async release branches?

Problem:
We have stage1, stage2 branches. Each of these branches have divergent tags - stage1 have 1.x.x, stage2 have 2.x.x. So we will get error in CI if we bump stage1 tags up to next major version.

Solution:

1. Prevent major version bump via some team convention or via some check in multi-semantic-release.
2. Diverge versions via semver metadata (But 'two versions that differ only in the build metadata, have the same precedence') or some prefix (which is not very sem ver).

[antongolub]

Hey, @yyynnn,

Unfortunately, we do not use multi-branch releases at all. Therefore, it is difficult to say something meaningful or advise, sorry. If you have enough time to add a workaround, we'll be happy to accept your PR.