Releasing a version is way too complex
Opened this issue · 1 comments
andersfylling commented
Describe the bug
When I do a squash commit and write "BREAKING CHANGES" in the footer, I expect that it's going to be a major release. Not minor, and not patch as well. Just major.
When I do a minor release, by typing "feat:" in the commit title, I expect there to be only a minor release, no patch releases.
It would be great to see that a release version is carried out across all affected packages. Think WYSIWYG principle. It's better to have multiple smaller PR's, if granularity is a concern, than trying to have a smart system that consistently deploys incorrect versions which may cause dependents to have a bad day.
Suggested change:
- commit title
feat!: msg
causes a major release in all affected packages - commit title
feat: msg
causes a minor release in all affected packages - commit title
fix: msg
causes a patch release in all affected packages - drop requirement to have
BREAKING CHANGES: msg
in the footer, and keep release logic consistent and unified.
related:
RodrigoRVSN commented
Just to put as a reference/example, release-please
works in this way