I am trying to configure a simple app and it keeps analyzing all the commits on the repo and not just the subset of commits after the latest release.
This is cause the versions to always be bumped major since there are commits early on that cause a major version update; even though the only commit analyzed should be a patch.
After debugging I've gotten to the point where it seems the package is not getting publish to npm with the gitHead and that cause semantic-release to not grab the subset of correct commits valid for that release.
I'm not sure whats going on. I've reprod this two times with dummy projects.
Note that our repo is published to npm through myget using a .npmrc file.
I am trying to configure a simple app and it keeps analyzing all the commits on the repo and not just the subset of commits after the latest release.
This is cause the versions to always be bumped major since there are commits early on that cause a major version update; even though the only commit analyzed should be a patch.
After debugging I've gotten to the point where it seems the package is not getting publish to npm with the
gitHeadand that cause semantic-release to not grab the subset of correct commits valid for that release.I'm not sure whats going on. I've reprod this two times with dummy projects.
Note that our repo is published to npm through myget using a .npmrc file.
Any ideas?