standard-version: CRITICAL: minor bumps being ignored
954363d (HEAD -> feature/standard-version-release, tag: v2.0.0) chore(release): 2.0.0
aede9f4 feat: Broke the API
30acfe1 (tag: v1.3.0) chore(release): 1.3.0
f76aa30 feat: Forced a feature change
6836ceb (tag: v1.2.0) chore(release): 1.2.0
570f674 fix: Fixed a dummy thing...
cbc732d (tag: v1.1.0) chore(release): 1.1.0
d21e3ed build: no trailing space
701a018 (tag: v1.0.0) chore(release): 1.0.0
e251f2e chore: Installed standard-version for simple semantic release tagging
the version bump is wrong for commits d21e3ed (build:…) and 570f674 (fix:…) as should be a patch level change but is bumping to next minor.
feat: works as expected BREAKING CHANGE: works as expected
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 17 (5 by maintainers)
I had the same issue and was able to resolve it by pushing the created tag for the minor version. After the tag was pushed
npm run releasecreated a patch version as expected.My problem was that I did not push the tag which is being created by standard-version but wanted to create it later manually.
@NetanelBasal I just had the same issue again on yesterday and I found a way to fix this.
What I realized was that I needed to merge the master-branch back into development (we are doing releases from development-branch) after creating the tag.
I just took a quick look at your repository and it seems like v3.10.0 did not find a way back into master and is being ignored when running
release.Also there seems to be a similar anomaly on version 3.7.0.
Going to post this here because it may help someone one day.
I had this problem only on my CI server. Version bump was minor no matter what I tried. Same repo/code on my machine produced correct results. Turns out the issue was that whatever Git plugin was running on my CI server did not fetch tags by default. The solution was to enable fetching tags.