Initially that repo was named hela-preset-tunnckocore with ~30 commits. Needed the name to be changed, so i changed the name to hela-config-tunnckocore. After the first commit on new repo, it "found" 32 commits in bulk, so for some only-god-know reason it decided to bump to major. No one of the commits have "BREAKING CHANGE" anywhere, just fix and feat types.
I in any way was going to publish v1 soon, but that surprise isn't good. Probably not documented that after some number of fixes and feats it auto-magically decides to bump major? More strange thing is that in the GitHub release is listed only the last commit - https://github.com/tunnckoCore/hela-config-tunnckocore/releases/tag/v1.0.0
https://travis-ci.org/tunnckoCore/hela-config-tunnckocore/jobs/285838102
Initially that repo was named
hela-preset-tunnckocorewith ~30 commits. Needed the name to be changed, so i changed the name tohela-config-tunnckocore. After the first commit on new repo, it "found" 32 commits in bulk, so for some only-god-know reason it decided to bump to major. No one of the commits have "BREAKING CHANGE" anywhere, justfixandfeattypes.I in any way was going to publish v1 soon, but that surprise isn't good. Probably not documented that after some number of
fixes andfeats it auto-magically decides to bump major? More strange thing is that in the GitHub release is listed only the last commit - https://github.com/tunnckoCore/hela-config-tunnckocore/releases/tag/v1.0.0