elliotttf / semantic-release-conventional-commits

Semantic release commit analyzer support for all of the conventional commit message types
12 stars 1 forks source link

ENOCHANGE error #3

Closed LeonardoGentile closed 7 years ago

LeonardoGentile commented 7 years ago

Hello, thank you for this package.

I've been using it before without problem. Today I've tried to use semantic-release with you plugin and no matter what, I receive:

semantic-release ERR! pre Failed to determine new version.
semantic-release ERR! pre ENOCHANGE There are no relevant changes, so no new version is released.

In my packages.json I have:

"devDependencies": {
    "cz-conventional-changelog": "2.0.0",
    "semantic-release": "^6.3.6",
    "semantic-release-conventional-commits": "1.0.2"
}
"scripts": {
    "commit": "git-cz",
    "semantic-release": "semantic-release pre && npm publish && semantic-release post",
    "config": {
      "commitizen": {
        "path": "./node_modules/cz-conventional-changelog"
      }
    },
    "release": {
      "analyzeCommits": {
        "path": "semantic-release-conventional-commits",
        "minorTypes": ["feat","minor"],
        "patchTypes": ["fix", "patch", "docs", "refactor", "style", "perf"]
      }
    }
  }

I have performed some commits since my last release, their messages are in the form:

refactor(myComp):Whatever
docs(README,CONTRIBUTING): Improved docs
style(withLink): Make linter happy
docs(CONTRIBUTING): Add note on linting before requesting a PR

As you can see I've configured refactor and docs to be commits type that should trigger a new patchTypes release.

But I can't get this to work. I have tried to debug with webstorm but it doesn't seem too happy to debug npm scripts.

I'm sure I've already used this configuation before and a docs(whatever) commit triggered a new release.

How can I help you debugging this?

LeonardoGentile commented 7 years ago

Sorry, I had a malformed packages.json