Workflow to use main and next branches

qiwi / multi-semantic-release

Proof of concept that wraps semantic-release to work with monorepos.

BSD Zero Clause License

86 stars 34 forks source link

Workflow to use main and next branches #101

Open iris-garcia opened 1 month ago

iris-garcia commented 1 month ago

Issue type

[ ] bug report
[ ] idea
[x] question
[ ] other

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 to next collisions with the git tag/release of main.

How is it supposed to work with that workflow? if it is possible at all.

Thank you.

[x] I've read the docs. This case is not mentioned
[x] Similar issue does not exist

antongolub commented 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.