search

go-semantic-release / semantic-release

📦🚀 semantic-release written in Go
https://go-semantic-release.xyz
MIT License
411 stars 43 forks source link

The initial run of semantic-release automatically increments the MAJOR version #19

Closed brooksjbr closed 5 years ago

brooksjbr commented 5 years ago

I'm experiencing something unexpected on the initial run of semantic-release. The MAJOR version is incremented, but a "BREAKING CHANGES" commit hasn't been made.

There have been a number of feat commit messages pushed, with the expectation of the MINOR version incrementing.

For example, if the tagged version is currently v0.0.0 and a commit is pushed feat(app): new feature I expect the updated version to be v0.1.0, but I'm seeing v1.0.0

christophwitzko commented 5 years ago

~Hi @brooksjbr, semantic-release does not support versions for initial development.~

semantic-release now supports initial development versions with the CLI flag --allow-initial-development-versions.

xoxys commented 1 year ago

Hello @christophwitzko is this still true? Because in this case the example from https://github.com/go-semantic-release/commit-analyzer-cz#bump-minor-version-012---020 seems to be wrong, indicating that bumping minor versions of 0.x.y is supported. I also encountered this problem when I expected a minor version bump from a 0.x.y version, since there were no breaking changes.

christophwitzko commented 1 year ago

@xoxys you are right, this is not true anymore. The comment meant an older version of semantic-release. You can use the CLI flag --allow-initial-development-versions

xoxys commented 1 year ago

Ah I missed that flag. Thanks!