If I run standard-version right after a release the patch version number is increased...
I would expect the script to leave every thing as is since no change was made...
Is this intended?
Is there a way to disable/workaround this?
IMO standard-version should just exit if there are no commits since the last release.
Currently it'll bump patch regardless, create an empty changelog entry, etc.
This can happen when having to re-run a CI job, for example.
this is honestly kind of a deal breaker
Got the same, wondering about how not to bump if no changes was found
Did you found any solution? @eiriarte-mendez
Got the same, wondering about how not to bump if no changes was found
Did you found any solution? @eiriarte-mendez
I am facing the same issue
Hi all, I opened the issue only as a question, since I didnt looked at the code yet and was expecting someone to give me a hint...
@SuaYoo linked the issue on a different PR, however it is not fixing the problem here...
I see this problem is being faced by several people, so I will try to investigate on my own how to fix it...
I solved that by git diff on each project's source folder in my monorepo.
Would be great to have that option in conventional-changelog package
My example:
git describe --tag --candidates 1 --abbrev=0 --match="{packagename}-v*"git rev-list -n 1 {taghash}git diff {commitId} master {path-to-sources}I hope it helps
I've found that standard-version calls a function conventionalRecommendedBump which is already able to recognize if there where any commits since last release... however it is continuing the process...
It also seems that the called warn function is a configurable callback ...so I think it should be possible to pass from standard-version a function which interrupts the process and show a notification instead...
I will try to test it later and make a PR if it works... but if someone else is faster, dont hesitate to do it
Most helpful comment
IMO standard-version should just exit if there are no commits since the last release.
Currently it'll bump patch regardless, create an empty changelog entry, etc.
This can happen when having to re-run a CI job, for example.